if there is a question here, the answer is to do what it says "Retry after X seconds". The actual time is included in the info dictionary of the error. Here's a snippet from CloudCore, an open-source sync engine, that shows how it retrieves this info… private func handle(error: Error, …) { guard let cloudError = error as? CKError else { … return } switch cloudError.code { case .requestRateLimited, .zoneBusy, .serviceUnavailable: if let number = cloudError.userInfo[CKErrorRetryAfterKey] as? NSNumber { let pauseUntil = Date(timeIntervalSinceNow: number.doubleValue) } … } }

In my experience, no. You should manually trigger your sync logic.

can you reproduce in iOS 16.2? If yes, file a bug in FeedBack Assistant

fwiw having the share link in and of itself doesn't give any access to the root record or zone being shared.

Yes, checking that box encrypts the data on CloudKit. You can learn more about it here https://developers.apple.com/videos/play/wwdc2021-10015/?time=1285 BUT, you might consider storing passwords in the Keychain instead.

explore CoreImage https://developer.apple.com/documentation/coreimage

sounds like a race condition

please file a bug report in the Feedback Assistant app.

FetchRequeset has its own sort descriptors. Better to let it resort itself. Also, is Table optimized for lots and lots of items?

AFAIK, No. ARBodyTracking uses the lidar sensor to detect 3D body position. You can use Vision to detect 2D body pose information on a video, if that helps.

I, too, have noticed that the pricing information seems to have been scrubbed from Apple's websites. Looking at my existing containers, it appears the public storage limits fall and rise based on active users. In the CloudKit dashboard, head over to Telemetry, Usage to see for yourself.

imo "occasional crash" almost always means "race condition". Look at refactoring your code to add and remove objects in the - (void)renderer:(id )renderer updateAtTime:(NSTimeInterval)time callback?

use NSPersistentCloudKitContainerOptions to configure the container identifier to sync with class PersistenceApp1: ObservableObject { static let shared = PersistenceApp1() let container: NSPersistentCloudKitContainer init(…) { container = NSPersistentCloudKitContainer(name: “App1”) let store = NSPersistentStoreDescription() store.cloudKitContainerOptions = NSPersistentCloudKitContainerOptions(containerIdentifier: "iCloud.com.example.App1") container = [store] container.loadPersistentStores… } … } Also, make sure to add both container identifiers to your app's Signing & Capabilities > iCloud > Containers list

fwiw, I also saw this two days ago. It's not often I change my CloudKit schema, so unsure how long this has been an issue. To resolve it to my own satisfaction, I manually restored the various indices in dev, such that the only change being pushed to production was the actual new fields, and it worked.

Yes, you can…