Post

Replies

Boosts

Views

Activity

Reply to Core Data CloudKit stops syncing after incomprehensible archive error
as requested, I've created another feedback issue: FB15652576 on FB10392936, the error message is in the followup comments. here is the error from that issue - also an incomprehensible archive error. on that issue yes I had to lower the CloudKit operation rate to complete the upload - it took a month or 2 - it would be great if there was some mechanism for bulk uploads that bypass the throttles. But throttles shouldn't also corrupt the CloudKit database. not only would it throttle, but it would corrupt the database - the only way to recover was to reset the database and reload the schema and start from scratch- not possible in production. > [error] error: CoreData+CloudKit: -[NSCloudKitMirroringDelegate _importFinishedWithResult:importer:](1306): <PFCloudKitImporter: 0x2815fca80>: Import failed with error: Error Domain=NSCocoaErrorDomain Code=4864 "*** -[NSKeyedUnarchiver _initForReadingFromData:error:throwLegacyExceptions:]: incomprehensible archive (0x53, 0x6f, 0x6d, 0x65, 0x20, 0x65, 0x78, 0x61)" UserInfo={NSDebugDescription=*** -[NSKeyedUnarchiver _initForReadingFromData:error:throwLegacyExceptions:]: incomprehensible archive (0x53, 0x6f, 0x6d, 0x65, 0x20, 0x65, 0x78, 0x61)} 2022-09-08 14:04:43.136554+1000 Tupperty[1354:139717] [error] error: CoreData+CloudKit: -[NSCloudKitMirroringDelegate recoverFromError:](2165): <NSCloudKitMirroringDelegate: 0x28397c8c0> - Attempting recovery from error: Error Domain=NSCocoaErrorDomain Code=4864 "*** -[NSKeyedUnarchiver _initForReadingFromData:error:throwLegacyExceptions:]: incomprehensible archive (0x53, 0x6f, 0x6d, 0x65, 0x20, 0x65, 0x78, 0x61)" UserInfo={NSDebugDescription=*** -[NSKeyedUnarchiver _initForReadingFromData:error:throwLegacyExceptions:]: incomprehensible archive (0x53, 0x6f, 0x6d, 0x65, 0x20, 0x65, 0x78, 0x61)}
3d
Reply to macOS Sequoia SwiftUI crash
I think NSBundle file:///System/Library/PrivateFrameworks/MetalTools.framework/ principal class is nil because all fallbacks have failed is a bug. I get the same warning with iOS18 final but it doesn't crash. I guess they will fix it next release
Oct ’24