[Jest][3.5.0] `fireEvent.press` no longer reaches `Touchable` when its child is inside an `InterceptingGestureDetector`

Aperta
#4,689 4 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

@m-bert ci sta già lavorando.

Dal 13/11/2026.

  • #4694 di @m-bert — aperta

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
72/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
javascript, react-native, typescript
Ambito
frontend, testing

Direzione di ricerca

Start by reading useJSResponderHandler and the changes from #4530 that add onStartShouldSetResponder to InterceptingGestureDetector; inspect the Jest setup and press handling in the reproduction. Run the two fireEvent.press cases with the listed React Native Testing Library version. Done means the wrapped-child case invokes onPress once while the plain-child case continues to pass.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Missing info Platform: Web
Description

Since 3.5.0, fireEvent.press from @testing-library/react-native no longer reaches a Touchable's onPress when the pressed element sits inside an InterceptingGestureDetector. The same test passes on 3.4.0.

The change comes from #4530. InterceptingGestureDetector now sets onStartShouldSetResponder on its host view, and the handler from useJSResponderHandler always returns false:

const handleStartShouldSetResponder = useCallback(() => {
  if (gesture !== undefined && isSupportedGesture(gesture, countNativeAsHandled)) {
    updateResponderEventValue(jsResponderContext, true);
  }

  return false;
}, [jsResponderContext, gesture, countNativeAsHandled]);

When testing-library dispatches a press, it walks up from the target and takes the nearest element with onStartShouldSetResponder as the touch responder. If that responder returns false, testing-library treats the touch as declined and skips every onPress above it.

Steps to reproduce
import 'react-native-gesture-handler/jest-setup';

import { fireEvent, render, screen } from '@testing-library/react-native';
import { Text } from 'react-native';
import {
  GestureHandlerRootView,
  InterceptingGestureDetector,
  Touchable,
} from 'react-native-gesture-handler';

describe('fireEvent.press on a child of a Touchable', () => {
  it('reaches onPress when the child is a plain Text', async () => {
    const onPress = jest.fn();

    await render(
      <GestureHandlerRootView>
        <Touchable onPress={onPress}>
          <Text>Press me</Text>
        </Touchable>
      </GestureHandlerRootView>
    );

    await fireEvent.press(screen.getByText('Press me'));

    expect(onPress).toHaveBeenCalledTimes(1); // passes
  });

  it('reaches onPress when the Text is wrapped in an InterceptingGestureDetector', async () => {
    const onPress = jest.fn();

    await render(
      <GestureHandlerRootView>
        <Touchable onPress={onPress}>
          <InterceptingGestureDetector>
            <Text>Press me</Text>
          </InterceptingGestureDetector>
        </Touchable>
      </GestureHandlerRootView>
    );

    await fireEvent.press(screen.getByText('Press me'));

    expect(onPress).toHaveBeenCalledTimes(1); // fails on 3.5.0, passes on 3.4.0
  });
});
A link to a Gist, an Expo Snack or a link to a repository based on this template that reproduces the bug.
Gesture Handler version

3.5.0

React Native version

0.86.3

Platforms

Web

JavaScript runtime

None

Workflow

None

Build type

None

Device

None

Device model

@testing-library/react-native 14.1.0, jest 30.5.2, jest-expo 57.0.5

Acknowledgements

Yes

Lingua principale
TypeScript
Stelle
6.8k
Fork
1.1k
Merge medio
1g 23h
PR unite (30g)
46

Preparare l'ambiente

  • Nessun Dockerfile né file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di software-mansion/react-native-gesture-handler

Tutte le issue di software-mansion/react-native-gesture-handler

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.