At least they add a search! (I'm working with CloudKit since the beginning and I have a lot of unused containers)

I can't help you there, I haven't use automatic synchronization because I need control about what is being synchronized. Actually I'm doing some test to stop using coredata references, so I won't have problems when synchronizing data out of order. You should make a list of pros and cons about the two options you have, and then decide which one is less painful, but you will have to compromise at some point.

I was using BEGINSWITH, it shouldn't need to be Searchable. My whole idea was being able to search for prefixes in an array containing words. Searchable was not an option because I needed to search by prefixes, like if you are looking for all the "Joels", so I can start searching for "J", "Jo", "Joe" and find what I'm looking for. I decided change my idea, and I'm going to synchronize to the device, so I can use coredata to make best queries.

The problem is not only on my testing App, also my fully working app, build for and with the latest stable release, but running on the last iOS 15 beta release.

I have a private app, build with the previous stable Xcode and it's also failing on my devices with beta 4. I was expecting an emergency update today :(

That error means that you should extract code to a variable or function because your actual code is too complex to check. Probably yo have a lot of nested views with some ifs-elses.

Probably they are adding some new security measures and they were not so nice to include a warning.

I would try setting the context in the setUp method.

The warning was caused by a bug in the Xcode beta, but this will be an issue in the future, so I hope that Apple will share the "right way" to do this, or probably they will make everything Sendable in CK.

I had a similar problem and what I did was creating an array of "Identifiable Structs" with only 1 item with the coordinates. Every time I had new data, I replaced the struct in the array and because it has a new ID, it's updated accordingly. It's almost the same that you are saying, but with your example, if you have too many lines, you start getting an error after approximately 600 lines. With my solution, I did a test with almost 5000 lines, all in the same polyline without any problem.

I just found an .onMapCameraChange(), I think it might have what I want :)

I only needed to get an update about the map camera, so I don't know about dragging items around. I haven't seen anything useful for your need, yet.

Awesome!