Can I ask what the ramifications are of the double registration? I don't do anything with the device token other than to log that I registered for remote notifications. Does it hurt to register first and then the registration via CKSyncEngine?

Many years later, it's now May 12, 2025 and a bunch of my customers all around the world have had this issue. Even when I've sent them a link directly to the App Store to redeem a discount offer code for my subscription app. It gives them the error on macOS, but if they use the link on iOS, it often works fine.

I had this happen again when I was adding a couple new properties to my schema. I had forgotten to switch back to the development settings in the entitlements file and ran against production. It gave some errors and I remembered I needed to switch to development, run the app there so it could update the schema, then promote the schema to production. When I did that, I started getting those incomprehensible archive errors again. So I looked at the records in the CloudKit dashboard and I noticed a couple entries that had the word FAKE in them in all caps. Didn't know how they got there, so deleted them. Then switched back to production and everything worked again. Oh, I did reset the development environment as well, but the problem was in production, not development. Those FAKE records were in production. Seems to be working now. Phew! I was worried I'd have to make all new entities and change the location of my CoreData store or something. Dodged a bullet I think.

I had this issue the other day too. But it went away. Possibly because I toggled Allow Purchases & Renewals.

How do you use the delegate? When I implement the delegate , I get an error in my AppName-Swift.h file. I have a Swift class that I've implemented to be the delegate for ImagePlaygroundViewController. Unless there's a way to access it directly from Objective-C. I figured I'd use an intermediate Swift class and then just pass the selected image to my Objective-C view controller. This is an AppKit app. Mostly in Objective-C, but with sprinkles of Swift and SwiftUI here and there. I've implemented the delegate and all the required methods. @objc public class TFImagePlaygroundManager: NSObject, ImagePlaygroundViewController.Delegate This error is what I get: Cannot find protocol declaration for 'ImageGenerationViewControllerDelegate'; did you mean [some other delegate] Is it not posible to use Image Playground in a mixed Swift / Objective-C Mac AppKit app? This is the code that's auto-generated inside my AppName-Swift.h file: @interface TFImagePlaygroundManager : NSObject <ImageGenerationViewControllerDelegate> - (void)imagePlaygroundViewController:(ImagePlaygroundViewController * _Nonnull)imagePlaygroundViewController didCreateImageAt:(NSURL * _Nonnull)imageURL; - (void)imagePlaygroundViewControllerDidCancel:(ImagePlaygroundViewController * _Nonnull)imagePlaygroundViewController; - (nonnull instancetype)initWithDelegate:(id <TFImagePlaygroundDelegate> _Nonnull)delegate OBJC_DESIGNATED_INITIALIZER; - (void)showImagePlaygroundFromController:(NSViewController * _Nonnull)controller; - (nonnull instancetype)init SWIFT_UNAVAILABLE; + (nonnull instancetype)new SWIFT_UNAVAILABLE_MSG("-init is unavailable"); @end

This is happening to me in production, but not the development environment. CloudKit Dashboard also display an error when I try to query the affected Record Type. Any proper solution to this scenario? Ok in Development, fails in Production?

I'm not using a VM. It worked before in the beta Sequoia and beta Xcode 16. But no longer since the RCs.

I have the same issue, but on a real device. Not using the simulator. Did you find a solution?

I'm using NSTableViewDiffableDataSource and as soon as I import a bunch of records (not even that many - like 600), I get the error if I have animations turned on. [self.tableDiffableDataSource applySnapshot:snapshot animatingDifferences:YES completion:^{ }]; But as soon as I turn OFF animatingDifferences, I no longer get the error.

I had this same problem, but as soon as I uncommented out this code and ran my app, while connected to the Production CloudKit container, it started to work. I thought you only had to do it one time on the Development container and then publish to production in the CloudKit Dashboard. Once I let this code run one time, after that it all started to work. do { // Use the container to initialize the development schema. try container.initializeCloudKitSchema(options: []) } catch { // Handle any errors. print(error) } #endif

Well I know this is 5 years old, but I'm just running into this issue now. Did you ever find a solution? I have an NSTreeController bound to a Swift array and I get the same crash. This time on macOS Monterey.

Well it turns out it was saving the binary data. I still get the file not found error though, but perhaps it's harmless. I wasn't seeing the photo I was saving appear due to a cacheing mechanism I had. I was forgetting to clear the cache after I added new images. So new images weren't showing up. It's all good.