Swift/ContiguousArrayBuffer.swift:580: Fatal error: Index out of range 2021-09-28 20:38:14.956007-0500 CloudkitTemplate[1852:78799] Swift/ContiguousArrayBuffer.swift:580: Fatal error: Index out of range The same code worked fine the night before on three physical devices and iPhone 8 simulator. Twenty four hours later, getting this mysterious crash.

Not trying to mix applications! Been working on an ios14 app all along -- suddenly get the "dyld: Library not loaded: /System/Library/Frameworks/_CoreData_CloudKit.framework/_CoreData_CloudKit" message!!!

Those changes (directly setting the databaseScope key did NOT work for me. I still get the following error: "dyld: Library not loaded: /System/Library/Frameworks/_CoreData_CloudKit.framework/_CoreData_CloudKit" even after re-adding the Cloudkit framework.

I don't recall upgrading to Xcode 13, but unfortunately that is what I am now stuck with -- ruined my window to work on my app -- once again, dead in the water dealing with very unprofessional handling of the Cloudkit/CoreData eco-system. They need a total re-write of the persistence architecture and/or get better management over their Cloudkit and CoreData teams.

This is worse than "awful" -- I have limited time to work on my ios14 app, which was working fine --- now I am stuck with some sort of "dyld: Library not loaded: /System/Library/Frameworks/_CoreData_CloudKit.framework/_CoreData_CloudKit" I did not give permission to Apple to upgrade my XCODE, now I get this run time error with NO guidance how to fix. The lame Cloudkit architecture is fragile enough, without the Cloudkit/CoreData folks constantly mucking around with the underlying code. It is bad enough they are using design patterns we proved untenable way back in the early 80's, I can see why serious apps use 3rd party persistent storage and avoid this nightmare Apple has created. Just an FYI -- since Apple uses this same flawed architecture for the MAIL app, the MAIL app is way too dangerous to use for business/commercial purposes. Constantly getting emails where some or all of the email content is irrevocably missing -- and with the change notification architecture it is impossible to get those email messages repaired. So, Apple happily (Naively) considers all the emails sync'd between devices, even when Apple MAIL has delivered damaged email content. Totally Unprofessional. They need to quit following some theoretical design pattern from some college professors and get back to the reality of real-world use cases AND need cases. Ugh. Kids these days....