SwiftUI从通知启动时navigationDestination竞态问题求助

问题背景 #

开发SwiftUI应用时遇到推送通知跳转异常：App完全关闭状态下点击通知启动，会导航到空白页面；后台状态下点击则能正常跳转。推测是App未完成视图渲染时，NavigationStack已尝试推入新视图导致的竞态问题。用DispatchQueue.main.asyncAfter(deadline: .now() + 5)延迟更新状态能解决，但5秒延迟体验极差，短延迟效果不稳定。同时无法调试关闭状态下的场景，尝试多种NavigationLink类型、调整.navigationDestination位置、改用极简视图均无效。

核心实现逻辑：通过AppDelegate的@Published布尔值openedFromNotification触发.navigationDestination跳转，自定义NotificationParser解析通知响应定位目标页面。

解决方案 #

1. 用NavigationStack路径管理替代布尔值触发 #

路径（Path）是SwiftUI导航的原生推荐方案，能更可靠地管理导航状态，避免竞态问题：

步骤1：创建导航状态管理器

class NavigationState: ObservableObject {
    @Published var path: [NavigationDestination] = []
    
    enum NavigationDestination: Hashable {
        case notification(UNNotificationResponse)
        // 可扩展其他跳转类型
    }
}

步骤2：在App中注入状态管理器

@main
struct navigationDestinationApp: App {
    @UIApplicationDelegateAdaptor(AppDelegate.self) var appDelegate
    @StateObject private var navigationState = NavigationState()
    
    var body: some Scene {
        WindowGroup {
            ContentView()
                .environmentObject(appDelegate)
                .environmentObject(navigationState)
        }
    }
}

步骤3：修改AppDelegate的通知处理逻辑

class AppDelegate: NSObject, UIApplicationDelegate, UNUserNotificationCenterDelegate, ObservableObject {
    weak var navigationState: NavigationState? // 弱引用避免循环引用
    
    func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
        // 通知授权逻辑...
        // 关联导航状态
        navigationState = (UIApplication.shared.connectedScenes.first?.delegate as? SceneDelegate)?.navigationState
        return true
    }
    
    func userNotificationCenter(_ center: UNUserNotificationCenter, didReceive response: UNNotificationResponse, withCompletionHandler completionHandler: @escaping () -> Void) {
        DispatchQueue.main.async {
            self.navigationState?.path.append(.notification(response))
        }
        completionHandler()
    }
}

步骤4：更新ContentView的导航逻辑

struct ContentView: View {
    @EnvironmentObject var appDelegate: AppDelegate
    @EnvironmentObject var navigationState: NavigationState
    
    var body: some View {
        NavigationStack(path: $navigationState.path) {
            VStack {
                Button("Schedule new notification") {
                    NotificationService().scheduleTimerNotification(title: "You asked for this!", subtitle: "Your app is ready to view", numSeconds: 5)
                }
            }
            .navigationDestination(for: NavigationState.NavigationDestination.self) { destination in
                switch destination {
                case .notification(let response):
                    NotificationParser().getNotificationDestination(response: response)
                }
            }
            .padding()
        }
    }
}

2. 延迟处理通知到App完全激活 #

将通知响应暂存，等待App进入活跃状态后再触发跳转，确保视图层级已初始化完成：

// 修改AppDelegate，暂存通知响应
class AppDelegate: NSObject, UIApplicationDelegate, UNUserNotificationCenterDelegate, ObservableObject {
    var pendingNotificationResponse: UNNotificationResponse?
    
    func userNotificationCenter(_ center: UNUserNotificationCenter, didReceive response: UNNotificationResponse, withCompletionHandler completionHandler: @escaping () -> Void) {
        DispatchQueue.main.async {
            self.pendingNotificationResponse = response
        }
        completionHandler()
    }
}

// 在SceneDelegate中处理活跃状态时的跳转
class SceneDelegate: UIResponder, UIWindowSceneDelegate {
    var window: UIWindow?
    @StateObject var navigationState = NavigationState()
    
    func sceneDidBecomeActive(_ scene: UIScene) {
        guard let appDelegate = UIApplication.shared.delegate as? AppDelegate,
              let response = appDelegate.pendingNotificationResponse else { return }
        
        navigationState.path.append(.notification(response))
        appDelegate.pendingNotificationResponse = nil
    }
}

3. 调试关闭状态下的跳转 #

• 配置Xcode Scheme：打开Edit Scheme > Run > Info，将Launch选项设为"Wait for executable to be launched"。
• 启动调试：点击Run后，手动关闭App，触发通知并点击启动，Xcode会自动附加调试器，控制台可输出日志。
• 添加关键日志：在userNotificationCenter(_:didReceive:)、sceneDidBecomeActive等方法中加入print语句，跟踪通知响应的流转过程。

4. 进阶方案：Deep Link处理跳转 #

在推送payload中添加自定义Deep Link，通过URL Scheme统一处理跳转，更灵活且符合iOS生态：

步骤1：配置URL Scheme

在Info.plist中添加URL Types，设置Identifier为com.yourapp.notification，URL Schemes为yourapp。

步骤2：处理Deep Link

class AppDelegate: NSObject, UIApplicationDelegate, UNUserNotificationCenterDelegate, ObservableObject {
    weak var navigationState: NavigationState?
    
    func application(_ app: UIApplication, open url: URL, options: [UIApplication.OpenURLOptionsKey : Any] = [:]) -> Bool {
        guard url.scheme == "yourapp", url.host == "notification" else { return false }
        
        let notificationId = url.lastPathComponent
        navigationState?.path.append(.notificationDetail(id: notificationId))
        return true
    }
    
    func userNotificationCenter(_ center: UNUserNotificationCenter, didReceive response: UNNotificationResponse, withCompletionHandler completionHandler: @escaping () -> Void) {
        if let deepLink = response.notification.request.content.userInfo["deepLink"] as? String,
           let url = URL(string: deepLink) {
            UIApplication.shared.open(url)
        }
        completionHandler()
    }
}

内容的提问来源于stack exchange，提问作者Donovan Smith