Eve library

V9-004 Android mobile E2E execution

Evidence

Revision 1

On this page

Date: 2026-07-27

Repository commit under test: cd35d8a0dd88

Outcome#

The Metis Expo application and its critical learner path passed a real Maestro run on an Android 15 API 35 emulator. The machine-readable result records one test, zero failures, SUCCESS, and 1,312 seconds: evidence/v1-v9/V9-004-mobile-e2e-junit.xml.

The executed path opened the application through Expo Go and verified:

  1. the Metis learner home and resumable lesson state;
  2. Course Play and its transcript action;
  3. the formative assessment and its short-check action;
  4. Downloads and its offline-bundle action;
  5. the degraded Tutor surface and text-tutor action status; and
  6. the grounded-source panel and visible Grounded Sources heading.

The checked-in recovery flow is apps/metis/mobile/e2e/flows/smoke-expo-go.yaml. It uses stable React Native accessibility IDs for action and surface assertions and resets both vertical and horizontal scroll state between surfaces. Paired horizontal gestures cover the two tab-rail positions observed under software rendering.

Runtime and command#

  • Android Emulator: 36.5.11.0 (15261927)
  • AVD: oshun_atd_api35
  • Android: 15, build AE3A.240806.019
  • Acceleration: software TCG (/dev/kvm absent)
  • Emulator command: headless, no audio or boot animation, SwiftShader, -memory 1536, -accel off, no snapshot
  • True completed boot: 538,060 ms
  • Expo Go: 57.0.2, 208,277,642 bytes
  • Expo Go SHA-256: 7eaf937383be1677cfae2fb2711e2066f5c3be2c369a24af3b76699a3589effc
  • Maestro: 2.5.1
  • Metro: port 8081 with adb reverse tcp:8081 tcp:8081
  • Command: MAESTRO_DRIVER_STARTUP_TIMEOUT=900000 maestro test --format junit --output /tmp/v9-004-maestro-junit-passed.xml e2e/flows/smoke-expo-go.yaml

Software TCG required a 900-second Maestro driver startup allowance. The Maestro driver packages were installed without streamed ADB transport and ahead-of-time compiled because streamed installs and interpreted startup had previously destabilized or timed out on this emulator. Host memory stayed above 9 GiB available throughout the supervised run.

Recovery from the earlier blocked attempt#

The 2026-07-25 attempt reached a true API 35 boot but Expo Go streamed installs destabilized Android's package service, so no application assertion ran. That result remains useful failure history, but it is superseded as the execution status by this successful non-streamed install and warmed-runtime run. Expo's temporary .gitignore and tsconfig.json edits were reverted after Metro startup.

Honest boundary#

This is a developer-runtime Expo Go pass, not a packaged release APK pass. It proves deep Android interaction coverage for the critical Metis learner flow and closes the V9-004 mobile-E2E portion of the automation checkbox.

It does not prove airplane-mode/network-loss behavior, persistence across a process restart, localization at scale, embodied face behavior, V2–V8 game bridges, creator payouts, or release-binary signing/installability. The separate V9-004 mobile/offline/localization/embodiment/bridge/payout checkbox therefore remains open.