The max apiVersion is 44.0 error
Trying to work through the Quick Start: Lightning Web Components trailhead and getting the following error while running command:
force:org:create -f config/project-scratch-def.json --setalias HelloWorldLightningWebComponent --durationdays 30 --setdefaultusername
ERROR: The configured apiVersion 45.0 is not supported for this org. The max apiVersion is 44.0.
I did not set up a new dev hub environment, but rather enabled devhub in my old dev environment.
Tried updating sfdx-project.json to include "sourceApiVersion": "44.0". but no luck.
trailhead vs-code
add a comment |
Trying to work through the Quick Start: Lightning Web Components trailhead and getting the following error while running command:
force:org:create -f config/project-scratch-def.json --setalias HelloWorldLightningWebComponent --durationdays 30 --setdefaultusername
ERROR: The configured apiVersion 45.0 is not supported for this org. The max apiVersion is 44.0.
I did not set up a new dev hub environment, but rather enabled devhub in my old dev environment.
Tried updating sfdx-project.json to include "sourceApiVersion": "44.0". but no luck.
trailhead vs-code
The Spring '19 pre-release signup is now live. Updated the link in the answer.
– Jayant Das
Dec 13 '18 at 17:13
add a comment |
Trying to work through the Quick Start: Lightning Web Components trailhead and getting the following error while running command:
force:org:create -f config/project-scratch-def.json --setalias HelloWorldLightningWebComponent --durationdays 30 --setdefaultusername
ERROR: The configured apiVersion 45.0 is not supported for this org. The max apiVersion is 44.0.
I did not set up a new dev hub environment, but rather enabled devhub in my old dev environment.
Tried updating sfdx-project.json to include "sourceApiVersion": "44.0". but no luck.
trailhead vs-code
Trying to work through the Quick Start: Lightning Web Components trailhead and getting the following error while running command:
force:org:create -f config/project-scratch-def.json --setalias HelloWorldLightningWebComponent --durationdays 30 --setdefaultusername
ERROR: The configured apiVersion 45.0 is not supported for this org. The max apiVersion is 44.0.
I did not set up a new dev hub environment, but rather enabled devhub in my old dev environment.
Tried updating sfdx-project.json to include "sourceApiVersion": "44.0". but no luck.
trailhead vs-code
trailhead vs-code
edited Dec 13 '18 at 18:58
Jayant Das
12.8k2723
12.8k2723
asked Dec 13 '18 at 16:44
Art SArt S
284
284
The Spring '19 pre-release signup is now live. Updated the link in the answer.
– Jayant Das
Dec 13 '18 at 17:13
add a comment |
The Spring '19 pre-release signup is now live. Updated the link in the answer.
– Jayant Das
Dec 13 '18 at 17:13
The Spring '19 pre-release signup is now live. Updated the link in the answer.
– Jayant Das
Dec 13 '18 at 17:13
The Spring '19 pre-release signup is now live. Updated the link in the answer.
– Jayant Das
Dec 13 '18 at 17:13
add a comment |
1 Answer
1
active
oldest
votes
UPDATE
Just got an update that the Spring '19 pre-release signup link is now live. You can access it on this link.
You are getting this error because the LWC project expects a version 45.0 (Spring '19 pre-release org), whereas the current DE sandboxes are still on version 44.0 (Winter '19).
You will need to signup for the Spring '19 pre-release DE Org to be used as DevHub for this module. And as of now that's not available, unless you already have a sandbox which has been upgraded to Spring '19.
I was in same situation this morning and found out that the signup for pre-release DE Org is not live yet. Refer to this tweet for response from Salesforce.
Yeah, the trailhead kind of fails to mention this, as far as I can tell.
– sfdcfox
Dec 13 '18 at 16:51
@sfdcfox True. I actually was exactly in this situation when went back and realized I need a Spring '19 org for this module. Then while signing up, couldn't do so.
– Jayant Das
Dec 13 '18 at 16:52
Yeah, I was just trying a trailhead this morn. I think LWC is going to change the way we do things, but a bit annoying they announced it without specifying special hoops
– sfdcfox
Dec 13 '18 at 16:54
I could just imagine, there's a lot of excitement around it from this morning, the time it was announced. I think I haven't seen anything like this which is GA without releasing a beta in first place.
– Jayant Das
Dec 13 '18 at 16:55
That's because they've been secretly testing it for a year. I noticed it a few months ago and I wrote it off as some Aura oddity, but I've known about this for a while. Like you'll write a component that useslightning:button
, but if you debug it in the Lightning Debugger, it shows up as alightning-button
, basically a first-class citizen of Lightning, which struck me as odd.
– sfdcfox
Dec 13 '18 at 16:58
|
show 1 more comment
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "459"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f242503%2fthe-max-apiversion-is-44-0-error%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
UPDATE
Just got an update that the Spring '19 pre-release signup link is now live. You can access it on this link.
You are getting this error because the LWC project expects a version 45.0 (Spring '19 pre-release org), whereas the current DE sandboxes are still on version 44.0 (Winter '19).
You will need to signup for the Spring '19 pre-release DE Org to be used as DevHub for this module. And as of now that's not available, unless you already have a sandbox which has been upgraded to Spring '19.
I was in same situation this morning and found out that the signup for pre-release DE Org is not live yet. Refer to this tweet for response from Salesforce.
Yeah, the trailhead kind of fails to mention this, as far as I can tell.
– sfdcfox
Dec 13 '18 at 16:51
@sfdcfox True. I actually was exactly in this situation when went back and realized I need a Spring '19 org for this module. Then while signing up, couldn't do so.
– Jayant Das
Dec 13 '18 at 16:52
Yeah, I was just trying a trailhead this morn. I think LWC is going to change the way we do things, but a bit annoying they announced it without specifying special hoops
– sfdcfox
Dec 13 '18 at 16:54
I could just imagine, there's a lot of excitement around it from this morning, the time it was announced. I think I haven't seen anything like this which is GA without releasing a beta in first place.
– Jayant Das
Dec 13 '18 at 16:55
That's because they've been secretly testing it for a year. I noticed it a few months ago and I wrote it off as some Aura oddity, but I've known about this for a while. Like you'll write a component that useslightning:button
, but if you debug it in the Lightning Debugger, it shows up as alightning-button
, basically a first-class citizen of Lightning, which struck me as odd.
– sfdcfox
Dec 13 '18 at 16:58
|
show 1 more comment
UPDATE
Just got an update that the Spring '19 pre-release signup link is now live. You can access it on this link.
You are getting this error because the LWC project expects a version 45.0 (Spring '19 pre-release org), whereas the current DE sandboxes are still on version 44.0 (Winter '19).
You will need to signup for the Spring '19 pre-release DE Org to be used as DevHub for this module. And as of now that's not available, unless you already have a sandbox which has been upgraded to Spring '19.
I was in same situation this morning and found out that the signup for pre-release DE Org is not live yet. Refer to this tweet for response from Salesforce.
Yeah, the trailhead kind of fails to mention this, as far as I can tell.
– sfdcfox
Dec 13 '18 at 16:51
@sfdcfox True. I actually was exactly in this situation when went back and realized I need a Spring '19 org for this module. Then while signing up, couldn't do so.
– Jayant Das
Dec 13 '18 at 16:52
Yeah, I was just trying a trailhead this morn. I think LWC is going to change the way we do things, but a bit annoying they announced it without specifying special hoops
– sfdcfox
Dec 13 '18 at 16:54
I could just imagine, there's a lot of excitement around it from this morning, the time it was announced. I think I haven't seen anything like this which is GA without releasing a beta in first place.
– Jayant Das
Dec 13 '18 at 16:55
That's because they've been secretly testing it for a year. I noticed it a few months ago and I wrote it off as some Aura oddity, but I've known about this for a while. Like you'll write a component that useslightning:button
, but if you debug it in the Lightning Debugger, it shows up as alightning-button
, basically a first-class citizen of Lightning, which struck me as odd.
– sfdcfox
Dec 13 '18 at 16:58
|
show 1 more comment
UPDATE
Just got an update that the Spring '19 pre-release signup link is now live. You can access it on this link.
You are getting this error because the LWC project expects a version 45.0 (Spring '19 pre-release org), whereas the current DE sandboxes are still on version 44.0 (Winter '19).
You will need to signup for the Spring '19 pre-release DE Org to be used as DevHub for this module. And as of now that's not available, unless you already have a sandbox which has been upgraded to Spring '19.
I was in same situation this morning and found out that the signup for pre-release DE Org is not live yet. Refer to this tweet for response from Salesforce.
UPDATE
Just got an update that the Spring '19 pre-release signup link is now live. You can access it on this link.
You are getting this error because the LWC project expects a version 45.0 (Spring '19 pre-release org), whereas the current DE sandboxes are still on version 44.0 (Winter '19).
You will need to signup for the Spring '19 pre-release DE Org to be used as DevHub for this module. And as of now that's not available, unless you already have a sandbox which has been upgraded to Spring '19.
I was in same situation this morning and found out that the signup for pre-release DE Org is not live yet. Refer to this tweet for response from Salesforce.
edited Dec 13 '18 at 17:11
answered Dec 13 '18 at 16:49
Jayant DasJayant Das
12.8k2723
12.8k2723
Yeah, the trailhead kind of fails to mention this, as far as I can tell.
– sfdcfox
Dec 13 '18 at 16:51
@sfdcfox True. I actually was exactly in this situation when went back and realized I need a Spring '19 org for this module. Then while signing up, couldn't do so.
– Jayant Das
Dec 13 '18 at 16:52
Yeah, I was just trying a trailhead this morn. I think LWC is going to change the way we do things, but a bit annoying they announced it without specifying special hoops
– sfdcfox
Dec 13 '18 at 16:54
I could just imagine, there's a lot of excitement around it from this morning, the time it was announced. I think I haven't seen anything like this which is GA without releasing a beta in first place.
– Jayant Das
Dec 13 '18 at 16:55
That's because they've been secretly testing it for a year. I noticed it a few months ago and I wrote it off as some Aura oddity, but I've known about this for a while. Like you'll write a component that useslightning:button
, but if you debug it in the Lightning Debugger, it shows up as alightning-button
, basically a first-class citizen of Lightning, which struck me as odd.
– sfdcfox
Dec 13 '18 at 16:58
|
show 1 more comment
Yeah, the trailhead kind of fails to mention this, as far as I can tell.
– sfdcfox
Dec 13 '18 at 16:51
@sfdcfox True. I actually was exactly in this situation when went back and realized I need a Spring '19 org for this module. Then while signing up, couldn't do so.
– Jayant Das
Dec 13 '18 at 16:52
Yeah, I was just trying a trailhead this morn. I think LWC is going to change the way we do things, but a bit annoying they announced it without specifying special hoops
– sfdcfox
Dec 13 '18 at 16:54
I could just imagine, there's a lot of excitement around it from this morning, the time it was announced. I think I haven't seen anything like this which is GA without releasing a beta in first place.
– Jayant Das
Dec 13 '18 at 16:55
That's because they've been secretly testing it for a year. I noticed it a few months ago and I wrote it off as some Aura oddity, but I've known about this for a while. Like you'll write a component that useslightning:button
, but if you debug it in the Lightning Debugger, it shows up as alightning-button
, basically a first-class citizen of Lightning, which struck me as odd.
– sfdcfox
Dec 13 '18 at 16:58
Yeah, the trailhead kind of fails to mention this, as far as I can tell.
– sfdcfox
Dec 13 '18 at 16:51
Yeah, the trailhead kind of fails to mention this, as far as I can tell.
– sfdcfox
Dec 13 '18 at 16:51
@sfdcfox True. I actually was exactly in this situation when went back and realized I need a Spring '19 org for this module. Then while signing up, couldn't do so.
– Jayant Das
Dec 13 '18 at 16:52
@sfdcfox True. I actually was exactly in this situation when went back and realized I need a Spring '19 org for this module. Then while signing up, couldn't do so.
– Jayant Das
Dec 13 '18 at 16:52
Yeah, I was just trying a trailhead this morn. I think LWC is going to change the way we do things, but a bit annoying they announced it without specifying special hoops
– sfdcfox
Dec 13 '18 at 16:54
Yeah, I was just trying a trailhead this morn. I think LWC is going to change the way we do things, but a bit annoying they announced it without specifying special hoops
– sfdcfox
Dec 13 '18 at 16:54
I could just imagine, there's a lot of excitement around it from this morning, the time it was announced. I think I haven't seen anything like this which is GA without releasing a beta in first place.
– Jayant Das
Dec 13 '18 at 16:55
I could just imagine, there's a lot of excitement around it from this morning, the time it was announced. I think I haven't seen anything like this which is GA without releasing a beta in first place.
– Jayant Das
Dec 13 '18 at 16:55
That's because they've been secretly testing it for a year. I noticed it a few months ago and I wrote it off as some Aura oddity, but I've known about this for a while. Like you'll write a component that uses
lightning:button
, but if you debug it in the Lightning Debugger, it shows up as a lightning-button
, basically a first-class citizen of Lightning, which struck me as odd.– sfdcfox
Dec 13 '18 at 16:58
That's because they've been secretly testing it for a year. I noticed it a few months ago and I wrote it off as some Aura oddity, but I've known about this for a while. Like you'll write a component that uses
lightning:button
, but if you debug it in the Lightning Debugger, it shows up as a lightning-button
, basically a first-class citizen of Lightning, which struck me as odd.– sfdcfox
Dec 13 '18 at 16:58
|
show 1 more comment
Thanks for contributing an answer to Salesforce Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f242503%2fthe-max-apiversion-is-44-0-error%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
The Spring '19 pre-release signup is now live. Updated the link in the answer.
– Jayant Das
Dec 13 '18 at 17:13