混用NavigationLink(destination:,label:)与.navigationDestination致NavigationStack异常

在App层级的NavigationStack中以Screen1为根视图，采用两种导航方式时出现异常：

• Screen1使用NavigationLink(destination:label:)跳转至Screen2
• Screen2通过.navigationDestination关联Screen3
• 实际跳转Screen3时，页面仅短暂显示就退回Screen2；点击Screen2的导航栏返回按钮，Screen3才会显示，再次点击返回则回到Screen1
• 经测试：先使用NavigationLink(destination:,label:)再用.navigationDestination必现此问题，顺序调换则不会。

复现代码：

struct Screen3: View {
    var body: some View {
        VStack {
            NavigationLink(destination: Fourth()) {
                Text("Screen 3")
            }
        }.navigationTitle("Screen 3")
    }
}

struct Screen2: View {
    var body: some View {
        VStack {
            NavigationLink(value: 0) {
                Text("Screen 2" )
            }
        }
        .navigationDestination(for: Int.self) { int in
            Screen3()
        }.navigationTitle("Screen 2")
    }
}

struct Screen1: View {
    var body: some View {
        NavigationLink(destination: Screen2()) {
            Text("Screen 1")
        }
        .navigationTitle("Screen 1")
    }
}

#Preview {
    NavigationStack {
        Screen1()
    }
}

这是因为旧版NavigationLink(destination:)和新版.navigationDestination的路由机制冲突：前者是手动直接压栈，后者依赖NavigationStack的NavigationPath状态管理导航栈，混合使用会导致栈状态混乱，触发异常回退。

要同时使用两种方式且不破坏NavigationStack，核心是让所有导航操作基于同一个NavigationPath状态，具体做法如下：

1. 在根层级为NavigationStack绑定NavigationPath实例
2. 将Screen1的NavigationLink(destination:)替换为基于value的形式，并在根视图添加对应的.navigationDestination处理跳转
3. 保留Screen2的.navigationDestination逻辑，建议统一用自定义枚举作为导航标识（比Int更清晰）

修改后的完整代码：

import SwiftUI

// 自定义导航标识枚举，清晰区分不同跳转目标
enum NavTarget: Hashable {
    case screen2
    case screen3
}

struct Screen3: View {
    var body: some View {
        VStack {
            Text("Screen 3")
            // 若需继续跳转，建议统一用value形式保持一致性
            // NavigationLink(value: NavTarget.screen4) { Text("跳转到Screen4") }
        }
        .navigationTitle("Screen 3")
    }
}

struct Screen2: View {
    var body: some View {
        VStack {
            NavigationLink(value: NavTarget.screen3) {
                Text("跳转到Screen3")
            }
        }
        .navigationDestination(for: NavTarget.self) { target in
            switch target {
            case .screen3:
                Screen3()
            default:
                EmptyView()
            }
        }
        .navigationTitle("Screen 2")
    }
}

struct Screen1: View {
    var body: some View {
        VStack {
            NavigationLink(value: NavTarget.screen2) {
                Text("跳转到Screen2")
            }
        }
        .navigationTitle("Screen 1")
    }
}

#Preview {
    @State private var navPath = NavigationPath()
    return NavigationStack(path: $navPath) {
        Screen1()
            .navigationDestination(for: NavTarget.self) { target in
                switch target {
                case .screen2:
                    Screen2()
                default:
                    EmptyView()
                }
            }
    }
}

如果确实需要保留旧版NavigationLink(destination:)，必须确保根NavigationStack绑定了NavigationPath，但更推荐统一使用新版NavigationLink(value:) + .navigationDestination的组合，这样导航栈状态管理更可控，能彻底避免这类冲突。

内容的提问来源于stack exchange，提问作者Gowtham Ravichandran