SFDX: Create New Project is not prompting for project type to create.

[cmdanner1982]

Summary

Salesforce extensions fail to load/activate when attempting to create SFDX project.

Steps To Reproduce:

1. Launch Visual Studio Code (User install) v1.94.2
2. Type >SFDX in search.
3. Select >SFDX:Create Project

Expected result

What should happen is you are met with an option to select Standard Project, Empty Project, or Analytics Project.

Actual result

Instead what happens is you see the 'Activating extensions..." displayed in the bottom-left corner, then it disappears and nothing else happens.

Additional information

Feel free to attach a screenshot.

Salesforce Extension Version in VS Code: 62.0.0

Salesforce CLI Version: 2.61.8

OS and version: Windows 11 22H2

VS Code version: 1.94.2

Most recent version of the extensions where this was working: Never. I work in IT Desktop Support, providing assistance to a contractor hired for Salesforce development work. We issued him an HP laptop to which he does not have local administrator rights to, and can not be given those rights per policy. MS VSC, Salesforce CLI and the Salesforce Extension Pack were installed under admin credentials but did not produce a different result.

[svc-idee-bot]

Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.

[peternhale]

@cmdanner1982 Would you mind providing a screenshot of the running extensions after "Activating extensions..." disappears.

Ctrl-Shift-P and type "Developer: Show Running Extensions"

Send the contents of "Developer: Startup Performance" The contents of that editor can be saved with Ctrl-S

[cmdanner1982]

Good afternoon, Peter,

I have a support call scheduled with the end user on Monday, 10/21. I’ll gather the requested information during the call and provide feedback afterward.

[cmdanner1982]

From my test machine that is experiencing the same outcome as the end-user:

chuckjonas.apex-pmd dbaeumer.vscode-eslint esbenp.prettier-vscode financialforce.lana redhat.vscode-xml salesforce.salesforce-vscode-slds salesforce.salesforcedx-einstein-gpt salesforce.salesforcedx-vscode salesforce.salesforcedx-vscode-apex salesforce.salesforcedx-vscode-apex-debugger salesforce.salesforcedx-vscode-apex-replay-debugger salesforce.salesforcedx-vscode-core salesforce.salesforcedx-vscode-expanded salesforce.salesforcedx-vscode-lightning salesforce.salesforcedx-vscode-lwc salesforce.salesforcedx-vscode-soql salesforce.salesforcedx-vscode-visualforce salesforce.sfdx-code-analyzer-vscode vignaeshrama.sfdx-package-xml-generator

startup_performace_report.txt

[peternhale]

@cmdanner1982 From what you have shared it shows that all of our extension have started up. What is it that I am missing? What is the expectation after "Activating extensions..." disappears?

[cmdanner1982]

The expectation is to be prompted for the options to select Standard Project, Empty Project, or Analytics Project. Instead, nothing happens and we are unable to create a new SFDX project.

[peternhale]

@cmdanner1982 Thank you.

[DavidWillsADS]

@cmdanner1982 Seeing the same thing. I received a new laptop for work, which required an install of VSC. After the install, I checked the environment variables, and installed the Salesforce Extensions. The same "Activating Extensions" notice you saw was at the bottom of my screen but no prompts occurred to create the project. I've checked my Running Extensions and see my Salesforce CLI Integration is stuck in Activating. I have installed VS Code version 1.94.2 and the old version 1.91.1, which is is up and running normally on my previous laptop. I've also tried to install previous versions of the Extension, but the result was the same.

[DavidWillsADS]

@cmdanner1982 I was able to get the Create Project feature working by installing version 60.0.0 of the Salesforce CLI Integration. I selected that specific version from within the Extension Pack. Hope this helps.

[cmdanner1982]

60.0.0

Thank you for the information! I’ll give that a try with our user during the scheduled support call later today and will provide feedback afterward.

[DavidWillsADS]

60.0.0

Thank you for the information! I’ll give that a try with our user during the scheduled support call later today and will provide feedback afterward.

Unfortunately, now I'm having issues Authorizing my Sandbox. Keep getting Authorization on Org Failed to run

[cmdanner1982]

60.0.0

Thank you for the information! I’ll give that a try with our user during the scheduled support call later today and will provide feedback afterward.

Unfortunately, now I'm having issues Authorizing my Sandbox. Keep getting Authorization on Org Failed to run

Downgrading to 60.0.0 did the trick for our user! No issues, so far. Thank You!

[git2gus[bot]]

This issue has been linked to a new work item: W-17038949

[peternhale]

@cmdanner1982 @DavidWillsADS I was able to reproduce the issue on a clean windows 11 VM. During startup of the Salesforce CLI extension, it checks to make sure that the Salesforce CLI is installed and is a minimum version of v2.

I realize that downgrading to v60 resolved the issue, but if you could try v62 again that would be appreciated. I would suggest uninstalling and installing the CLI as part of this exercise. Also, can you share how the CLI was installed in your machines; via Windows installer or npm.

I have logged a bug against for this issue and will start investigating the root cause.

[JoeyACS]

I tried downgrading to v60 and still does not work. I see "activating extensions" and nothing.

[peternhale]

@JoeyACS can you provide your config?

[JoeyACS]

@JoeyACS can you provide your config?

I'm not sure what you mean but here's Visual Studio about:

Version: 1.94.2 (user setup) Commit: 384ff7382de624fb94dbaf6da11977bba1ecd427 Date: 2024-10-09T16:08:44.566Z Electron: 30.5.1 ElectronBuildId: 10262041 Chromium: 124.0.6367.243 Node.js: 20.16.0 V8: 12.4.254.20-electron.0 OS: Windows_NT x64 10.0.22631

