iOS17下SwiftUI多视图返回出现0x104344480并发访问崩溃求助

问题根源 #

你遇到的崩溃是因为iOS17中NavigationStack对导航状态的处理逻辑更严格——同时修改多个isPresented绑定属性会触发并发的导航栈操作，导致内部内存访问冲突。iOS16及模拟器的旧实现无此严格校验，因此不会出现崩溃。

解决方案 #

推荐使用NavigationPath统一管理导航栈状态，替代多个独立的布尔绑定属性，这种方式更贴合SwiftUI导航系统的设计，能彻底避免并发操作冲突。

步骤1：定义导航目标枚举 #

用枚举统一管理所有导航场景，需遵循Hashable协议以便NavigationStack识别：

enum NavigationDestination: Hashable {
    case settings
    case teamBuilding
    case continueScore
    case startGame
}

步骤2：重构NavigationState #

将原有的布尔属性替换为NavigationPath，若需兼容旧代码，可保留布尔属性的封装，内部通过路径操作实现逻辑：

class NavigationState: ObservableObject {
    @Published var path = NavigationPath()
    
    // 兼容旧的teamBuildingView绑定
    var teamBuildingView: Bool {
        get { path.contains(NavigationDestination.teamBuilding) }
        set {
            if newValue {
                path.append(NavigationDestination.teamBuilding)
            } else {
                if let index = path.firstIndex(of: NavigationDestination.teamBuilding) {
                    path.removeSubrange(index...)
                }
            }
        }
    }
    
    // 其他导航属性按同样方式封装
    var settingsView: Bool {
        get { path.contains(NavigationDestination.settings) }
        set {
            if newValue {
                path.append(NavigationDestination.settings)
            } else {
                if let index = path.firstIndex(of: NavigationDestination.settings) {
                    path.removeSubrange(index...)
                }
            }
        }
    }
    
    var continueScoreView: Bool {
        get { path.contains(NavigationDestination.continueScore) }
        set {
            if newValue {
                path.append(NavigationDestination.continueScore)
            } else {
                if let index = path.firstIndex(of: NavigationDestination.continueScore) {
                    path.removeSubrange(index...)
                }
            }
        }
    }
}

步骤3：修改主视图的NavigationStack #

绑定NavigationPath并通过枚举匹配导航目标：

struct MainMenuView: View {
    @ObservedObject var navigationState: NavigationState
        
    var body: some View {
        NavigationStack(path: $navigationState.path) {
            ZStack(alignment: .bottom) {               
                HStack {
                    Button {
                        if appSettings.resumeGame {
                            isShowingDisableModal = true
                        } else {
                            appSettings.resetGame()
                            navigationState.teamBuildingView = true
                        }
                    } label: {
                        Text(LocalizedStringKey("New Game"))
                    }
                    .buttonStyle(StartGameButtonStyle())
                    .disabled(isShowingDisableModal)
                    
                    if appSettings.resumeGame {
                        Button {
                            navigationState.continueScoreView = true
                        } label: {
                            Text(LocalizedStringKey("Continue"))
                        }
                        .buttonStyle(GameButtonStyle())
                        .disabled(isShowingDisableModal)
                    }
                }
            }
            .navigationBarTitleDisplayMode(.inline)
            .toolbar {
                ToolbarItem(placement: .navigationBarTrailing) {
                    CustomNavigationButton(action: {
                        navigationState.settingsView = true
                    }, imageName: "gearshape")
                    .font(.title2)
                    .opacity(isShowingDisableModal ? 0.5 : 1.0)
                    .disabled(isShowingDisableModal)
                }
            }
            .navigationDestination(for: NavigationDestination.self) { destination in
                switch destination {
                case .settings:
                    SettingsView()
                case .teamBuilding:
                    TeamBuildingView(navigationState: navigationState)
                case .continueScore:
                    TeamScoreView(navigationState: navigationState)
                case .startGame:
                    StartGameView(navigationState: navigationState)
                }
            }
        }
    }
}

步骤4：修改返回逻辑 #

在TeamScoreView中直接清空路径回到根视图，避免同时修改多个绑定：

struct TeamScoreView: View {    
    @ObservedObject var navigationState: NavigationState
    
    var body: some View {
        ZStack {
          // 原有视图代码
        }
        .navigationTitle(LocalizedStringKey("Team Scores"))
        .navigationBarBackButtonHidden(true)
        .toolbar {
            ToolbarItem(placement: .navigationBarLeading) {
                CustomNavigationButton(action: {
                    appSettings.resumeGame = true
                    navigationState.path = [] // 直接回到根视图
                }, imageName: "chevron.left")
                .opacity(appSettings.isGameOver ? 0 : 1)
            }
        }
    }
}

临时 workaround（不推荐长期使用） #

若暂时无法重构路径管理，可尝试将状态修改放在异步队列中，确保操作串行执行：

CustomNavigationButton(action: {
    appSettings.resumeGame = true
    DispatchQueue.main.async {
        navigationState.continueScoreView = false
        DispatchQueue.main.async {
            navigationState.teamBuildingView = false
        }
    }
}, imageName: "chevron.left")

该方法仅能临时规避崩溃，长期来看仍推荐使用NavigationPath的方式，更稳定且符合SwiftUI设计规范。

内容的提问来源于stack exchange，提问作者Oleksii Ruban