[BUG] iOS26: Deep back navigation causes infinite loop when using NavigationStack instead of NavigationView

[bobkexit]

Title

Deep back navigation causes infinite loop when using NavigationStack instead of NavigationView

Description

When replacing NavigationView with NavigationStack in a TabView setup with FlowStacks coordinators, deep back navigation triggers an infinite loop, making it impossible to navigate back through the stack.

Repository Link

Full code available at: FlowStacks_Back_Bug_Navigation

• Relevant file: LiquidGlass%2BFlowsStack/Root/TabBarView.swift

Current Code

TabView {
    ForEach(viewModel.tabs, id: \.id) { coordinator in
        Tab(coordinator.tabBarItem.name, systemImage: coordinator.tabBarItem.systemImage) {
            NavigationView {  // Works fine
                TabResolverView(coordinator: coordinator)
            }
        }
    }
}

Problematic Code

TabView {
    ForEach(viewModel.tabs, id: \.id) { coordinator in
        Tab(coordinator.tabBarItem.name, systemImage: coordinator.tabBarItem.systemImage) {
            NavigationStack {  // Causes infinite loop on deep back navigation
                TabResolverView(coordinator: coordinator)
            }
        }
    }
}

Expected Behavior

Deep back navigation should work the same way with NavigationStack as it does with NavigationView, allowing users to navigate back through multiple screens without getting stuck.

Actual Behavior

When attempting to navigate back through multiple screens (deep back navigation), the app gets stuck in an infinite loop and becomes unresponsive.

Environment

• iOS: 26.0 (23A5297i)
• Xcode: 26.0 beta 4 (17A5285i)
• FlowStacks version: 0.8.4

Reproduction Steps

1. Set up TabView with NavigationStack containing FlowStacks coordinator
2. Navigate deep into a flow (multiple screens)
3. Attempt to navigate back multiple levels
4. App gets stuck in an infinite loop

This issue prevents migration from the deprecated NavigationView to the modern NavigationStack API.

[abubakar-9013]

Can't say for sure what the issue might be, but you are wrapping your tabView in FlowStack at top level and inside TabView, you are using another NavigationStack. That doesn't seem right.

[bobkexit]

@abubakar-9013, that has nothing to do with the original issue. If you remove FlowStack, which wraps TabView, the issue is still there. About wrapping TabView with FlowStack: In our original project, we present some views on top of TabView. After encountering the issue, I tried to reproduce it by partially recreating the navigation structure of the original project. Originally it was looking like:

FlowStack($coordinator.routes) {
            TabBarView(viewModel: coordinator.rootViewModel)
        }
        .flowDestination(for: RootRoute.self) { route in
            switch route {
                ...
            }
        }