Anyone tried the iOS 18.5 beta to see if it fixes anything?

It’s also frustrating that there has been no comment from anyone at Apple, I’ve also received no response to my Feedback ticket. What are we supposed to tell our customers in the mean time? No idea if this will be fixed or not and my app is useless without it. Fwiw I tried resetting my Apple Watch and it did not resolve the issue.

I've just started to experience the same problem with my app. Tried with another WorkoutKit app and they don't sync either. Restarted devices, reset connections but no joy. Will send feedback but in the mean time did anyone find a workaround for this?

Any news @DTS Engineer? Thanks!

I'm a bit stuck, I believe I'm experiencing this issue too although I'm not sure if it's exactly the same or not. I'm trying to test a migration from V2 to V3 in the simulator but the app always terminates before didMigrate with issues such as: error: Attempting to retrieve an NSManagedObjectModel version checksum while the model is still editable. This may result in an unstable verison checksum. Add model to NSPersistentStoreCoordinator and try again. error: CoreData+CloudKit: -[NSCloudKitMirroringDelegate recoverFromError:](2313): <NSCloudKitMirroringDelegate: 0x600003d05d10> - Attempting recovery from error: Error Domain=NSCocoaErrorDomain Code=134060 "A Core Data error occurred." UserInfo={NSLocalizedFailureReason=The mirroring delegate could not initialize because it's store was removed from the coordinator.} BUG IN CLIENT OF CLOUDKIT: Registering a handler for a CKScheduler activity identifier that has already been registered (com.apple.coredata.cloudkit.activity.export.8315617A-2590-4989-A1F0-0AACDDA4713E). I'm not sure the first one is relevant, but the others are similar to those of the OP. I have attached the entire output here: Output Log The test device is an iPhone 16 simulator running iOS 18.3. @DTS Engineer what is the recommended course of action for me? Do I need to wait for a fix, is it then an Xcode fix or in iOS? It seems I cannot perform migrations at all until this is fixed which seems like an issue that would affect many people? Thanks! Will