This unexpected user experience has far reaching effects. It is bad enough that the Core Data / CloudKit frameworks are inherently fragile and need a total re-write, but it makes everyone scared to death to try anything they have none before in the XCODE IDE. I just ruined another project --- there are edge effects evidently to having more than one container -- it now destroyed my ability to properly query data from the other container. Went to uncheck the extra container (that caused the meltdown in what should have been unrelated areas of the project) and find that I can't. Worse, find that this problem has been documented here FOR FIVE YEARS. I tried to be loyal and tried to do an app that was going to be 100% Apple (CoreData, CloudKit) -- weaving through all the ridiculous code and coding and decoding between SwiftUI/CoreData/CloudKit just to sync a few measly data elements -- only to be kicked in the face by this amateurish (college professor theoretical data structures that don't work in the real world) joke for persistence management. (Which horrible architecture earlier today destroyed a slideshow in KeyNote I had to rebuild earlier today -- just because Finder and KeyNote cratered on an edge effect they had not architected to cover in a shared KeyNote file. Just showing that the Apple persistence/syncing architecture is not robust enough for serious commercial use.) I feel I have a bit of a right to rant about this -- as I have been programming since 1977!! What takes me a day to develop in this decrepit architecture took minutes to do back in the 1980's --- with 100's of concurrent users and absolutely no data loss in syncing and persistence. It is like somehow all the great knowledge we had back in the 1980's got flushed down the toilet and had to be relearned by another generation. Anyway -- I have about had it with ignoring bugs for FIVE YEARS. Sorry, once again, for this useless rant that won't go anywhere.