Unfortunately this issue still exists. The combination of Map() and MapAnnotation() causes it. Switching out the annotations with MapMarker() removes the runtime errors, but unfortunately isn't suited for my uses case. It might help someone else though. The purple runtime error pops up quite a bit. And most of the time it's valid: you're updating a @Published var from within the view you display that same @Published var. Which is bad. But I don't see this cause at all with the MapAnnotation implementation, something else must be triggering this.

Bit old topic, but might as well add the ultimately implemented solution if anyone else needs something similar. return locations.places.filter { $0.routes.contains { (minDistance..<maxDistance).contains($0.distance) } }

To add some more context: I'm using a fully up-to-date Xcode, against a fully up-to-date iPhone 15. I use Xcode managed signing. I changed nothing to my bundle ID or anything It runs fine in simulator I can build my other project, but I see no differences in setup except for Firestore being used in the one and not the other

Oh wow. I managed to solve it. I removed my Cocoapods integration which I used for Firebase. After that I reintegrated Firebase using the Xcode package manager. This is what solved it for me: Close Xcode, terminal navigate to your Xcode Project directory brew install cocoapods-deintegrate cocoapods-clean pod deintegrate pod clean rm Podfile Open Xcode, 'add packages' Add Firebase to build target GOGOGOGOGO ;)