@salesforce/core
Version:
Core libraries to interact with SFDX projects, orgs, and APIs.
99 lines (52 loc) • 2.56 kB
Markdown
is not properly formatted.
- If attempting to create a scratch org then re-authorize. Otherwise create a new scratch org.
Failed to decipher auth data. reason: %s.
Unsupported Operating System: %s
Unable to find required security software: %s
Unable to execute security software: %s
Failed to get the password after %i retries.
A password is required.
Unable to get or set a keychain value without a service name.
Unable to get or set a keychain value without an account name.
User canceled authentication.
Failed to create a password in the keychain.
The service and account specified in %s do not match the version of the toolbelt.
- Check your toolbelt version and re-auth.
Invalid file permissions for secret file: %s
- Ensure the file %s has the file permission octal value of %s.
Could not find password.
%s
- Ensure a valid password is returned with the following command: [%s]
Command failed with response:
%s
- Determine why this command failed to set an encryption key for user %s: [%s].
We’ve encountered an error with the Mac keychain being out of sync with your `sfdx` credentials. To fix the problem, sync your credentials by authenticating into your org again using the auth commands.
The SF_CRYPTO_V2 environment variable was set to "false" but a v2 crypto key was detected. v1 crypto can only be used with a v1 key. Unset the SF_CRYPTO_V2 environment variable.
SF_CRYPTO_V2 was set to "true" but a v1 crypto key was detected. v2 crypto can only be used with a v2 key. To generate a v2 key:
1. Logout of all orgs: `sf org logout --all`
2. Delete the sfdx keychain entry (account: local, service: sfdx). If `SF_USE_GENERIC_UNIX_KEYCHAIN=true` env var is set, you can delete the `key.json` file.
3. Set `SF_CRYPTO_V2=true` env var.
4. Re-Authenticate with your orgs using the CLI org login commands.
The encrypted data