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)}
Post
Replies
Boosts
Views
Activity
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.
add .id(UUID()) on the NavigationLink fixes it for me in some cases.
I think it's a bug in swiftUI. and I'm sure that there are more appropriate ways of assigning the id, but if u ensure the id is unique then it will fix the freeze in some cases.
still doesn't fix it for everything.
I didn't think Xcode supported java? I thought it was only C, and apple languages - Objective C, Swift, SwiftUI no?
same issue when tapping on NavigaitonLink. using new swiftui syntax but not using the programmatic way. 100% CPU freeze.