嵌套视图中UILabel无法接收触摸事件，如何测试响应者链？

Hey Jim, let's work through your touch event problem—nested views and stack views can trip up even experienced devs, so let's break this down clearly.

核心问题：为什么你的嵌套Label不响应触摸？ #

First, let's recap how the responder chain works: when a touch occurs, iOS starts at the topmost visible view and uses hitTest(_:with:) to check if it can handle the event. If not, it traverses up the view hierarchy until it finds a responder that can. The key issue here is almost certainly parent views blocking the touch event before it reaches your nested Label.

1. StackView的影响：检查父视图的isUserInteractionEnabled #

UIStackView has isUserInteractionEnabled = true by default, but here's the critical detail: every parent view in the chain leading to your target Label must have isUserInteractionEnabled = true for the touch to pass through. You mentioned you only enabled this property for the nested Label—but all intermediate views (the vertical StackView, horizontal StackView, the UIView wrapping the Label, and the colorView in your makeColorItem function) need this set to true (which is the default for UIView, but it's worth double-checking you didn't disable it accidentally elsewhere).

If any parent view has isUserInteractionEnabled = false, it will absorb the touch event and not pass it down to child views—this is the most common cause of your issue.

2. 是否需要将部分视图的isUserInteractionEnabled设为False？ #

No—quite the opposite. You need to ensure all parent views along the path to your target Label have isUserInteractionEnabled = true. You'd only set this to false if you want a view to ignore touches entirely (like a purely decorative element). Since your StackViews and container views are just layout containers, they should keep this enabled so touches can reach their interactive children.

3. 如何给响应者链添加日志，找出阻塞点？ #

The best way to debug this is to override hitTest(_:with:) to log exactly which views iOS checks during the touch process. Add this extension to your project:

extension UIView {
    open override func hitTest(_ point: CGPoint, with event: UIEvent?) -> UIView? {
        let result = super.hitTest(point, with: event)
        print("Hit test on \(self) returned \(result ?? nil)")
        return result
    }
}

Run your app, tap the unresponsive area, and check the console. You'll see which view is "catching" the touch instead of passing it to your Label. Common culprits include:

• A parent view with isUserInteractionEnabled = false
• A view that's accidentally covering your target Label (verify your constraints are positioning the Label correctly)
• A gesture recognizer on a parent view with cancelsTouchesInView = true (this cancels touches from reaching child views)

你的代码中的潜在问题 #

Looking at your makeColorItem function, there's a critical mistake that could break touch events and layout:

1. Duplicate superview assignment: You're adding colorView to self.view directly with self.view.addSubview(colorView), then returning it to be added to your StackView. A UIView can only have one superview at a time—iOS will automatically remove colorView from self.view when you add it to the StackView, but this causes unexpected layout issues and can disrupt touch event routing. Remove self.view.addSubview(colorView) entirely; you should only add colorView to the StackView when building your layout.

2. Unnecessary subview check in tapColor: Your current code tries to access v?.subviews.first as? UILabel, but v is colorChoice—the Label itself—so its subviews array is empty. Simplify the function to directly use the sender's view:

@objc func tapColor(sender:UITapGestureRecognizer) {
    print("A Color was tapped...with tag:\(sender.view?.tag ?? -1)")
    guard let colorLabel = sender.view as? UILabel else { return }
    colorNumber = colorLabel.tag
    print("The \(colorLabel.text ?? "unknown") label was tapped.")
}

关于自定义hitTest的疑问 #

You mentioned wondering why you might need to customize hitTest—this is only necessary for edge cases: for example, if you want a view to respond to touches outside its bounds, or if you need to override default hit test behavior (like ignoring certain subviews). In your scenario, you shouldn't need a custom hitTest implementation if you fix the parent view interaction settings and duplicate superview issue.

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