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

Aberta Para iniciantes
#60,177 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 2 dias

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
2/5
Tempo estimado
1-3 horas
Facilidade para iniciantes
78/100
Tipo de issue
Bug
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
android, github-actions
Domínio
ci-cd, mobile

Direção de pesquisa

Leia .github/actions/maestro-android/action.yml para verificar a versão do Maestro usada pelo Android E2E CI e, em seguida, execute o reprodutor vinculado ou inspecione seu fluxo em busca de pressKey: tab. Confirme o comportamento no Android e compare-o com o comportamento esperado indicado para o Maestro 2.12.1. A tarefa estará concluída quando a configuração de CI deixar de usar uma versão que digita um espaço para Tab e a navegação por Tab no Android funcionar como esperado.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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

Linguagem predominante
C++
Estrelas
127k
Forks
25.5k
Merge médio
3d 17h
PRs com merge (30d)
302

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de react/react-native

Todas as issues de react/react-native

Issues semelhantes

Mais issues de C++

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.