The max apiVersion is 44.0 error











up vote
2
down vote

favorite
1












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







share|improve this question
























  • The Spring '19 pre-release signup is now live. Updated the link in the answer.
    – Jayant Das
    1 hour ago















up vote
2
down vote

favorite
1












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







share|improve this question
























  • The Spring '19 pre-release signup is now live. Updated the link in the answer.
    – Jayant Das
    1 hour ago













up vote
2
down vote

favorite
1









up vote
2
down vote

favorite
1






1





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







share|improve this question















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






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 1 hour ago









Jayant Das

11.4k2523




11.4k2523










asked 1 hour ago









Art S

134




134












  • The Spring '19 pre-release signup is now live. Updated the link in the answer.
    – Jayant Das
    1 hour ago


















  • The Spring '19 pre-release signup is now live. Updated the link in the answer.
    – Jayant Das
    1 hour ago
















The Spring '19 pre-release signup is now live. Updated the link in the answer.
– Jayant Das
1 hour ago




The Spring '19 pre-release signup is now live. Updated the link in the answer.
– Jayant Das
1 hour ago










1 Answer
1






active

oldest

votes

















up vote
5
down vote



accepted










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.






share|improve this answer























  • Yeah, the trailhead kind of fails to mention this, as far as I can tell.
    – sfdcfox
    1 hour ago










  • @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
    1 hour ago










  • 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
    1 hour ago










  • 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
    1 hour ago










  • 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
    1 hour ago











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',
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
});


}
});














draft saved

draft discarded


















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








up vote
5
down vote



accepted










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.






share|improve this answer























  • Yeah, the trailhead kind of fails to mention this, as far as I can tell.
    – sfdcfox
    1 hour ago










  • @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
    1 hour ago










  • 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
    1 hour ago










  • 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
    1 hour ago










  • 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
    1 hour ago















up vote
5
down vote



accepted










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.






share|improve this answer























  • Yeah, the trailhead kind of fails to mention this, as far as I can tell.
    – sfdcfox
    1 hour ago










  • @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
    1 hour ago










  • 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
    1 hour ago










  • 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
    1 hour ago










  • 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
    1 hour ago













up vote
5
down vote



accepted







up vote
5
down vote



accepted






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.






share|improve this answer














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.







share|improve this answer














share|improve this answer



share|improve this answer








edited 1 hour ago

























answered 1 hour ago









Jayant Das

11.4k2523




11.4k2523












  • Yeah, the trailhead kind of fails to mention this, as far as I can tell.
    – sfdcfox
    1 hour ago










  • @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
    1 hour ago










  • 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
    1 hour ago










  • 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
    1 hour ago










  • 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
    1 hour ago


















  • Yeah, the trailhead kind of fails to mention this, as far as I can tell.
    – sfdcfox
    1 hour ago










  • @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
    1 hour ago










  • 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
    1 hour ago










  • 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
    1 hour ago










  • 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
    1 hour ago
















Yeah, the trailhead kind of fails to mention this, as far as I can tell.
– sfdcfox
1 hour ago




Yeah, the trailhead kind of fails to mention this, as far as I can tell.
– sfdcfox
1 hour ago












@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
1 hour ago




@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
1 hour ago












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
1 hour ago




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
1 hour ago












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
1 hour ago




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
1 hour ago












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
1 hour ago




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
1 hour ago


















draft saved

draft discarded




















































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.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • 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.




draft saved


draft discarded














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





















































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







-

Popular posts from this blog

What visual should I use to simply compare current year value vs last year in Power BI desktop

Image
0 I have column SubToBind that shows current year ratio and column PY SubToBind which shows previous year ratio. How can I simply create a card that would be displaying them both in a nice way? Something like that: I cannot achieve that with regular card, I also tried Card with States by OKViz but also unable to see both values. In KPI visual - I dont like the word "Goal", it will confuse end users. Are there any cards or other visuals that would do the job? Thanks powerbi dax powerbi-embedded share | improve this question edited Jun 11 '18 at 20:11 Oleg ...
Read more

How to ignore python UserWarning in pytest?

Image
up vote 1 down vote favorite I am using openpyxl for parsing .xlsm files, and pytest for testing. When I open a file, I get the: OpenPyxl -> UserWarning: Data Validation extension is not supported and will be removed That is not really a problem bcs. program works and I can't change the .xlsm file to fix that. But... When I run pytest with something like: def test_wrong_file_format(): assert check_excel(open_excel('file.xlsm')) == True I will get the warning i mentioned altought check_excel(open_excel('file.xlsm')) returns True and the test should suceed... Is there a nice way to tell the pytest that "It's not a bug it's a feature" and tests should pass even when they get this warning? Is there other way than using something like: with pytest.warns(UserWarning): ...
Read more

Alexandru Averescu

Image
Alexandre Averescu Alexandru Averescu Naissance 3 avril 1859 Babele, Ismail  (ro) près de Izmaïl (principauté de Moldavie) Décès 2 octobre 1938 (à 79 ans) [ 1 ] Bucarest Origine   Roumanie Arme cavalerie Grade Maréchal Années de service 1901-1917 Commandement chef d'état-major général 2 e  armée 3 e  armée Groupe d'armée sud armée du Danube Conflits Guerre russo-turque de 1877-1878 Deuxième guerre balkanique Première Guerre mondiale Faits d'armes Bataille de Turtucaia/Tutrakan Bataille de Mărăști Distinctions Autres fonctions 3 fois président du Conseil des ministres ministre des Affaires étrangères ministre sans portefeuille conseiller de la Couronne modifier   Alexandre Averescu (en roumain : Alexandru Averescu .mw-parser-output .prononciation>a{background:url("//upload.wikimedia.org/wikipedia/commons/thumb/8/8a/Loudspeaker.svg/11px-Loudspeaker.svg.png")center ...
Read more