Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Replayed taps refused with "no confirmed resting position" since 0.21.29

Abierto
  • ¿Algo no está bien?
#3,981 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
55/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
android, react-native, typescript
Área
mobile, testing

Línea de trabajo

Start by reading the runtime gate and settle handling changes in #3631, #3570, and #3640, then compare the post-gesture settling changes in #3868, #3869, and #3915. Reproduce with the 23-test suite on an API 34 emulator, comparing 0.21.28 with the affected versions. Done means the same recordings replay without “no confirmed resting position” refusals.

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

Descripción

bug ready-for-agent

Purpose. Replaying a recorded tap on an Android Compose app stopped working reliably after 0.21.28. The tap is refused with:

ENGINE_FAILURE: The target had no confirmed resting position when the transition window after the previous action ran out, so nothing was dispatched.

The target is on screen and not moving; the screenshot at failure shows the screen fully loaded.

What we see. We replay a 23-test suite through e2e 0.21.3 and @e2e-dev/mobile 0.12.4 (strict cache) on an API 34 emulator, with the same app build and recordings for every version:

agent-device Result
0.21.28 Passes, about 15 runs with no refusals
0.21.29 Tap on an overflow button on a profile screen refused, 4 of 4 runs
0.21.30 Passed once, then a tap on the first row of a LazyColumn refused
0.21.31 Both taps refused, 2 of 2 runs
0.21.32 Both taps refused

Both refused taps come right after a navigation (opening a tab, or opening the profile screen). It starts in 0.21.29, which moved the moving-target decision into the runtime gate (#3631) and changed settle handling (#3570, #3640). 0.21.31 and 0.21.32 changed post-gesture settling again (#3868, #3869, #3915) and it got more frequent.

Required behavior. A tap on a target that is on screen and still is dispatched, as in 0.21.28.

Done when. The same recordings replay on the new version with no "no confirmed resting position" refusals.

Dependencies. None. We are pinned to 0.21.28 until this is fixed.

Lenguaje dominante
TypeScript
Estrellas
5.2k
Forks
359
Merge medio
12 h 48 min
PR fusionados (30 d)
657

Preparar el entorno

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 callstack/agent-device

Todos los issues de callstack/agent-device

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.