-
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
sf org login jwt -> TypeError: #2935
Comments
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. |
Hello @tparaiso 👋 It looks like you didn't include the full Salesforce CLI version information in your issue. A few more things to check:
Thank you! |
{ |
Same issue with this command : sf org list TypeError: Cannot read properties of undefined (reading 'entries') |
@tparaiso - I can't reproduce this using the same installed CLI version. We have tons of tests that use these commands as well and they run cleanly. This is specific to your environment so here's what I'd do:
|
@shetzel thank you very much, the command "sf plugins reset --hard" fix my issue. At my work I have had the same issue with our CI, we installed the previous version of the CLI and it's worked. There is something in the version of June 20 and plugins dependency. I will try the command tomorrow. Thanks ! |
I had the same problem. FWIW, I uninstalled plug-ins one at a time until |
We're experiencing the same error with this version as well |
@salesforce/cli/2.47.6 darwin-x64 node-v20.10.0 still has the issue |
It appears that a breakage has been introduced for plugins using the relatively old sfdx-core package, as noted in this pull request: forcedotcom/sfdx-core#1080. I managed to bypass the problem for debugging purposes by editing the core library. Specifically, I added a couple of lines exports.Lifecycle = Lifecycle;
Lifecycle.getInstance() above const cloneListeners = (listeners) => new Map(Array.from(listeners.entries())); in the lifecycleEvents.js part of the old version of the sfdx-core package. Please note that I am not proposing this as a solution, just sharing my findings. |
Thanks @mgalalm @jhgihub0 @seanhharrison - I verified that the bug exists with if anyone else can confirm the latest version of scanner is fixed as well that'd be great |
Unfortunately Im getting the same problem there :( Updating the scanner to version 4.3.0 havent helped :( |
Upgrading to latest version of sfdx/scanner is not working on my side. |
Same happens to me. Tried reinstalling or uninstalling the sacnner, but it doesnt work. |
If you are blocked, you can install an older version (that's worked for me on my other computer) : install @salesforce/cli@2.45.6 --global |
Hey @tparaiso @ReaperBeats @kevanmoothien @four4444PL - after a lot more testing, I'm still stumped. I've installed all of the versions, with the various node versions reported, and the problem keeps appearing for me when I use |
This issue has been linked to a new work item: W-16160024 |
It is working fine for me since I updated to the last version on CLI. |
Still an issue with latest stable
|
Hey @jhgihub0 - thanks for staying so on top of this change, you might have just missed our promotion to latest (I mean, missed it by minutes, this happened within the hour), which is now |
Yes, it seems to work with Thank you. |
Hi there guys, i´m facing the same issue with @salesforce/cli/2.49.7 win32-x64 node-v20.15.0 |
Summary
When the commande "sf org login jwt" is executed, it returns "TypeError: Cannot read properties of undefined (reading 'entries')"
Steps To Reproduce:
Expected result
You forget something normally
Actual result
TypeError: Cannot read properties of undefined (reading 'entries')
Additional information
Feel free to attach a screenshot.
Salesforce Extension Version in VS Code:
Salesforce CLI Version: Latest
@salesforce/cli/2.46.6 darwin-arm64 node-v20.9.0
OS and version:
MacOs Sonoma
The text was updated successfully, but these errors were encountered: