-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to authorize an org #2608
Comments
Hi @nkl14, could you please open your command palette, run |
Hi @nkl14 sorry for the delay. Can you open the command palette and run |
Hi @nkl14, There looks like a mismatch between your extensions version and the CLI command in the Output panel. Please try the following steps to get your extensions to a clean state:
Let me know if this solves your issue. |
hi both, I am afraid none of this solves my issue |
Hi @nkl14, |
Hmm, it's the same thing repeated over and over again. Is there anything above that? What's the 3 warnings and 1 issue? |
Can you please try restarting your computer? If that still doesn't resolve the issue, let me bring the issue to my team to review. |
I restarted my system thrice as I thought it would solve but unfortunately it didnt |
Ok thanks for letting me know. Let me see what suggestions my team has. |
Hi @nkl14,
|
This issue has not received a response in 7 days. It will auto-close in 7 days unless a response is posted. |
Hi @nkl14, I'm assuming this issue has been resolved and am closing it as completed. Feel free to reopen if you're still experiencing issues. Thanks! |
Hi @daphne-sfdc, I have been on holidays hence couldnt respond. I still get the same error. |
Hi @nkl14, Can you run Please also make sure you have the latest version of our extensions: v59.5.1. |
I am not sure what has gone wrong while updating cli that none of sf commands work for me |
Oh... so this is an issue with the CLI, not with the way the extensions are using the CLI. In that case, I would uninstall and reinstall the CLI. I don't know if you installed the CLI using the installer or using npm, or what CLI version you are using, so follow the link and do both the "macOS or Linux" section and the "npm" section. (Uninstall both sfdx v7 and sf v1/v2 for npm.). Uninstall instructions here: https://developer.salesforce.com/docs/atlas.en-us.sfdx_setup.meta/sfdx_setup/sfdx_setup_uninstall.htm Then reinstall the CLI using the installer at this link: https://developer.salesforce.com/tools/salesforcecli |
This issue has not received a response in 7 days. It will auto-close in 7 days unless a response is posted. |
@nkl14 Given that reinstalling the CLI does not solve the issue and the issue is also present when you run directly from the command line, I'm going to transfer the issue to the CLI team. Hopefully they will be able to help you identify and resolve the problem. Good luck! |
Hi @nkl14! |
Hello @nkl14 👋 It looks like you didn't include the full Salesforce CLI version information in your issue. A few more things to check:
Thank you! |
This issue has not received a response in 7 days. It will auto-close in 7 days unless a response is posted. |
Hey, sorry for the late reply, CLI team was mostly out in the last 2 weeks.
That's coming from oclif (CLI framework we use): The If you installed from npm, make sure to update to latest node LTS, or use the installers which includes its own node binary. |
Summary
I GET BELOW ERROR WHEN I TRY TO AUTHORISE ORG
TypeError: shellPath.at is not a function
Steps To Reproduce:
Expected result
It should have redirected to a web page to authorise an org
Actual result
Getting below error
TypeError: shellPath.at is not a function
Additional information
Salesforce Extension Version in VS Code: 59.1.2
SFDX CLI Version: 2.14.6
OS and version: mac OS Ventura 13.5
VS Code version: 1.83
The text was updated successfully, but these errors were encountered: