That's good to know, thank you. The error is still there on the simulator in beta 2 for me: com.apple.coredata.cloudkit.zone:defaultOwner = <CKError 0x600002d983f0: "Internal Error" (1/5000); "Failed to sync user keys">

Yes, still not working in the simulator but working on a physical device.

Thanks for the update. Can confirm that if it's an existing simulator in use from an earlier build you do have to 'erase all contents & settings' and start fresh.

Not working for me in beta 5 at all. This all started with beta 4 (see my post below).

Yes, I have this issue in the Development Environment with my app... and in the Production Environment if I download and use my publicly available App Store version, but running on an iOS15 device. It broke with beta 4 and is still broken.

Same in beta 5. This is very, very frustrating.

Installed my App Store app on a new device running iOS beta 5 to see what happens. All data syncs down to it just fine except for data created on the main device since beta 4. There is a clear temporal delineation. Creating a new item 'starts' an upload but nothing is uploaded and it eventually crashes. Sigh...

Here is my Feedback Assistant ticket number: FB9412346

And still not working properly in beta 5 for me: App Store app just doesn't sync any more; any new builds in Xcode on simulator & device report an authentication error despite being logged in, reset, etc. If this isn't sorted before the RC my users are going to be very, very upset with me!

Not for me. Still not working in simulators & devices (authentication error). Running my App Store version of my app on beta 5 results in no syncing at all - it 'starts' a sync... then nothing, nothing, nothing -> crash to springboard with no error. Ugh. Crash logs give no meaningful information. I've submitted a sysdiagnose to Apple and have a Feedback Assistant report here (FB9412346)

I'm seeing an attempt to sync... but nothing happens and then this appears in the console (despite the app being in the foreground the whole time): CoreData: CloudKit: CoreData+CloudKit: -[NSCloudKitMirroringDelegate executeMirroringRequest:error:]: <NSCloudKitMirroringDelegate: 0x6000015515c0>: Asked to execute request: <NSCloudKitMirroringExportRequest: 0x600002ed2a30> CBE1852D-7793-46B6-8314-A681D2038B38 2021-08-13 08:41:01.518422+1000 Somnus[11058:671570] [BackgroundTask] Background Task 68 ("CoreData: CloudKit Export"), was created over 30 seconds ago. In applications running in the background, this creates a risk of termination. Remember to call UIApplication.endBackgroundTask(_:) for your task in a timely manner to avoid this. 2021-08-13 08:41:03.519455+1000 Somnus[11058:671570] [BackgroundTask] Background Task 154 ("CoreData: CloudKit Scheduling"), was created over 30 seconds ago. In applications running in the background, this creates a risk of termination. Remember to call UIApplication.endBackgroundTask(_:) for your task in a timely manner to avoid this.

Excellent, thank you for the feedback and for submitting a report to Apple as well. I have had an engineer reach out but after sending them more information, I'm still waiting to hear back. It's not fixed in beta 6 (although I think this was a quick beta release) so fingers crossed for beta 7!!

I'm currently running an iOS15 beta 5 simulator after ingesting my backup data to Core Data (700MB) it shows "Finished processing analyzed history with 29581 metadata objects to create"... and nothing after that. Currently, it's sitting at 4GB of RAM consumed, which would have crashed a physical device ages ago. Something is broken with NSPersistentCloudkitContainer since beta 4.

I've also cross referenced your Feedback ID in mine. My Feedback ID for this is: FB9412346 (is there a way to view someone else's feedback?)

Thank you for commenting. This information is in my feedback (FB9412346) report. I have not received a reply from Apple in this report yet.