Open epavlic-revenue opened 3 weeks ago
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 @epavlic-revenue :wave: None of the versions of sf
you shared match the latest release.
Shared: 2.42.6
Latest: 2.45.6
Update to the latest version of Salesforce CLI (docs) and confirm that you're still seeing your issue.
You can also try the rc
and nightly
releases! (docs)
After updating, share the full output of sf version --verbose --json
{
"architecture": "darwin-arm64",
"cliVersion": "@salesforce/cli/2.45.6",
"nodeVersion": "node-v20.5.1",
"osVersion": "Darwin 23.5.0",
"rootPath": "/opt/homebrew/lib/node_modules/@salesforce/cli",
"shell": "zsh",
"pluginVersions": [
"@oclif/plugin-autocomplete 3.1.2 (core)",
"@oclif/plugin-commands 4.0.2 (core)",
"@oclif/plugin-help 6.1.0 (core)",
"@oclif/plugin-not-found 3.2.2 (core)",
"@oclif/plugin-plugins 5.2.2 (core)",
"@oclif/plugin-search 1.1.1 (core)",
"@oclif/plugin-update 4.3.3 (core)",
"@oclif/plugin-version 2.2.2 (core)",
"@oclif/plugin-warn-if-update-available 3.1.4 (core)",
"@oclif/plugin-which 3.2.1 (core)",
"@salesforce/cli 2.45.6 (core)",
"apex 3.1.14 (core)",
"auth 3.6.17 (core)",
"data 3.4.3 (core)",
"deploy-retrieve 3.8.4 (core)",
"devops-center 1.2.10 (user) published 34 days ago (Thu May 09 2024) (latest is 1.2.14)",
"info 3.3.4 (core)",
"limits 3.3.10 (core)",
"marketplace 1.2.10 (core)",
"org 4.1.19 (core)",
"packaging 2.4.5 (core)",
"schema 3.3.10 (core)",
"settings 2.3.0 (core)",
"sobject 1.4.8 (core)",
"source 3.3.21 (core)",
"telemetry 3.3.12 (core)",
"templates 56.2.9 (core)",
"trust 3.7.4 (core)",
"user 3.5.11 (core)"
]
}
Is it a 1GP or 2GP package? Looks like you're mixing the commands. package1
are commands for 1GP. package
are commands for 2GP.
@shetzel It's a 1GP package, and package install
should be for either 1GP or 2GP. It used to work for 1GP, and it still does for older versions (for example, on my instance two versions or more behind last work, while the last one and the one before last do not). package1
has only version
create
, display
, list
.
Is this issue about the error message that you'd like improved or about propagation? The CLI team can enhance the error message but propagation is controlled by the server. Customer support could look into the propagation delays.
@shetzel If that's the distribution of responsibilities, I'm happy for the error message to be made clearer — The subscriber package version <version-id> is invalid
is not true, as the version has been valid for a day.
This issue has been linked to a new work item: W-16009913
Chiming in to say that this is also happening for me in Scratch Org Pooling. Over the weekend a new version of vlocity_cmt was released, which failed to install on scratch orgs with the exact same error message. As far as I'm able to see, the previous package version can get installed just fine, the CI pipeline I use didn't fail at the time the other one did, but keeps on running.
Summary
sf package install --package <version-id> --wait 30
outputsThe subscriber package version <version-id> is invalid, no subscriber package version record found
.sf package1 version list --target-org dev-hub
lists the<version-id>
.Trying to install manually gives a different error:
The version in question was packaged 1 day ago.
Expected result
If a package version exists in the
sf package1 version list --target-org dev-hub
it should be propagated to Salesforce instances in under a day.Actual result
Package version appears not to have been propagated, and the error message is confusing.
System Information