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

未關閉 適合新手
#60,177 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 2 天內回覆

還沒有人認領這個 Issue。

評估

難度
2/5
預估耗時
1-3 小時
新手友好度
78/100
Issue 類型
缺陷
描述清晰度
描述清楚
活躍度
活躍
技術堆疊
android, github-actions
領域
ci-cd, mobile

研究方向

閱讀 .github/actions/maestro-android/action.yml,檢查 Android E2E CI 使用的 Maestro 版本,接著執行連結的重現程式,或檢查其流程中的 pressKey: tab。確認 Android 上的行為,並與 Maestro 2.12.1 下所述的預期行為比較。當 CI 設定不再使用會在按 Tab 時輸入空格的版本,且 Android 上的 Tab 導覽符合預期時,工作即告完成。

由索引模型根據 Issue 內容生成。

描述

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

主要語言
C++
星號
127k
分支
25.5k
平均合併
3 天 17 小時
30 天內合併 PR
302

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

react/react-native 的其他 Issue

查看 react/react-native 的全部 Issue

相似的 Issue

更多 C++ Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。