SwiftUI点击通知跳转指定页面返回路径异常问题求助

你遇到的核心问题是导航栈层级错误：当前实现是从DashboardScreen直接发起跳转到ChattingView，无论用户当前处于InboxView还是DashboardScreen，ChattingView都会被添加到DashboardScreen的导航栈顶部。这就导致当用户在InboxView时，点击通知跳转后的栈结构是DashboardScreen -> ChattingView，而非预期的DashboardScreen -> InboxView -> ChattingView，所以返回时会直接回到DashboardScreen。

需要调整导航逻辑，让ChattingView的跳转始终从InboxView层级发起，并根据用户当前页面状态自动补全导航路径，具体步骤如下：

1. 优化状态管理 #

在全局状态类中添加更精准的导航触发状态与数据存储：

// AppState.swift
class AppState: ObservableObject {
    @Published var isLoggedIn = false
    // 存储聊天跳转所需数据
    @Published var pendingChatData: ChatNotificationData?
    // 全局跳转触发信号
    @Published var triggerChatNavigation = false
}

// ChatAppState.swift（你的聊天状态类）
class ChatAppState: ObservableObject {
    @Published var notificationChatData: ChatNotificationData?
    @Published var notificationOrganisationId: String?
    // 供InboxView监听的跳转信号
    @Published var shouldOpenChat = false
}

2. 修改通知处理逻辑 #

在ContentView中，不再直接触发DashboardScreen的跳转，而是将数据存入全局状态并发送跳转信号：

// ContentView中的onNotification回调修改
.onNotification { notificationResponse in
    let userInfo = notificationResponse.notification.request.content.userInfo
    let (type, data) = NotificationHandler.shared.getNotificationTypeAndData(response: userInfo)
    guard type == NotificationType.chat, let chatData = data else { return }
    
    // 解析并存储聊天数据
    let parsedChatData = ChatNotificationHandler.shared.saveChatDataAfternotification(jsonBody: chatData)
    ChatConfigurationManager.shared.configure()
    
    // 设置全局状态，触发后续导航
    appState.pendingChatData = parsedChatData
    appState.triggerChatNavigation = true
}

3. 调整DashboardScreen的导航逻辑 #

让DashboardScreen根据用户当前位置，先导航到InboxView（如果不在的话），再由InboxView发起ChattingView跳转：

struct DashboardScreen: View {
    @EnvironmentObject var appState: AppState
    @EnvironmentObject var chatAppState: ChatAppState
    @State private var isNavigateToInbox = false
    
    var body: some View {
        NavigationStack {
            // Dashboard原有内容
            Button("进入收件箱") {
                isNavigateToInbox = true
            }
            
            // 导航到InboxView
            .navigationDestination(isPresented: $isNavigateToInbox) {
                InboxView()
            }
        }
        .onReceive(appState.$triggerChatNavigation) { shouldTrigger in
            guard shouldTrigger, let chatData = appState.pendingChatData else { return }
            
            // 先确保跳转到InboxView
            isNavigateToInbox = true
            // 延迟传递数据，确保InboxView已加载
            DispatchQueue.main.asyncAfter(deadline: .now() + 0.1) {
                chatAppState.notificationChatData = chatData
                chatAppState.shouldOpenChat = true
                // 重置全局状态
                appState.triggerChatNavigation = false
                appState.pendingChatData = nil
            }
        }
    }
}

4. 在InboxView中添加ChattingView导航 #

将ChattingView的导航目的地移到InboxView，并监听聊天状态的跳转信号：

struct InboxView: View {
    @EnvironmentObject var chatAppState: ChatAppState
    @State private var isNavigateToChatting = false
    
    var body: some View {
        // Inbox原有内容
        NavigationStack {
            // ...
        }
        // 导航到ChattingView
        .navigationDestination(isPresented: $isNavigateToChatting) {
            ChattingView(
                selectedRemoteUser: chatAppState.notificationChatData!,
                organizationId: chatAppState.notificationOrganisationId ?? "",
                isFromTransferring: false
            )
        }
        .onReceive(chatAppState.$shouldOpenChat) { shouldOpen in
            isNavigateToChatting = shouldOpen
            if shouldOpen {
                chatAppState.shouldOpenChat = false
            }
        }
    }
}

5. 修正ChattingView的返回逻辑 #

使用SwiftUI导航栈的原生返回逻辑，避免直接调用dismiss()跳过栈层级：

// ChattingView中的返回按钮回调修改
NavigationBarView(
    receiverDetail: viewModel.receiverDetail,
    userStatus: viewModel.receiverStatus,
    isUserTyping: viewModel.isRemoteUserTyping,
    onTapBackCallback: {
        viewModel.messagesDataArr.removeAll()
        // 使用导航栈的原生dismiss动作
        presentationMode.wrappedValue.dismiss()
    }
)

• 当用户在DashboardScreen时：点击通知会先跳转到InboxView，再自动跳转到ChattingView，返回路径为ChattingView -> InboxView -> DashboardScreen
• 当用户在InboxView时：点击通知会直接跳转到ChattingView，返回路径为ChattingView -> InboxView

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