SwiftUI自定义带输入框Alert的Action无法更新Binding值问题

核心问题是UIKit的UIAlertController回调中修改SwiftUI状态变量时，未触发视图刷新，导致UIViewRepresentable的updateUIView方法未执行。原因在于UIAlertController的回调上下文与SwiftUI的视图更新机制存在适配问题，直接修改状态可能未被SwiftUI捕获。

解决步骤 #

1. 强制在主队列执行状态更新 #

SwiftUI的状态变更必须在主队列完成，即使UIAlertController回调默认在主队列，显式包裹主队列调度能确保状态变化被SwiftUI的更新机制捕获：

Button("Export") {
    alertTF(title: "Save as", message: "Please enter your file name", hintText: "my_file", primaryTitle: "Save", secondaryTitle: "cancel") { text in
        print(text)
        DispatchQueue.main.async {
            submittedName = text
            submittedExportRequest.toggle()
        }
    } secondaryAction: {
        print("cancelled")
    }
}

2. 检查submittedName的变量类型 #

如果submittedName是普通变量，修改它不会触发SwiftUI视图更新，需将其声明为@State（当前视图私有）或@Binding（来自父视图）：

@State private var submittedName = ""

3. 优化顶层ViewController获取逻辑 #

原rootController()方法可能无法正确获取当前最顶层的ViewController（如存在导航控制器、弹窗场景），递归获取顶层VC可避免上下文异常：

extension View {
    func alertTF(title: String, message: String, hintText: String, primaryTitle: String, secondaryTitle: String, primaryAction: @escaping (String) -> (), secondaryAction: @escaping () -> () ) {
        let alert = UIAlertController(title: title, message: message, preferredStyle: .alert)
        alert.addTextField { field in
            field.placeholder = hintText
        }
        
        alert.addAction(.init(title: secondaryTitle, style: .cancel, handler: { _ in
            DispatchQueue.main.async {
                secondaryAction()
            }
        }))
        
        alert.addAction(.init(title: primaryTitle, style: .default, handler: { _ in
            let text = alert.textFields?.first?.text ?? ""
            DispatchQueue.main.async {
                primaryAction(text)
            }
        }))
        
        topViewController().present(alert, animated: true, completion: nil)
    }
    
    private func topViewController() -> UIViewController {
        guard let windowScene = UIApplication.shared.connectedScenes.first as? UIWindowScene,
              let rootVC = windowScene.windows.first?.rootViewController else {
            return UIViewController()
        }
        return getTopViewController(from: rootVC)
    }
    
    private func getTopViewController(from vc: UIViewController) -> UIViewController {
        if let presentedVC = vc.presentedViewController {
            return getTopViewController(from: presentedVC)
        } else if let navVC = vc as? UINavigationController {
            return getTopViewController(from: navVC.topViewController ?? navVC)
        } else if let tabVC = vc as? UITabBarController {
            return getTopViewController(from: tabVC.selectedViewController ?? tabVC)
        }
        return vc
    }
}

4. 完善UIViewRepresentable的状态响应 #

确保ARViewWrapper的绑定逻辑正确，且执行导出后重置状态避免重复触发：

struct ARViewWrapper: UIViewRepresentable {
    @Binding var submittedExportRequest: Bool
    @Binding var exportedURL: URL?
    var submittedName: String
    
    func makeUIView(context: Context) -> ARView {
        ARView(frame: .zero)
    }
    
    func updateUIView(_ uiView: ARView, context: Context) {
        print("updateUIView triggered: \(submittedExportRequest)")
        if submittedExportRequest {
            // 执行导出逻辑
            // 完成后重置状态，确保下次点击能触发更新
            DispatchQueue.main.async {
                submittedExportRequest = false
            }
        }
    }
}

关键说明 #

• SwiftUI状态更新必须在主队列执行，显式DispatchQueue.main.async能规避UIKit与SwiftUI的上下文适配问题。
• 正确获取顶层ViewController可避免Alert弹出异常或回调失效。
• 导出逻辑执行后重置submittedExportRequest，确保状态变更能被SwiftUI重复捕获。

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