fix(maestro): type inputText with a 75 ms per-character delay on Android

Merged
AI
1d ago
+95-6

Summary

Maestro inputText on Android now types with Maestro 2.5.1's 75 ms per-character delay (MaestroDriverService.kt), so debounced inputs see a change per keystroke instead of one batched commit. iOS is unchanged. The default lives in the Maestro compatibility policy next to the other 2.5.1 defaults and reaches the port through MAESTRO_RUNTIME_ADAPTER_POLICY. No new CLI flag or flow grammar. 7 files touched, no scope expansion.

Fixes #2159

Validation

  • Tested SHA: 327c9e2 (pnpm check:affected --run on an identical working tree, not --head, so the receipt is not commit-exact): format, lint, typecheck, layering, fallow, build and vitest-related all pass.
  • New tests: a projection case, and port-level tests that Android inputText sends delayMs: 75, iOS inputText sends none, and eraseText sends none on either platform. The Android assertions failed before each change.
  • Updated two Android provider-scenario assertions that encoded delayMs: 0; they show 75 reaching the provider seam.
  • Live (device evidence from 4331a7f, before the eraseText fix in 327c9e2, which doesn't touch the inputText path): replay --maestro inputText of 100 chars into Settings search took 12,023 ms on API 36 and 15,602 ms on API 32; released 0.20.3 took 375 ms and 299 ms. Recordings are in the comments.
  • Not run: the debounced Catalog search field in the Expo test app, API 34, and the Appium/Limrun backends.