CloudKit Console: Deploy Schema Changes to Production fails with HTTP 500 "internal-error"

App & System Services iCloud
anthai OP
Created
Replies 1
Boosts 0
Views 454
Participants 2

I'm hitting the same issue. Deploying the Development schema to Production fails every time with HTTP 500 internal-error on the …/schema/<developmentSchemaId>/promote request. It fails from both the "Changes" tab and the "Diff View" tab of the Confirm Deployment dialog. detailedMessage is undefined.

  • Filed as FB25280547, with the container ID, request UUIDs and screenshots.
  • Example requestUuid: 7f4aec62-6ead-4e86-8784-77be751d3622
  • The diff is purely additive: Core Data / NSPersistentCloudKitContainer fields such as _ckAsset assets, CD_moveReceipt and one new string field, plus QUERYABLE indexes on ___recordID. No type changes and no removals.
  • I tried refreshing, re-signing in, and a private window. It still fails.

This blocks our App Store release because the new build writes a field that Production doesn't have yet. Could someone from the CloudKit Console team take a look? Thank you!

Replies  1
Boosts 0
Views  454
Participants  2
DTS Engineer OP
Apple

Thanks for reporting the issue and filing the feedback report. From the server side log, we see something like this: "... promotion of type changes field ID." If I'd trust the log, it seems that the schema you would deploy contains a change that the CloudKit server doesn't allow, and CloudKit Console wasn't able to detect it and show you the detail.

You can try to export the CloudKit schemas of your development and production environments using the Export Schema... button on the sidebar in CloudKit Console, and then do a comparison to hopefully find something that CloudKit Console missed.

Best,
——
Ziqiao Chen
 Worldwide Developer Relations.