SwiftUI - NavigationLink inside NavigationBarItems, returns error on navigating from detail back to master view

I'm getting this crash with a brand new app with minimal code.

I have a single content view with the following body:

var body: some View {
    NavigationView {
        Text("Hello, World!")
            .navigationBarTitle("TestNav")
            .navigationBarItems(trailing:
                NavigationLink(destination: Text("Hello"), label: {
                    Text("Navigation")
                })
        )
    }
}

If I tap the navigation link and go back, the app completely crashes.

Here's a video: https://cl.ly/9cedd98cec8b

Xcode 11.2 - iOS 13.2

I'm amazed that Apple hasn't acknolwdged or god forbid fixed this already.

It seriously affecting development work.

Having same issue, NOT on simulator, on iphone and ipad.. same exacxt error message iOS 13.2

anyone figure this out yet?

+1 not working on physical iPad on 13.2

I submitted a Feedback Request thru Xcode and apparently "Less than 10" people are also having this issue, lol. Their bug reporting is a joke.

for reference: Nov 5, 2019 at 11:03 AM – FB7428344

Please tell us how to help with your request. I am sure there are many more. As far as I see it, any app built in SwiftUI that has navigation will crash in iOS 13.2. I am sure there are numerous SwiftUI apps in the store and many people that upgraded to 13.2.

I would suggest, go into Xcode, click on Help and choose Report to Apple. Then submit a feedback/bug report with the title:

Tried to pop to a view controller that doesn't exist.

Then explain breifly what your specific issue is, that should let them link some more of these reports together.. Maybe then theyll take a look at it..

now it says more than 10. Thats good, its growing..

Everyone in this thread should be filing bugs, while being sure to add their report #s to their comment(s) for reference.

I think I figured out a workaround at least for my specific issue with a NavigationView enclosing a TabView. Here are two almost identical views with the only difference of where the NavigationView is placed.

Both views work on iOS 13.1 but only one works in iOS 13.2. I hope this helps to some of you to create some workarounds

struct ContentViewThatCrashes: View {
    @State private var selection = 0

    var body: some View {
        NavigationView{
            TabView(selection: $selection){
                NavigationLink(destination: NewView()){
                    Text("First View")
                        .font(.title)
                }
                .tabItem {
                    VStack {
                        Image("first")
                        Text("First")
                    }
                }
                .tag(0)
                NavigationLink(destination: NewView()){
                    Text("Second View")
                        .font(.title)
                }
                .tabItem {
                    VStack {
                        Image("second")
                        Text("Second")
                    }
                }
                .tag(1)
            }
        }
    }
}

struct ContentViewThatWorks: View {
    @State private var selection = 0
    
    var body: some View {
        TabView(selection: $selection){
            NavigationView{
                NavigationLink(destination: NewView()){
                    Text("First View")
                        .font(.title)
                }
            }
            .tabItem {
                VStack {
                    Image("first")
                    Text("First")
                }
            }
            .tag(0)
            NavigationView{
                NavigationLink(destination: NewView()){
                    Text("Second View")
                        .font(.title)
                }
            }
            .tabItem {
                VStack {
                    Image("second")
                    Text("Second")
                }
            }
            .tag(1)
        }
    }
}

I have also added it as answer into the StackOverflow link with the same problem:

https://stackoverflow.com/questions/58404725/why-does-my-swiftui-app-crash-when-navigating-backwards-after-placing-a-navigat/58737171#58737171

I've just filed an official I-used-to-work-on-this-and-have-some-extra-insights-I-can't-share-publicly version of the above as FB7431049.

Thank you for your solution. Ive tried putting the NavigationView everywhere, no help..

I had the same problem and my workaround was to replace the NavigationLink in the "trailing: " with a Button that triggered a State variable to show a .hidden NavigationLink.

Example:

struct ContentView: View {

    @EnvironmentObject var dataStore : DataStore

    @State private var showingInvite : Bool = (DataStore.shared().vehicles.count == 0)
    @State private var showVehicles : Bool  = false

    var body: some View {
        NavigationView {
            VStack {
                MasterView()
                NavigationLink(destination: VehiclesView(currentCar: self.$dataStore.currentLog), isActive: self.$showingInvite) {
                    Text("Add Vehicle")
                }.hidden()
                MenuView()
            }
            .navigationBarItems(
                trailing: Button(action: {self.showingInvite = true},
                                 label: { if DataStore.shared().vehicles.count > 0 {
                                                Text(DataStore.shared().vehicles[self.dataStore.currentLog] )
                                            } else {
                                                Text("Add")
                                            }
                                        })
            )
        }
    }

}

Aha! I recognize `isActive:` now—I'd seen that & forgotten all about it when I was looking for ways to automatically trigger a push a few weeks ago. I suspect this is the way such things are 'supposed' to be done (after all, it's a NavigationLink, not a NavigationLinkView).

I wonder if what label content of EmptyView() would do? There may be a more attractive canonical way of including a toggle-able NavigationLink without resorting to .hidden().

Yep,

so looks like nav bar items which actually navigate cause this issue.

Just moved the nav link to inside my code and set a toggle in the nav bar for that and no crash..

sweet! thx