it seems modifiedAt in iOS15 is now modifedTimpstamp. u need to have a Sortable index on that and queryable one recordName. But I also get the same "Custom zones are not allowed in public DB" when following the CoreData + Cloudkit doc.

just need a flag to get it out of the interface. don't have to delete it. gets confusing with so many junk containers - causes problems and lots of wasted time.

looks like rate limiting to me. basically impossible to sync a large amount of data in iCloud now

not solved in iOS 15.3 final either. seems it only happens when pulling down data from the private database in the cloud. i'm not getting these issues with the public database.

is this fixed in iOS 15.4?

I think something like this would be an ideal solution but I was never able to get it to work to parse axis values either. Maybe someone who understands FormatStyle better can help us.

thanks, that worked. I'd been splitting out each section on a list to a separate struct file each with their own navigationDestinations so it makes it a bit messy to do this way but that definitely gets rid of the errors and makes scrolling a lot smoother, so looks like ill need to find a better design pattern.

same issue. in my case it's about 150mb of data, 1.5million records.

I have a feedback assistant entry logged: FB10392936. if u are getting the same, please log one also and reference mine, so they can get more info on it

thanks. I ended up implementing a custom queue in the first actor to manage and queue the 'async' calls to the second actor. A decent amount of code, would be nice if actors had some standard functionality to do something like this, as the custom queue has quickly become boilerplate code in almost all of my actors now.

on FB10392936 they asked for some more info, but closed it before I could get the info for them - I had to run the process again - it takes a couple of weeks to run (hence the problem), before it corrupts the CloudKit db. ive updated it with the info they requested. any chance we can get it reopened?

same issue here in iOS16 RC

dont really need a server. can use CloudKit for this

effort sounds about right for someone who can already develop swift macOS apps. Some of those requirements are quite involved, and at first glance may only be possible (or not possible) with some cutting edge research/tech and may take significantly longer than expected as far as effort goes. If u want corporate style governance, you will need to pay corporate style prices if anyone is going to do that.

further on this. I was able to stop the freezing on all of my use cases now with .id(UUID()). needed it on all NavigationLinks and some Lists where there was still freezing. not a full fix because setting .id(UUID()) on a List makes it reload every time it appears which is annoying for users when the list takes time to reload (as in my case). a couple of NavigationLinks needed a static id like .id("someid"), some needed .id(UUID()). not sure why. hopefully gets fixed in the sdk as some point.