NSPersistentCloudKitContainer export blocked account-wide by failing _pcs_data RecordDelete (BAD_REQUEST)

Question

Created 1w

Replies 1

Boosts 0

Participants 2

Since ~July 10, NSPersistentCloudKitContainer export has failed on every device on my iCloud account; import still works. In CloudKit Console → Logs (Production), the only failing operations are RecordDelete/RecordSave of record type pcs_data (error BAD_REQUEST) in the private com.apple.coredata.cloudkit.zone. No CD* app-record failures; the app schema is fully deployed to Production.

Advanced Data Protection is enabled on the account, so PCS keys are managed end-to-end on-device. This looks like a wedged PCS key state rather than an app/schema problem.

Tried with no effect: toggling ADP off/on, toggling iCloud Keychain, multiple reboots, app reinstall, extended foreground on Wi-Fi. Still failing after updating from iOS 27 Seed 3 to beta 4.

Is there a way to get the account's Protected Cloud Storage key state reset so export can resume? Happy to share the Feedback number and sysdiagnoses privately with an Apple engineer.

Answer 1

NavismareYachtLogistic OP

3h

Same issue here, filed as FB24150787. Two iOS devices (iPad Air 5th gen, iPhone 17 Pro, both 26.5.2), ADP enabled: every export fails with RecordSave → BAD_REQUEST, returnedRecordTypes _pcs_data, in com.apple.coredata.cloudkit.zone. Import still works. Device reboots and toggling the app's iCloud switch do not help. Interesting data point: the same app/account on a Mac whose sync state was set up fresh after the wedge exports fine — and CloudKit Console shows an unrelated user of our app with the exact same failure signature. So this looks account/PCS-side, not app-side. The device-side PCS identity is valid per pcsstatus.txt, pointing to a server-side inconsistency in the zone's _pcs_data manifest.