maestro icon indicating copy to clipboard operation
maestro copied to clipboard

inputText extremely slow on Android 16

Open basevik opened this issue 3 months ago • 8 comments

Is there an existing issue for this?

  • [x] I have searched the existing issues and didn't find mine.

Steps to reproduce

- inputText: 'Some text'

Actual results

One keystroke is entered every 10-20 seconds

Expected results

Input should be typed in a reasonable time, e.g. <1 second per keystroke.

About app

Expo 52, issue is only present on Android

About environment

macOS 15.6

Java 17

Logs

No response

Maestro version

1.40.3

How did you install Maestro?

Homebrew

Anything else?

No response

basevik avatar Sep 11 '25 21:09 basevik

Can you try in the current version of Maestro?

What device were you running on?

Fishbowler avatar Sep 12 '25 07:09 Fishbowler

Device: Android emulator Medium_Phone_API_36

I can't try on the current version right now -- we need to migrate our app to the latest version first due to breaking changes.

basevik avatar Sep 12 '25 20:09 basevik

Also -- I'm frequently seeing the inputText command fail entirely on Android with the error Android driver unreachable.

Works fine on iOS!

basevik avatar Sep 12 '25 20:09 basevik

For me, input is very fast on the iOS Simulator and slower on the Android Emulator; higher Android API levels improve the input speed somehow. So, I am using Pixel 9 Pro with API 36. maestro version is 2.0.3 and expo sdk 50 (deveopment build)

mogulist avatar Sep 16 '25 23:09 mogulist

Noticed this coincidentally but can confirm and reproduce: since upgrading my physical device to Android 16, but also apparently the whole time with some of my emulator(s) running on API 36.0, inputText is unbearably slow - on the order of one character every 10 seconds. I have a hunch it has to do with versioning then, since my physical device just a day prior was handling e2e tests perfectly. Separate emulator(s) with API 35 are slightly slow, but manageable and a "normal" speed I suppose. iOS demos do seem to type significantly faster in any case

EDIT: I feel like it's important to mention after taking some time to poke around out of curiosity, but things just seem downright slower in general after my physical device Android version update - and this logic would apply to emulators on API 36.0 in my case as well. I'd be hesitant to say it's limited strictly to inputText, although that's going to be one of the most obvious candidates for a noticeable regression since the performance multiplier over many characters in a string becomes insurmountable, as opposed to say 3s per each button press vs 2s (annoying but surmountable haha)

jake-lindvall-lt avatar Sep 19 '25 11:09 jake-lindvall-lt

I've updated the title to reflect the common theme - that this all appears to be on API 36. Technically it's not yet supported by the CLI. That being said, if someone wants to have a crack at opening a PR to fix this, it'd certainly grease the wheels to making a supported version. Failing that, we'll certainly use the information gathered here when the internal team come to adding support, hopefully later in 2025.

Fishbowler avatar Oct 12 '25 19:10 Fishbowler

I have the same issue, I'm using API 36 with Maestro 0.8.4. A simple input like this "[email protected]" takes more than 2 minutes. [Failed] login-02-email-validation (2m 21s)

etsraphael avatar Oct 14 '25 03:10 etsraphael