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

Abierto
#4,689 4 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

@m-bert ya está trabajando en esto.

Desde el 13/11/2026.

  • #4694 de @m-bert — abierto

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
72/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
javascript, react-native, typescript
Área
frontend, testing

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

Lenguaje dominante
TypeScript
Estrellas
6.8k
Forks
1.1k
Merge medio
1 d 23 h
PR fusionados (30 d)
46

Preparar el entorno

  • Sin Dockerfile ni archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de software-mansion/react-native-gesture-handler

Todos los issues de software-mansion/react-native-gesture-handler

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.