I’m experiencing a CloudKit Dashboard failure that is preventing me from releasing an app update, and I’m looking for help escalating it to the team responsible for CloudKit’s schema-management services.
Symptoms
For one CloudKit container, both Development and Production are affected:
- Record Types cannot be displayed.
- Indexes returns an Internal Error.
- Deploy Schema to Production also returns an Internal Error.
- Schema export to .ckdb succeeds.
- The Logs section is accessible, with no obvious errors.
Other containers in the same developer account work normally. My app appears to continue operating against both environments.
Apple System Status reports CloudKit as operational.
Diagnostic information
Safari’s Web Inspector reports HTTP 429 responses for the diff and recordTypes requests.
The response includes:
- code: 429
- message: too-many-requests
- reason: Internal error
- requestUuid: 47b6b1be-ce3c-41a4-bd3d-6f5c38ec875c
Impact
I added a new Core Data entity, CD_ShipsPaperEntity. It is present in the Development schema export but absent from Production.
I opened CloudKit Dashboard to deploy the schema change and discovered the problem. I cannot deploy the schema required for my next app release.
I have exported both schemas and confirmed that their existing shared record types are consistent.
This appears to be a container-specific CloudKit Dashboard or backend failure, rather than an application-code issue. A sample application would not necessarily reproduce a failure in the Dashboard’s own schema-management requests.
Could an Apple engineer investigate the request UUID and advise how to get the affected container’s schema deployment working again?
Thanks
