It depends in so many factors, such as how many records you will have, if you need to be able to work offline, and so on. I have an App (private) that shared a large number of records using CloudKit and a local cache with coredata. Now I'm dividing that App in multiple Apps and I thing I will use a mix between full synchronize tables and cache tables, all sharing the same record zone. I would recommend that you start using only CloudKit, then you can start adding coredata for cache, if you realize that you need it.

Just a comment, I have had much more than 5000 records in a single CKRecord shared for many many years without many problems, so I think that limit is no longer valid.

I'm having the same problem :(

Someone helped me with this instructions for the same problem with TwilioVoice.framework and it worked perfect. Maybe you can adapt the instruction for your frameworks. [https://github.com/twilio/twilio-voice-ios/issues/64#issuecomment-747186499) Basically you separate the framework in the platforms and then you join them again as xcframework. Finally, you include the new xcframework into your code.

I'm having the same issue. It seems that it has something to do with "internet". If I disconnect my wifi, Xcode start responding fine again. If I'm right, Xcode must be trying to connect to some service that is not responding and not giving timeout, neither.

I'm having the same issue with Twilio.framework. It worked without problem until the last 12.3 beta. And after updating to the last macOS 15.15.7, Xcode is freezing after every single click. :/

I found the true error in the problem I was having using StateObject(wrappedValue:). One of the params that I need to initialize the object is given by @Environment, and it seems that I can't access that var in the struct initializer.

Initializing the State Object in the init using StateObject(wrappedValue:) is not longer working for me. Maybe is beta4. I tried to look if Apple made any change, but I did not find anything.

I have a Late 2012 iMac that works perfectly fine, with good CPU, RAM, etc..., and I can not understand why is not being supported by Big Sur. I am pretty sad, I would upgrade to a new iMac but I can not at this moment. :(