NavigationView切换视图时onDisappear未触发的问题及解决咨询

在iPad iOS 15.6环境下，使用NavigationView通过NavigationLink跳转详情页时，目标视图的onAppear能正常触发，但onDisappear不会立即执行——只有当切换到第三个视图时，第一个视图的onDisappear才会被调用。例如：

• 跳转到"one"时，触发DetailView: onAppear: one
• 跳转到"two"时，触发DetailView: onAppear: two
• 跳转到"three"时，才会触发DetailView: onDisappear: one，同时触发DetailView: onAppear: three

这种延迟会导致无法及时执行暂停视频播放器这类需要视图消失时立刻处理的操作，这是SwiftUI为优化性能保留视图实例导致的。

复现代码 #

struct DetailModel: Identifiable {
    var title: String
    
    var id: String  {
        title
    }
}

struct ContentView: View {
    
    @State var details = [DetailModel(title:"one"), DetailModel(title:"two"), DetailModel(title:"three"), DetailModel(title:"four")]
    
    var body: some View {
        NavigationView {
            List {
                ForEach(details) { detail in
                    NavigationLink(detail.title) {
                        DetailView(detail: detail)
                    }
                }
            }
            .navigationTitle("Details")
        }
    }
}

struct DetailView: View {
    
    var detail: DetailModel
    
    var body: some View {
        Text("DetailView: \(detail.title)")
            .onAppear() {
                print("DetailView: onAppear: \(detail.title)")
            }
            .onDisappear() {
                print("DetailView: onDisappear: \(detail.title)")
            }
    }
}

日志输出 #

DetailView: onAppear: one

DetailView: onAppear: two

DetailView: onDisappear: one
DetailView: onAppear: three

DetailView: onDisappear: two
DetailView: onAppear: four

解决方案 #

方法1：升级到iOS 16+，使用NavigationStack替代NavigationView #

NavigationStack是iOS 16引入的新导航组件，视图生命周期回调更精准，会在视图真正从导航栈移除时立即触发onDisappear。修改后的代码如下：

struct ContentView: View {
    @State var details = [DetailModel(title:"one"), DetailModel(title:"two"), DetailModel(title:"three"), DetailModel(title:"four")]
    @State private var path = NavigationPath()

    var body: some View {
        NavigationStack(path: $path) {
            List {
                ForEach(details) { detail in
                    NavigationLink(detail.title, value: detail)
                }
            }
            .navigationTitle("Details")
            .navigationDestination(for: DetailModel.self) { detail in
                DetailView(detail: detail)
            }
        }
    }
}

此时DetailView的onDisappear会在视图切换或弹出时立即触发，无需额外修改。

方法2：兼容iOS 15，使用NavigationLink的selection绑定跟踪活跃视图 #

通过绑定NavigationLink的selection属性，精确跟踪当前显示的详情视图，当选中视图变化时主动执行清理操作。

修改ContentView添加选中状态绑定：

struct ContentView: View {
    @State var details = [DetailModel(title:"one"), DetailModel(title:"two"), DetailModel(title:"three"), DetailModel(title:"four")]
    @State private var selectedDetail: DetailModel?

    var body: some View {
        NavigationView {
            List {
                ForEach(details) { detail in
                    NavigationLink(
                        detail.title,
                        tag: detail,
                        selection: $selectedDetail
                    ) {
                        DetailView(detail: detail, selectedDetail: $selectedDetail)
                    }
                }
            }
            .navigationTitle("Details")
        }
    }
}

修改DetailView监听选中状态变化：

struct DetailView: View {
    var detail: DetailModel
    @Binding var selectedDetail: DetailModel?

    var body: some View {
        Text("DetailView: \(detail.title)")
            .onAppear() {
                print("DetailView: onAppear: \(detail.title)")
                // 启动视频播放等操作
            }
            .onChange(of: selectedDetail) { newValue in
                guard newValue != detail else { return }
                print("DetailView: 已不再显示，执行暂停操作: \(detail.title)")
                // 暂停视频播放器、清理资源等操作
            }
            .onDisappear() {
                print("DetailView: onDisappear: \(detail.title)")
            }
    }
}

这种方式可以在视图切换瞬间立刻执行所需操作，不受SwiftUI视图缓存机制影响。

补充说明 #

SwiftUI的NavigationView在iPad上会保留导航栈中最近的几个视图实例以优化切换性能，这就是onDisappear延迟触发的核心原因。上述两种方法分别通过使用新导航组件或主动跟踪导航状态，解决了无法及时检测视图消失的问题。

内容的提问来源于stack exchange，提问作者Fred Klein