still happening in iOS18.5

I consistently get a similar incomprehensible archive error after running for a while. have a few radars open on this. so far no response: FB15652576 FB10392936 https://developer.apple.com/forums/thread/766662 https://developer.apple.com/forums/thread/713908 They broke something around the time of the iOS16 RC and it's been broken in every iOS release since. something on the CloudKit server side gets corrupted and fails. the only way to fix it is to reset the container and start again - not possible in production. Has been a show stopper for us. Had to shelve an app until its fixed.

no solution yet. if it happens in dev then you can reset the environment. in prod you are screwed. still happening in iOS18.3.1

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)}

still happens in iOS18.0.1

seems to be ok now

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

this is beta software. downgrade and go back to iOS17

This still happens in iOS17. anyone know a solution or a workaround? We cant be resetting the environment in production.

you are probably having thread contention. they could be blocking each other. it is possible to overwhelm the system with too many threads. sometimes u get better utilisation with less threads. really u only want as many as you have cpu cores running at the same time otherwise they interrupt each other. u can look at the concurrency tool in instruments for some hints.

other people having same issue: https://developer.apple.com/forums/thread/737724 and https://developer.apple.com/forums/thread/737724

I get same issue.

this still happens in iOS17 final

yes. they give u sample code to setup the stack in swift without using swiftui

I've found that in some cases setting .id(UUID()) on the navigationLink fixes the problem, but it doesn't work all the time.