ManagedNavigationStack nested in TabView itself nested in a Main ManagedNavistationStack

[alexandreadriaens]

Hi,

First of all thanks for creating this nice library.

However, I'm bumping on a problem on my side, and I'm wondering how to deal with it.

For my app, I have created a main ManagedNavigationStackView that embed my whole app. And then inside it I have a TabView, and for each element of the tab, I have another ManagerNavigationStackView. In this inner one, I added a view, let's say TestView. In this TestView while trying to call navigator.navigate() with push NavigationMethod, the push is done on the main stack and not the inner one.

Why? Is it a known limitation of Navigator? Or I'm doing something bad?

I want to be able to have a main stack view in order to push on the main app if needed (pushing a WebView) but also pushing a view in the inner stack when I want to keep displaying the tabBar.

Thanks in advance for your help !

[hmlongco]

See if this helps...

https://hmlongco.github.io/Navigator/documentation/navigatorui/navigationtree

[alexandreadriaens]

No I still bump with the same problem. It seems we can't really works with ManagedNavigationStack that embed another ManagedNavigationStack for example here :

// ❌ Your actual setup — the outer stack handle the push
ManagedNavigationStack {        // outer
    TabView {
        ManagedNavigationStack { // inner 
            TestView()
        }
    }
}

// ✅ Pattern that works with Navigator
@main struct MyApp: App {
    @Environment(\.navigator) var navigator  // root navigator 
    var body: some Scene {
        WindowGroup {
            TabView {
                ManagedNavigationStack { // each tab handle its own stack
                    FeedView()
                }
                ManagedNavigationStack {
                    ProfileView()
                }
            }
        }
    }
}

The problem is when I want to push another view in TestView, the navigator is the one from the inner stack, but when applying a navigator.navigate(to) action, it pushes the screen on the outer stack.

[theedov]

NavigationStack { TabView { NavigationStack { … } } }

I'm pretty sure what you've described is a swiftui anti-pattern.

NavigationStacks(ManagedNavigationStack) should live inside TabView not the other way around.

[alexandreadriaens]

But what about apps that push for example a full screen view on the main view ? Let's say a webView or a complex configuration screen like a filter. In this case, I want to be over my tabView context and don't see the tabBar anymore. But I don't want a present either.