[Android] Fix Intercepting and Virtual detectors hit testing

[Copilot]

PR #3981 changed the hit-test condition in GestureHandler.handle() from view is RNGestureHandlerDetectorView to hostDetectorView != null, which is too broad — hostDetectorView is set for all handler types (regular, native, virtual, intercepting), but the detector-child coordinate transform should only run when the handler's view is the detector itself.

For Virtual/Intercepting handlers, the event is already in the virtual child's coordinate space. Entering the detector branch applies a bogus transform, breaking x/y and isWithinBounds.

Fix

Added view == detectorView to the condition so the multi-child hit test only runs when the handler is bound directly to the detector view:

// Before (broken): enters branch for all handlers with a hostDetectorView
if (detectorView != null && detectorView.isNotEmpty()) {

// After: only enters for handlers whose view IS the detector
if (detectorView != null && view == detectorView && detectorView.isNotEmpty()) {

[Copilot]

Pull request overview

Refines Android hit-testing in GestureHandler.handle() so the detector-child coordinate transform only runs when the handler is attached directly to the RNGestureHandlerDetectorView, fixing incorrect x/y and bounds checks for virtual (and related) detector-attached handlers.

Changes:

• Tightens the multi-child detector hit-test condition by requiring view == detectorView.
• Prevents applying an extra (incorrect) detector→child coordinate transform for handlers whose events are already in the child’s coordinate space.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.