Post not yet marked as solved
I answered myself, I can always get the CKShare requesting the CKRecord with recordName = "cloudkit.zoneshare" for the record zone I want.
Hi,
I can see a couple of mistakes.
The first one, you should create your new Ping() inside your recordFetched block, and I would use a struct, not a class.
The second is that you are printing the return from loadPing(), that will print to your console only.
If you want to automatically show them, you should fetch them from an ObservableObject, similar to what it seems to be UserProgress. Basically you create a model, and your results as @Published array that you can put in a ForEach.
Finally, your operations run asynchronously. Probably your return is return an empty array because the operations are still running in another thread.
Post not yet marked as solved
If you have different devices for your work and personal life, I don't see the problem, I have like three or four iCloud accounts.
Are you doing the synchronization manually? You can add your own CKRecordID when you first create the CKRecord previously to save it to CK.
Once the record lives in CK, you can't edit the ID (as far as I know).
Just remember that the ID must be unique between all the CKRecord in your CKRecordZone.
Post not yet marked as solved
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.
Post not yet marked as solved
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.
Post not yet marked as solved
I'm having the same problem :(
Post marked as Apple Recommended
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.
Post marked as Apple Recommended
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.
Post not yet marked as solved
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. :(
Post not yet marked as solved
Having the same problem here.It seems that if you use the same idea of this answer in stackoverflow, it works.https://stackoverflow.com/a/57837007/3377161Basically you add a Button in your NavigationBar and then inside the body the navigationlink.
Post not yet marked as solved
They just release the documentation.https://developer.apple.com/documentation/coredata/nsderivedattributedescriptionI wish they would release some examples, too.