Scratch org disappears from list after generating password
See original GitHub issueSummary
When I generate a password for a scratch org, the scratch org disappears from force:org:list
and force:org:list --all
. It remains accessible via its alias, but doesn’t appear in any lists.
Steps To Reproduce:
- Create a scratch org
- Run
force:org:list
and see the scratch org listed - Reset the password
sfdx force:user:password:generate --targetusername MyAlias --targetdevhubusername MyDevHub
- Run
force:org:list
and see the scratch org no longer present
Expected result
Password reset in scratch org, remains in list
Actual result
Scratch org disappears from list
Workaround:
Find the JSON file generated for the scratch org. Remove the properties userId
and password
, and save. See the scratch org reappear in force:org:list
Additional information
SFDX CLI Version(to find the version of the CLI engine run sfdx --version): sfdx-cli/7.92.0-88320113e7 win32-x64 node-v14.15.4
SFDX plugin Version(to find the version of the CLI plugin run sfdx plugins --core) @oclif/plugin-autocomplete 0.3.0 (core) @oclif/plugin-commands 1.3.0 (core) @oclif/plugin-help 3.2.2 (core) @oclif/plugin-not-found 1.2.4 (core) @oclif/plugin-plugins 1.10.0 (core) @oclif/plugin-update 1.4.0-2 (core) @oclif/plugin-warn-if-update-available 1.7.0 (core) @oclif/plugin-which 1.0.3 (core) @salesforce/sfdx-trust 3.6.0 (core) alias 1.1.8 (core) auth 1.4.10 (core) config 1.2.6 (core) generator 1.1.5 (core) salesforcedx 51.4.0 (core) ├─ limits 1.0.4 (core) ├─ schema 1.0.4 (core) ├─ apex 0.1.4 (core) ├─ custom-metadata 1.0.11 (core) ├─ org 1.3.3 (core) ├─ templates 51.3.0 (core) ├─ user 1.2.0 (core) ├─ @salesforce/sfdx-plugin-lwc-test 0.1.7 (core) └─ salesforce-alm 51.4.0 (core) sfdx-cli 7.92.0 (core) telemetry 1.1.1 (core)
OS and version: Windows 10 Pro x64 20H2
Issue Analytics
- State:
- Created 2 years ago
- Comments:15 (5 by maintainers)
@toddhalfpenny put yourself a reminder to
plugins:uninstall org
once the fix ships on (sometime on 4/1) so you get back to “normal”Thanks for the fix @mshanemc - all good now for me with the updated plugin