search

forcedotcom / cli

Salesforce CLI
https://developer.salesforce.com/docs/atlas.en-us.sfdx_cli_reference.meta/sfdx_cli_reference/
BSD 3-Clause "New" or "Revised" License
494 stars 78 forks source link

`force:package:version:create` is failing for all Custom Metadata records with Invalid Cross Reference Id. #1582

Closed chriskarpyszyn closed 2 years ago

chriskarpyszyn commented 2 years ago

ISV Partners have a critical problem with the SFDX CLI to create 2GP packages.

Today, packaging with force:package:version:create started failing for all Custom Metadata records with the error Invalid Cross Reference Id

The error has been reported by others attempting to package today on SFXD. No changes to the code caused the error.

Blocked and need help ASAP.

github-actions[bot] commented 2 years 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.

bbrummer commented 2 years ago

Exact same issue here. Our last successful build was June 20th (two days ago). It began failing for us yesterday, including the exact same code revision we packaged successfully on the 20th.

We hadn't updated SFDX tooling in between, so this is most likely a Salesforce side bug. -AFAIK the SFDX cli does very little of the actual packaging and validation work, most all of that is handed on the Salesforce side.

ClayChipps commented 2 years ago

We are also now experiencing this issue, but as @bbrummer mentioned, this looks to be on the Salesforce "server" side, not on the CLI.

m-rodriguez7 commented 2 years ago

Same here ... we are unable to create new package versions. The issue started last night. I have been able to recreate the problem with the dreamhouse app (see public repo linked below). I added a custom metadata record and proceeded to create a new package version. The following error is thrown for custom metadata records.

https://gitlab.com/mrodriguez1232/dreamhouse-lwc

ERROR running force:package:version:create: Support_Tier.Bronze: An unexpected error occurred. Please include this ErrorId if you contact support: 1106878027-189513 (1860077356)

Salesforce CLI Version: sfdx-cli/7.155.1

jwalke commented 2 years ago

I'm seeing this as well with our Unlocked packages. This is blocking our ability to package/install code internally into our sandboxes and production environments.

shetzel commented 2 years ago

Thanks for posting. It's a known issue and the team is working to revert the server code. I'm not aware of a public KI post yet but I'll post here if I see one.

chriskarpyszyn commented 2 years ago

https://partners.salesforce.com/_ui/core/chatter/groups/GroupProfilePage?g=0F93A000000HXAq&fId=0D54V00006CgNsz

Information Regarding 2GP Package Version Creation Issues (June, 22 2022) It has been determined that a regularly scheduled Summer '22 maintenance release (238.10) contained a regression that may cause some 2GP package:version:create requests to fail. NOTE: This issue only affects package version creation. Package upgrades and installations should not be affected in any way. Salesforce R&D is in the final stages of testing a fix. We're working to get this into an emergency patch release ASAP. Once the patch is approved it will take approximately 24-72 hours to be deployed to all pods. A KI for this issue is being created. I'll modify this post to include the link once it's available. If you have any questions, please respond to this post and mention @Vivek Chawla (Salesforce.com). FYI: @AppExchange & ISV Technical Enablement @Dileep Burki (salesforce.com) @Vydianath Iyer (Salesforce.com)

github-actions[bot] commented 2 years ago

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.

keithrogersfenergo12 commented 2 years ago

We are also facing the same issue. I have raised a case with Salesforce to help increase the priority.

user851 commented 2 years ago

I think there may be another facet to this issue. It appears that when a package with custom metadata types is declared as a dependency in the sfdx-project.json file the package that depends on it also can not have a version created. It fails stating

An error occurred while trying to install a package dependency, ID (packageID): The data you were trying to access could not be found. It may be due to another user deleting the data or a system error. If you know the data is not deleted but cannot access it, please look at our support page.

At this point it's a little difficult to test this as we can't create a test package version with metadata, but from what I'm seeing this may also need to be investigated

mlabrosse6 commented 2 years ago

We have also started experiencing this issue yesterday and cannot created a new package version. Salesforce Support Case created to help push as priority.

mohanraj-svmx commented 2 years ago

We have also started experiencing this issue yesterday and cannot created a new package version. Salesforce Support Case created to help push as priority. It was success on 20th June, without code change we initiated which was failing from yesterday.

Gontsov commented 2 years ago

We have the same issue, started on 21 June

VivekMChawla commented 2 years ago

Information Regarding 2GP Package Version Creation Issues (June, 22 2022)

IMPORTANT: This will be the ONLY post I make here in GitHub. Please see one of the following threads for further updates.

Hello everyone. My name is Vivek M. Chawla. I'm a Platform Expert for Packaging at Salesforce and work closely with the product and engineering teams.

It has been determined that a regularly scheduled Summer '22 maintenance release (238.10) released on June 20, 2022, contained a regression that may cause some 2GP package:version:create requests to fail.

This issue only affects package version creation. Package upgrades and installations should not be affected

Salesforce R&D has designed a fix for this issue. We're working to get this into an emergency patch release ASAP. Once the patch is approved it will take approximately 24-72 hours to be deployed to all pods.

Please see one of the following threads for further updates.

chriskarpyszyn commented 2 years ago

At 6:40pm EST I was able to create a package.

user851 commented 2 years ago

At 6:40pm EST I was able to create a package.

Lucky You!

Patch roll-out status is here

shetzel commented 2 years ago

This should now be fixed.