SwiftUI is very bad at working with maps, and they still have a long way to go. Since most of the stuff I'm doing, these days, is highly location-dependent, I can't compromise.
I have been reading about people hitting these types of walls for a couple of years, and thought that Apple has worked around it. I suspect that the issue is with trying to use UIKit stuff inside of SwiftUI, and I was trying to avoid UIViewRepresentable (because it's a kludge).
SwiftUI is very bad at working with maps, and they still have a long way to go. Since most of the stuff I'm doing, these days, is highly location-dependent, I can't compromise.
I have been reading about people hitting these types of walls for a couple of years, and thought that Apple has worked around it. I suspect that the issue is with trying to use UIKit stuff inside of SwiftUI, and I was trying to avoid UIViewRepresentable (because it's a kludge).
Back to UIKit. This stinks. :(