UIKit与SwiftUI跨栈导航问题：双导航栏及转场异常

一、解决双导航栏问题 #

核心是统一导航栈的管理逻辑，避免UIKit和SwiftUI导航栏同时生效：

• 方案1：UIKit主导整个导航栈
  从UIKit页面推送SwiftUI页面时，用UIHostingController直接包装SwiftUI View，保留UIKit导航栏，SwiftUI内部不再使用NavigationStack。SwiftUI页面的跳转需求通过闭包回调给上层UIKit导航控制器处理，全程由UIKit的UINavigationController统一管理栈结构。
  示例代码：

  // SwiftUI的Screen2
  struct Screen2: View {
      let pushScreen3: () -> Void
      
      var body: some View {
          Button("跳转到Screen3") {
              pushScreen3()
          }
      }
  }
  
  // UIKit中触发跳转逻辑
  let screen2 = Screen2(pushScreen3: {
      let screen3 = Screen3(pushScreen4: {
          let screen4VC = Screen4ViewController()
          self.navigationController?.pushViewController(screen4VC, animated: true)
      })
      let screen3VC = UIHostingController(rootView: screen3)
      self.navigationController?.pushViewController(screen3VC, animated: true)
  })
  let screen2VC = UIHostingController(rootView: screen2)
  navigationController?.pushViewController(screen2VC, animated: true)
  

• 方案2：SwiftUI主导整个导航栈
  将初始UIKit页面和目标UIKit页面都包装成UIViewControllerRepresentable，放入SwiftUI的NavigationStack中管理，全程仅使用SwiftUI导航栏。所有跳转通过navigationDestination统一处理，避免双栏冲突。
  示例代码：

  // 包装UIKit的Screen1
  struct Screen1Representable: UIViewControllerRepresentable {
      func makeUIViewController(context: Context) -> Screen1ViewController {
          Screen1ViewController()
      }
      
      func updateUIViewController(_ uiViewController: Screen1ViewController, context: Context) {}
  }
  
  // 包装UIKit的Screen4
  struct Screen4Representable: UIViewControllerRepresentable {
      func makeUIViewController(context: Context) -> Screen4ViewController {
          Screen4ViewController()
      }
      
      func updateUIViewController(_ uiViewController: Screen4ViewController, context: Context) {}
  }
  
  // 主导航入口
  struct MainNavigation: View {
      @State private var path = NavigationPath()
      
      var body: some View {
          NavigationStack(path: $path) {
              Screen1Representable()
                  .navigationDestination(for: String.self) { value in
                      if value == "Screen2" {
                          Screen2()
                              .navigationDestination(for: String.self) { val in
                                  if val == "Screen3" {
                                      Screen3()
                                          .navigationDestination(for: String.self) { _ in
                                              Screen4Representable()
                                          }
                                  }
                              }
                      }
                  }
          }
      }
  }
  

二、解决Screen3到Screen4的转场异常问题 #

转场异常本质是导航栈管理混乱导致的，需配合上述统一方案修正：

• 若用UIKit主导导航栈：
  禁止在SwiftUI内部直接调用UIKit的导航方法，所有跳转通过闭包传递给上层UIKit导航控制器执行pushViewController，确保转场动画与UIKit原生逻辑一致。

• 若用SwiftUI主导导航栈：
  必须将Screen4包装成UIViewControllerRepresentable，通过navigationDestination触发跳转，而非直接调用UIKit导航API，让SwiftUI统一管理转场动画和栈结构。

注意：绝对不要混合两种导航栈的跳转方式，比如在SwiftUI的NavigationStack中直接调用UIKit的pushViewController，这会导致栈结构紊乱，引发转场异常和导航流程断裂。

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