XCUIElement存在但不可点击：UI测试自定义单元格视图问题问询

Hey there, I’ve run into this exact scenario a handful of times with UI tests—where a visually visible view reports as not hittable, even though it looks like it should be. Let’s break down the most likely causes and how to fix them:

1. Hidden Overlays or Clipped Bounds #

Even if your topMarker looks fully visible, there might be an invisible view (like a transparent overlay, or a parent view with clipsToBounds = true) blocking it, or its frame might extend outside the parent’s interactive area.

• How to check: Pause your test at the failure breakpoint and open Xcode’s Debug View Hierarchy tool. This lets you inspect the full view stack—look for any views sitting on top of topMarker, and verify its frame fits entirely within its parent’s bounds.
• Quick code check: Print key properties to confirm:

  let topMarker = app.otherElements["topMarker"]
  print("Top Marker Frame: \(topMarker.frame)")
  print("Parent View Bounds: \(topMarker.parent?.frame ?? .zero)")
  

2. Disabled User Interaction #

It’s easy for userInteractionEnabled to get flipped to false accidentally—maybe in your cell’s layout code, or a state change you didn’t account for.

• Verify: Use the Debug View Hierarchy to check the userInteractionEnabled flag for topMarker, or add an assertion in your test:

  XCTAssertTrue(topMarker.isUserInteractionEnabled, "Top marker should allow user interaction")
  

3. Layout Delay from Table View Scrolling/Reuse #

If the cell containing topMarker was just scrolled into view, the layout system might not have finished positioning the view yet when your test checks isHittable.

• Fix: Add an expectation to wait for the view to become hittable:

  let hittablePredicate = NSPredicate(format: "isHittable == true")
  expectation(for: hittablePredicate, evaluatedWith: topMarker, handler: nil)
  waitForExpectations(timeout: 5, handler: nil)
  

4. isHittable’s Strict Rules #

Apple’s documentation for isHittable has more requirements than just "visually visible":

The element must be within the screen’s visible bounds, not blocked by any non-transparent views, and have user interaction enabled.

Even a tiny part of topMarker extending outside the window or safe area can make it report as not hittable.

• Check details: Print these properties to narrow it down:

  print("Is Visible: \(topMarker.isVisible)")
  print("Is Hittable: \(topMarker.isHittable)")
  print("Attached to Window: \(topMarker.window != nil)")
  

5. Custom hitTest Logic #

If topMarker (or any of its parent views) is a custom UIView subclass that overrides hitTest(_:with:), the method might be intercepting touches and returning a different view (or nil) instead of topMarker.

• Review code: Check your custom view’s hitTest implementation to ensure it returns self when the touch point is within its bounds.

Pro Tip for Debugging #

Split your assertions to isolate the issue better—this way you’ll know for sure if the view exists but just isn’t hittable:

XCTAssertTrue(topMarker.exists, "Top marker should be present in the view hierarchy")
XCTAssertTrue(topMarker.isHittable, "Top marker should be tappable")

内容的提问来源于stack exchange，提问作者Reinhard Männer