Can't create package version with coverage & dependency: invalid attribute 'subscriberPackageId' at line 1, column 535 #2912
Labels
investigating
We're actively investigating this issue
owned by another team
The Salesforce CLI team does not own this work but will pass on the information to the correct team.
validated
Version information for this issue has been validated
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. |
github-actions
bot
added
the
validated
|
I am having this same issue. I was trying to create a new package using sf-cli 2gp package creation. As of 2024-06-11, it seems that package creation began to create packages against API version 61.0. However to be backwards compatible with some dev orgs that are on 60.0, I've also added Once this is added however, package creation fails with this error message. |
|
could someone run the command with Also, if someone could try on an older sf like v2.36.8 thanks for reporting!
|
Here's what I see after updating to 2.36.8 and then running this command i see a stack trace here Here's the full log of that command |
cristiand391
added
the
owned by another team
|
We have determined that the issue you reported exists in code owned by another team that uses only the official support channels. To ensure that your issue is addressed, open an official Salesforce customer support ticket with a link to this issue. We encourage anyone experiencing this issue to do the same to increase the priority. We will keep this issue open for the community to collaborate on. |
|
thank you, @Vincent-Ip! the packaging team is investigating this issue. |
dschibster
changed the title
|
I got word back from my case. As it looks, there's two things at work separately here:
The build fails because the scratch org uses an org shape of the current release, but tries to use the previous version, causing a mismatch. As per the case comments, using a separate scratch org definition for the purposes of building where the relase version is not set to "previous" this should work. I have yet to try this out but will do so next week. Maybe @Vincent-Ip you are able to do so earlier. |
|
@dschibster I'll give this a try, but the explanation doesn't sound 100% right to me. I got a similar response from my case, and i've got a meeting with them this afternoon. I'll let you know what I find out. |
|
@dschibster When I create a package without the "release":"previous" parameter in the scratch definition, this does "work" however, it creates a package based on the 61.0 release version. This will not be installable in orgs that have not been upgraded and is the reason why we added the "release":"previous" in the first place. On the call for my case, not much new information was given to me. The Packaging team is looking into the bug and have not respsonded directly to the Support Tech for my case. So I'm still just waiting. |
|
Well now after the weekend, the release version can't even be set to previous anymore. I'm just fearful that this will come up once again in the next release window if it isn't addressed properly. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
Running a multi-package setup with a pipeline utilizing flxbl.io, I have however tested this locally too and have run into the same result. Creating a package with coverage and dependency to a managed package (vlocity_cmt) results in the following cryptic error message:
Ensured that sf is up to date, and that sfdx-project.json uses API version 61. No change in results.
Steps To Reproduce
Unable to provide a repo due to the metadata being reserved for a client.
I can however show the structure this follows.
(This repo is in the process of decomposition)
The package that is currently failing is located in src-sales/core and has a dependency to vlocity_cmt (latest version)
The package contains the following metadata:
I ran the following command on my machine to get this result:
Expected result
The package should be created and receive a coverage report.
Actual result
Fails with error message mentioned above.
System Information
Using zsh on MacOS, the VM that also runs into this issue uses ubuntu and the flxbl.io GitHub container.]
{ "architecture": "darwin-arm64", "cliVersion": "@salesforce/cli/2.44.8", "nodeVersion": "node-v22.2.0", "osVersion": "Darwin 23.4.0", "rootPath": "/opt/homebrew/lib/node_modules/@salesforce/cli", "shell": "zsh", "pluginVersions": [ "@oclif/plugin-autocomplete 3.0.18 (core)", "@oclif/plugin-commands 3.3.4 (core)", "@oclif/plugin-help 6.0.22 (core)", "@oclif/plugin-not-found 3.1.10 (core)", "@oclif/plugin-plugins 5.1.3 (core)", "@oclif/plugin-search 1.0.24 (core)", "@oclif/plugin-update 4.2.14 (core)", "@oclif/plugin-version 2.1.2 (core)", "@oclif/plugin-warn-if-update-available 3.0.19 (core)", "@oclif/plugin-which 3.1.10 (core)", "@salesforce/cli 2.44.8 (core)", "apex 3.1.13 (core)", "auth 3.6.17 (core)", "data 3.4.3 (core)", "deploy-retrieve 3.8.3 (core)", "info 3.3.3 (core)", "limits 3.3.9 (core)", "marketplace 1.2.8 (core)", "org 4.1.14 (core)", "packaging 2.4.5 (user)", "schema 3.3.9 (core)", "settings 2.2.7 (core)", "signups 2.0.13 (link) /opt/homebrew/lib/node_modules/@salesforce/plugin-signups", "sobject 1.4.6 (core)", "source 3.3.18 (core)", "telemetry 3.3.11 (core)", "templates 56.2.9 (core)", "trust 3.7.3 (core)", "user 3.5.11 (core)", "sfdmu 4.32.2 (user)", "sfdx-git-delta 5.40.0 (user)" ] }Additional information
The first time this came up was when the new release was rolled out to us. We had a version mismatch in our packages, leading me to use
releaseVersion: previousin our scratch org definition. After this the installation on our lower instance (integration instance) started working again, the build of releasable packages however failed.What did work was the creation of beta packages. This error seems to be exclusive to release candidate packages.
The text was updated successfully, but these errors were encountered: