Simulator won't sync with CloudKit since Xcode 14

Question

Created Sep ’22

Replies 10

Boosts 3

Views 2.7k

Participants 8

I have a few apps that use Core Data & CloudKit to sync data to multiple devices. Everything was fine until I updated to Xcode 14. Now, although the apps work on an actual device, in the simulator, I get errors about "Failed to sync user keys" and it won't sync anything.

I haven't changed the code at all. It just suddenly won't work in the simulator. Since it does this for all apps, I have to believe it's something changed with the simulator?

2022-09-13 12:47:26.766223-0400 Time Since[8061:88974] [error] error: CoreData+CloudKit: -[NSCloudKitMirroringDelegate _performSetupRequest:]_block_invoke(1134): <NSCloudKitMirroringDelegate: 0x600003b540e0>: Failed to set up CloudKit integration for store: <NSSQLCore: 0x1219071d0> (URL: file:///Users/jon/Library/Developer/CoreSimulator/Devices/1990772E-CDF1-4A58-B454-E09D327B2182/data/Containers/Data/Application/3314EA95-4D86-4053-84B3-F1523A57E204/Library/Application%20Support/TimeSince.sqlite)
<CKError 0x600000cc1e60: "Partial Failure" (2/1011); "Failed to modify some record zones"; partial errors: {
	com.apple.coredata.cloudkit.zone:__defaultOwner__ = <CKError 0x600000cc2160: "Internal Error" (1/5000); "Failed to sync user keys">
}>

Boost

Answer 1

bss OP

Sep ’22

I pulled down Xcode 13, and verified CloudKit syncing works correctly in the simulator, so this appears to be something specific to Xcode 14.

1

Answer 2

Cardu6lis OP

Sep ’22

Same issue here.

0

Answer 3

cypher OP

Sep ’22

Had this problem all Summer. Still in GM. CloudKit has been non-functional on Simulator all Summer on Xcode 14 including the RC of Xcode 14. Today in particular, CloudKit production has also been mostly down, but that's on normal devices.

0

Answer 4

bss OP

Sep ’22

I don't know what happened, but I'm now getting the same errors with Xcode 13 so CloudKit won't work in any simulator. I opened a report and got a request to include a simctl diagnose, which I did, but haven't heard anything back since.

1

Answer 5

pableiros1 OP

Sep ’22

I have the same issue using Xcode 14.0.1, I downloaded Xcode 13 and it didn't work either. Only debugging with a physical device works

0

Answer 6

Nervus OP

Oct ’22

I found out it works in simulator only if you log in with a sandbox user id ( tester account ) - same user type one would use for in app purchase testing.

The weird thing is that it’s using a sandbox version of the store ( not the development one) and there’s no option in CloudKit database viewer to see that sandbox store …

I hope it goes back to working as I like having my phone app and simulator app having the same data .

I’m sure you know it’s works fine on the device - just in case you are blocked by it in any way.

0

Answer 7

bss OP

Oct ’22

Well this is interesting. I just created another Apple ID account, and signed in with that, and I don't get these errors anymore. So I guess it's something about my Apple ID. But I don't have the slightest idea how to fix that.

Edit: one thing I notice about the Apple ID that doesn't work: when I sign in on the simulator, the "Sign Out" button in iCloud is disabled. I don't know if that's relevant.

0

Answer 8

hm.stahl OP

Nov ’22

I had the same problem with Xcode 14 simulators. I managed to get access to iCloud by logging out from iCloud and logging in again with the same apple id.

0

Answer 9

Exafunk OP

Feb ’24

completly blocked from getting files into the simulator, this included. im on a m2 and i bet all of us having problems are apple silicone users. they are not supporting this transition well. its been how long? still like pulling teeth developing on this m2 mac mini. lots of simulator problems get it together

0

Answer 10

kersten83 OP

Nov ’24

The same thing started happening for me after I started running my app on a 18.1 simulator. When running the same code on a 18.0 simulator, it works correctly. I've tried logging in and out multiple times, restarting both simulators and even my computer, tried using different device simulators, but unfortunately nothing seems to help. I'm unsure what to try next other than filing a bug or asking for code-level support.

1