From 3464ea4c635884b5efa38a6b537b561816ed636c Mon Sep 17 00:00:00 2001 From: Samuel Newman Date: Sun, 19 Jul 2026 11:42:36 +0300 Subject: [PATCH] fix stale emulator provisioning description in testing docs Co-Authored-By: Claude Fable 5 --- docs/testing.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/testing.md b/docs/testing.md index 908b89e96e..1bc2af46c5 100644 --- a/docs/testing.md +++ b/docs/testing.md @@ -41,8 +41,8 @@ The jobs run Maestro CLI 2.6.1 locally on GitHub Actions; Maestro Cloud is not used. iOS runs on `macos-26-xlarge` with Xcode 26.4. Android runs on `Linux-x64-32core`. Both use Java 17 and the Node and pnpm versions declared in `package.json`. The iOS job selects an iPhone 17 simulator running iOS 26.5; -Android uses `reactivecircus/android-emulator-runner` to provision a Pixel 6 AVD -with the API 35 Google APIs x86_64 image. +Android directly provisions and boots a Pixel 6 AVD with the API 35 Google APIs +x86_64 image using the Android SDK command-line tools. Both development clients use the `e2e` EAS profile and the same reusable local EAS build action as the release build workflows; the resulting simulator app and APK are installed directly on the selected devices.