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

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.

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.

is this fixed in iOS 15.4?

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.

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

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.

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.