Where you are using CKRecordZoneSubscription to sync the private database, you can use CKDatabaseSubscription to sync shared databases. See CloudCore for an example. Are you syncing CloudKit to CoreData? I create an observer singleton with a FetchedResultsController, detecting when changes occur in the root object (as synced from CloudKit), and post local notifications as appropriate. See CarShuffle for an example

you're jumping into a background thread, then accessing CoreData using the viewContext, which should only be used on the main thread.

nvrmnd

Look at using these in your modelComponent: MeshResource, MeshResource.Contents, MeshResource.Part e.g. func meshContents() -> MeshResource.Contents { // update mesh data … var meshPart = MeshResource.Part(…) meshPart.positions = .init(positions) meshPart.textureCoordinates = MeshBuffer(textureCoordinates) meshPart.triangleIndices = .init(indices) var contents = MeshResource.Contents() contents.models = [.init(…, parts: [meshPart])] return contents } let meshResource = try await MeshResource(from: meshContents()) let modelComponent = ModelComponent(mesh: meshResource, …) for loop { try modelComponent.mesh.replace(with: meshContents()) }

look at NSCompountPredicate

my guess is the web client to CloudKit is like any other client, and likely decrypts the data on display. better to ask, is the data encrypted in transit? You could use a packet sniffer to intercept the requests to/from CloudKit, and verify the encrypted fields are not cleartext.

my code calls player.prepareToPlay explicitly, fwiw

random crashes, imo, often mean threading issues, and indeed what you shared shows a crash in thread 2 with several other threads running as well. FWIW, early in my SceneKit days, I experienced similar crashes, and solved it by refactoring my code to add and remove SCNNodes only in main thread. fwiw.

I implemented the userDidAcceptCloudKitShareWith… in the SceneDelegate, and set up the scene delegate as such: class AppDelegate { // MARK: UISceneSession Lifecycle func application(_ application: UIApplication, configurationForConnecting connectingSceneSession: UISceneSession, options: UIScene.ConnectionOptions) -> UISceneConfiguration { let config = UISceneConfiguration(name: nil, sessionRole: connectingSceneSession.role) config.delegateClass = SceneDelegate.self return config } } class SceneDelegate: UIResponder, UIWindowSceneDelegate { var window: UIWindow? func windowScene(_ windowScene: UIWindowScene, userDidAcceptCloudKitShareWith cloudKitShareMetadata: CKShare.Metadata) { let acceptShareOperation = CKAcceptSharesOperation(shareMetadatas: [cloudKitShareMetadata]) acceptShareOperation.qualityOfService = .userInteractive acceptShareOperation.perShareResultBlock = { meta, result in guard let recordID = meta.hierarchicalRootRecordID else { return } // do the things… } acceptShareOperation.acceptSharesResultBlock = { result in // N/A } CKContainer(identifier: cloudKitShareMetadata.containerIdentifier).add(acceptShareOperation) } }

I've often wondered how NSPersistentCloudKitContainer.share… works, and your example goes a long way to explaining it. When you identify the objects you want to share, they get moved to a new zone. and that zone is what is shared. but the API probably wasn't designed to handle the scenario you describe, so once a record is moved to a shared zone, it doesn't/can't get move to another zone. 2¢

there are several open source libraries that use location… like https://github.com/AndrewHartAR/ARKit-CoreLocation

and finally, read TN3164: Debugging the synchronization of NSPersistentCloudKitContainer

then read TN3163: Understanding the synchronization of NSPersistentCloudKitContainer

start with TechNote 3162: Understanding CloudKit Throttles

I suspect that all apps using NSPersistentCloudKitContainer will behave the same way? If this genuinely surprises end-users, then it's on Apple to address, not you.