iOS15及以下SwiftUI大视图双击坐标获取的性能优化问题

一、修复当前UIViewControllerRepresentable方案的性能问题 #

你遇到的CPU飙升，核心原因是UIHostingController与SwiftUI大视图的联动更新没有做精准控制，导致子视图调整时触发了全局不必要的重绘和状态刷新。可以从这几点优化：

• 缩小UIHostingController的包裹范围：不要把整个LazyHStack塞进控制器，只给需要监听双击的子视图单独添加手势封装容器，避免大视图更新时全局刷新。
• 限制updateUIViewController的执行逻辑：在该方法中添加条件判断，只有当子视图高度等关键属性确实变化时，才更新UIHostingController的内容，不要每次都执行全量配置。
• 用@StateObject管理状态：如果封装视图内有状态变量，使用@StateObject初始化，避免每次视图刷新都重建状态对象，减少无效刷新次数。

二、替代实现方案（规避原有限制） #

1. 轻量自定义手势容器（推荐） #

不嵌套整个大视图的UIHostingController，而是封装仅处理双击手势的UIViewRepresentable容器，将SwiftUI子视图嵌入其中。这种方式既不干扰原有DragGesture，又能精准获取双击位置，且性能开销极低：

struct DoubleTapGestureWrapper<Content: View>: UIViewRepresentable {
    let content: Content
    let onDoubleTap: (CGPoint) -> Void
    
    func makeUIView(context: Context) -> UIView {
        let containerView = UIView()
        // 添加双击手势识别器
        let doubleTapGesture = UITapGestureRecognizer(
            target: context.coordinator,
            action: #selector(Coordinator.handleDoubleTap(_:))
        )
        doubleTapGesture.numberOfTapsRequired = 2
        containerView.addGestureRecognizer(doubleTapGesture)
        
        // 嵌入SwiftUI子视图
        let hostingVC = UIHostingController(rootView: content)
        hostingVC.view.translatesAutoresizingMaskIntoConstraints = false
        containerView.addSubview(hostingVC.view)
        NSLayoutConstraint.activate([
            hostingVC.view.topAnchor.constraint(equalTo: containerView.topAnchor),
            hostingVC.view.leadingAnchor.constraint(equalTo: containerView.leadingAnchor),
            hostingVC.view.trailingAnchor.constraint(equalTo: containerView.trailingAnchor),
            hostingVC.view.bottomAnchor.constraint(equalTo: containerView.bottomAnchor)
        ])
        
        return containerView
    }
    
    func updateUIView(_ uiView: UIView, context: Context) {
        // 仅在子视图内容确实更新时刷新
        guard let hostingVC = uiView.subviews.first?.next as? UIHostingController<Content> else { return }
        hostingVC.rootView = content
    }
    
    func makeCoordinator() -> Coordinator {
        Coordinator(onDoubleTap: onDoubleTap)
    }
    
    class Coordinator: NSObject {
        private let onDoubleTap: (CGPoint) -> Void
        
        init(onDoubleTap: @escaping (CGPoint) -> Void) {
            self.onDoubleTap = onDoubleTap
        }
        
        @objc func handleDoubleTap(_ gesture: UITapGestureRecognizer) {
            let tapLocation = gesture.location(in: gesture.view)
            onDoubleTap(tapLocation)
        }
    }
}

// 使用方式
LazyHStack {
    ForEach(items) { item in
        DoubleTapGestureWrapper(content: YourItemView(item: item)) { location in
            // 处理双击位置逻辑
        }
    }
}

2. 手势识别器代理协调共存 #

SwiftUI的TapGesture和DragGesture冲突，但可以通过UIKit手势代理调整优先级，让两者共存。在上面的DoubleTapGestureWrapper中，给协调器添加UIGestureRecognizerDelegate实现：

class Coordinator: NSObject, UIGestureRecognizerDelegate {
    private let onDoubleTap: (CGPoint) -> Void
    
    init(onDoubleTap: @escaping (CGPoint) -> Void) {
        self.onDoubleTap = onDoubleTap
    }
    
    @objc func handleDoubleTap(_ gesture: UITapGestureRecognizer) {
        let tapLocation = gesture.location(in: gesture.view)
        onDoubleTap(tapLocation)
    }
    
    // 允许双击手势与拖拽手势同时识别（可根据需求调整）
    func gestureRecognizer(_ gestureRecognizer: UIGestureRecognizer, shouldRecognizeSimultaneouslyWith otherGestureRecognizer: UIGestureRecognizer) -> Bool {
        return true
    }
    
    // 设置双击手势优先识别，失败后再触发拖拽手势
    func gestureRecognizer(_ gestureRecognizer: UIGestureRecognizer, shouldBeRequiredToFailBy otherGestureRecognizer: UIGestureRecognizer) -> Bool {
        return gestureRecognizer is UITapGestureRecognizer
    }
}

然后在makeUIView中给手势设置代理：

doubleTapGesture.delegate = context.coordinator

3. 纯SwiftUI模拟双击（备选） #

如果不想依赖UIKit，可以用PreferenceKey结合单次点击手势模拟双击逻辑：

• 用@State记录第一次点击的位置和时间戳
• 第二次点击时，判断时间间隔（比如0.3秒内）和位置距离（比如20pt内），满足则判定为双击
• 通过PreferenceKey传递子视图的点击位置（解决iOS15onTapGesture无location参数的问题）

示例代码：

struct TapLocationPrefKey: PreferenceKey {
    static var defaultValue: CGPoint = .zero
    static func reduce(value: inout CGPoint, nextValue: () -> CGPoint) {
        value = nextValue()
    }
}

struct DoubleTapSimulator<Content: View>: View {
    let content: Content
    let onDoubleTap: (CGPoint) -> Void
    @State private var lastTapLoc: CGPoint = .zero
    @State private var lastTapTime: Date = .distantPast
    
    var body: some View {
        content
            .anchorPreference(key: TapLocationPrefKey.self, value: .bounds) { anchor in
                CGPoint(x: anchor.midX, y: anchor.midY)
            }
            .onTapGesture {
                let currentLoc = TapLocationPrefKey.defaultValue
                let currentTime = Date()
                let interval = currentTime.timeIntervalSince(lastTapTime)
                
                if interval < 0.3 && distanceBetween(lastTapLoc, currentLoc) < 20 {
                    onDoubleTap(currentLoc)
                    lastTapTime = .distantPast
                } else {
                    lastTapLoc = currentLoc
                    lastTapTime = currentTime
                }
            }
            .backgroundPreferenceValue(TapLocationPrefKey.self) { _ in
                Color.clear // 触发Preference更新
            }
    }
    
    private func distanceBetween(_ p1: CGPoint, _ p2: CGPoint) -> CGFloat {
        sqrt(pow(p1.x - p2.x, 2) + pow(p1.y - p2.y, 2))
    }
}

注意该方案需要结合GeometryReader进一步校准位置，模拟逻辑的精准度略逊于原生手势胜在纯SwiftUI实现。

三、总结 #

• 若保留原有方案，核心是限制重绘范围和无效更新；
• 优先选择轻量自定义手势容器，兼顾功能和性能；
• 纯SwiftUI模拟方案可作为无UIKit依赖的备选。

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