Just to expand on @OOPer's comment and spell it out for simple-folk such as myself who are fairly new to SwiftUI - You don't need to "nest" a NavigationView. By that it means (including pseudo-code) View A -> View B View A var body: some View { NavigationView( .. stuff here .navigationBarTitle("Main menu") ) } View B var body: some View { Text("Stuff to show on the next page") .navigationBarTitle("sub menu", displayMode: .inline) } Seems kind of obvious when you think about it, coming from UIKit, you wouldn't be able to push a UINavigationController into the navigation stack.

I'm getting this very quickly in areas that require a lot of MKPolylineRenderer / MKPolygonRenderer / MKMultiPolygonRenderer. I have tried changing mapType on when moving about, before removing/adding new overlays, but it's just totally flaking out on iOS 16.1.1. This is kind of a critical issue for us as it's breaking our production application. Has anyone got any insight into this this recently?