Android E2E CI's Maestro 2.6.1 types a space for `pressKey: tab`

Abierto Apto para principiantes
#60,177 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
78/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
android, github-actions
Área
ci-cd, mobile

Línea de trabajo

Lee .github/actions/maestro-android/action.yml para comprobar la versión de Maestro que utiliza Android E2E CI y luego ejecuta el reproductor vinculado o inspecciona su flujo en busca de pressKey: tab. Confirma el comportamiento en Android y compáralo con el comportamiento esperado indicado para Maestro 2.12.1. La tarea estará terminada cuando la configuración de CI deje de usar una versión que escriba un espacio al pulsar Tab y la navegación con Tab en Android funcione como se espera.

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

Descripción

Needs: Triage :mag: Platform: Android
Description

.github/actions/maestro-android/action.yml installs Maestro 2.6.1:

run: export MAESTRO_VERSION=2.6.1; curl -Ls "https://get.maestro.mobile.dev" | bash

On Android, Maestro 2.6.1's pressKey: tab sends keyevent 62, KEYCODE_SPACE, rather than 61, KEYCODE_TAB (AndroidDriver.kt L307, sent at L319). So in test_e2e_android_rntester, a flow that presses Tab in RNTester types a space into the focused TextInput, and keyboard focus stays on it. No flow on main presses Tab yet; one that tests Tab navigation cannot pass under this pin.

Maestro sends 61 since mobile-dev-inc/Maestro#3679, first released in cli-2.12.0 (AndroidDriver.kt L310 at cli-2.12.0).

#59048's keyboard-focus-exclusion.yml met this in Test All, where its pressKey: tab typed a space, so that flow presses the D-pad instead.

Steps to reproduce
  1. On an Android 15 emulator (google_apis, x86_64), install the rntester-release artifact's app-arm64-v8a-release.apk from a main Test All run, the APK test_e2e_android_rntester installs.
  2. Install Maestro the way the action does: export MAESTRO_VERSION=2.6.1; curl -Ls "https://get.maestro.mobile.dev" | bash.
  3. Open rntester://example/TextInput/uncontrolledComponent.
  4. Run a flow that taps uncontrolled-textinput, runs eraseText, then pressKey: tab.
  5. Read the TextInput's text and focus (adb shell uiautomator dump).

./reproduce.sh in the reproducer does all of this with one emulator or device on adb: it takes the newest main commit whose Test All run passed, reads the Maestro version that commit's maestro-android/action.yml installs, downloads that run's rntester-release APK, and installs Maestro into its own folder. It exits 1 while Tab types into the TextInput and 0 once the TextInput stays empty.

Expected: pressKey: tab types nothing into the TextInput and moves keyboard focus off it, as the same flow does under Maestro 2.12.1 (REPRO_MAESTRO_VERSION=2.12.1 ./reproduce.sh).
Seen: the TextInput holds a space and keeps focus:

after tapOn + eraseText: uncontrolled-textinput text="" focused=true
after pressKey: tab: uncontrolled-textinput text=" " focused=true
React Native Version

0.90.0-nightly-20261120-bbfd39149

Affected Platforms

Runtime - Android

Output of npx @react-native-community/cli info
host: MINGW64_NT-10.0-26300 3.6.10-5a1665c8.x86_64 x86_64; openjdk version "17.0.20.1" 2026-08-18 LTS; Android Debug Bridge version 1.0.41
device: Android 15 (API 35), ABIs x86_64,arm64-v8a, input method com.google.android.inputmethod.latin/com.android.inputmethod.latin.LatinIME
Stacktrace or Logs
react-native main bbfd391496baa6e0461262f76f1ae9a819a7ecd2, Test All run https://github.com/react/react-native/actions/runs/44614513110
.github/actions/maestro-android/action.yml at bbfd391496: export MAESTRO_VERSION=2.6.1; curl -Ls "https://get.maestro.mobile.dev" | bash
APK: rntester-release/app-arm64-v8a-release.apk, 12599927 bytes
Maestro CLI: 2.6.1
device: Android 15 (API 35), ABIs x86_64,arm64-v8a, input method com.google.android.inputmethod.latin/com.android.inputmethod.latin.LatinIME
opened rntester://example/TextInput/uncontrolledComponent in com.facebook.react.uiapp
after tapOn + eraseText: uncontrolled-textinput text="" focused=true
after pressKey: tab: uncontrolled-textinput text=" " focused=true
SUMMARY: Maestro 2.6.1, pressKey: tab typed " " into the TextInput it had focused (focused=true after it) on react-native main bbfd391496
MANDATORY Reproducer

https://github.com/YevheniiKotyrlo/rn-ci-maestro-tab-types-space

Screenshots and Videos

No response

Lenguaje dominante
C++
Estrellas
127k
Forks
25.5k
Merge medio
3 d 17 h
PR fusionados (30 d)
302

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 react/react-native

Todos los issues de react/react-native

Issues similares

Más issues de C++

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.