[DavidWillsADS]

@peternhale I just completely removed my instance of VS Code and then reinstalled 1.94.2.

My Environmental Variables:

I installed the Salesforce Extension Pack version 62.0.0 , but don't see the Salesforce CLI Integration in my running Extensions, so I installed the Salesforce Extension Pack (Expanded) version 62.0.0. The CLI is stuck in Activating. However, I do see the SFDX Prompts, but they don't do much. I continuously get the "Activating Extensions" with no action.

[peternhale]

@DavidWillsADS can you open a command prompt and run sf version --verbose. Please share the results.

[DavidWillsADS]

@peternhale

@DavidWillsADS can you open a command prompt and run sf version --verbose. Please share the results.

[peternhale]

@DavidWillsADS It appears that sf CLI is not installed. It can be installed with either Windows installer or via npm. One can download the installer from Salesforce CLI or install it using NPM. Using npm requires the installation of nodejs.

npm install @salesforce/cli -g

[DavidWillsADS]

@DavidWillsADS It appears that sf CLI is not installed. It can be installed with either Windows installer or via npm. One can download the installer from Salesforce CLI or install it using NPM. Using npm requires the installation of nodejs.

npm install @salesforce/cli -g

New laptop, I guess I missed that. Installing now. Thank you.

[peternhale]

@DavidWillsADS It appears that sf CLI is not installed. It can be installed with either Windows installer or via npm. One can download the installer from Salesforce CLI or install it using NPM. Using npm requires the installation of nodejs. npm install @salesforce/cli -g

New laptop, I guess I missed that. Installing now. Thank you.

@DavidWillsADS that's how I found out, new Windows VM and forgot to install CLI.

[DavidWillsADS]

@peternhale That worked! Thank you very much.

[peternhale]

@DavidWillsADS you are welcome.

[cmdanner1982]

@cmdanner1982 @DavidWillsADS I was able to reproduce the issue on a clean windows 11 VM. During startup of the Salesforce CLI extension, it checks to make sure that the Salesforce CLI is installed and is a minimum version of v2.

I realize that downgrading to v60 resolved the issue, but if you could try v62 again that would be appreciated. I would suggest uninstalling and installing the CLI as part of this exercise. Also, can you share how the CLI was installed in your machines; via Windows installer or npm.

I have logged a bug against for this issue and will start investigating the root cause.

Good evening, @DavidWillsADS. We attempted upgrades to every version above 60.0.0, but each upgrade caused issues—specifically, it would get stuck on "activating extensions" without offering options for Standard Project, etc.

Additionally, we're now facing a new issue even with version 60.0.0. When our user tries connecting to their sandbox environment at "https://ca-volunteers--svffull.sandbox.my.salesforce.com/," they receive the following error: "sf org:login --alias svffull --instance-url https://ca-volunteers--svffull.sandbox.my.salesforce.com/ --set-default ended with error spawn sf ENOENT."

According to Salesforce documentation, this error typically indicates that the Salesforce CLI isn’t installed. However, we have confirmed that it is installed in both C:\Program Files\sf and C:\Program Files\Salesforce CLI. We removed it from C:\Program Files\sf, leaving only the C:\Program Files\Salesforce CLI location, but the error remains. I also tried copying the CLI files to %LOCALAPPDATA%\sf and created firewall/Defender exclusions, yet the issue persists.

[cmdanner1982]

Good morning Salesforce Developer Support,

Just wanted to check-in and see if there are any updates or guidance that could be helpful to resolve this issue for our end user?

@cmdanner1982 @DavidWillsADS I was able to reproduce the issue on a clean windows 11 VM. During startup of the Salesforce CLI extension, it checks to make sure that the Salesforce CLI is installed and is a minimum version of v2. I realize that downgrading to v60 resolved the issue, but if you could try v62 again that would be appreciated. I would suggest uninstalling and installing the CLI as part of this exercise. Also, can you share how the CLI was installed in your machines; via Windows installer or npm. I have logged a bug against for this issue and will start investigating the root cause.

Good evening, @DavidWillsADS. We attempted upgrades to every version above 60.0.0, but each upgrade caused issues—specifically, it would get stuck on "activating extensions" without offering options for Standard Project, etc.

Additionally, we're now facing a new issue even with version 60.0.0. When our user tries connecting to their sandbox environment at "https://ca-volunteers--svffull.sandbox.my.salesforce.com/," they receive the following error: "sf org:login --alias svffull --instance-url https://ca-volunteers--svffull.sandbox.my.salesforce.com/ --set-default ended with error spawn sf ENOENT."

According to Salesforce documentation, this error typically indicates that the Salesforce CLI isn’t installed. However, we have confirmed that it is installed in both C:\Program Files\sf and C:\Program Files\Salesforce CLI. We removed it from C:\Program Files\sf, leaving only the C:\Program Files\Salesforce CLI location, but the error remains. I also tried copying the CLI files to %LOCALAPPDATA%\sf and created firewall/Defender exclusions, yet the issue persists.

Good morning Salesforce Developer Support,

Just wanted to check-in and see if there are any updates or guidance that could be helpful to resolve this issue for our end user?

[catmac42]

Just chipping in to say I'm having the same issue. I have a new laptop for work, and am installing everything required. When I try to Create New Project With Manifest, no dialogue appears to allow me to name it.

I followed the advice above to downgrade the CLI integration extension to Version 60.0.0, which solved the new project creation issue. But now, as with @DavidWillsADS above, I'm getting the same error when trying to authorise an org.

I upgraded the CLI integration back to Version 62.0.0, still no luck. I will try to uninstall and reinstall the CLI for Windows tomorrow, as I don't have admin access on my PC.