Maestro stopped asking which device to use when many are running, defaults to Android device

[DavidREntwistle]

Is there an existing issue for this?

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

Steps to reproduce

1. Open multiple devices e.g. x1 iOS simulator & x1 Android Emulator.
2. Run the maestro test yourFlow.yaml command.
3. Observe no Multiple running devices detected. Choose a device to run on. prompt.

Actual results

When I have multiple devices running, I cannot select which device to run the flow on with the maestro test command anymore.

If I have both an iOS simulator and android emulator running and I want to run X flow on the android emulator, I need to close the iOS simulator first, vice versa.

Expected results

When I have multiple devices running, I should be prompted with:

Multiple running devices detected. Choose a device to run on.
Enter a number from the list above:

The maestro studio command still allows this functionality.
I do not require any devices to be closed to run X flow on the correct device.

About app

• Native iOS & Android app

About environment

• MacBook Pro M2 Max - 32 GB
• macOS Sonoma 14.6
• arm64

Logs

N/a

Maestro version

1.37.0 - 1.39.0

How did you install Maestro?

install script (https://get.maestro.mobile.dev)

Anything else?

Re-raised of this issue here as this hasn't been resolved by this fix in CLI 1.39.0.

1.36.0 did not have this issue.
Occurred since 1.37.0 release.

[linear]

MA-2342 Maestro stopped asking which device to use when many are running, defaults to Android device

[tylerqr]

Please fix this. I've been stuck on version 1.36.0 because of this issue.

[Fishbowler]

Does this only affect situations with mixed iOS and Android environments?

Can you work around this with maestro -p android test someFlow.yaml and/or maestro --device=emulator-5554 test someFlow.yaml?

[DavidREntwistle]

@Fishbowler the option to select device doesn't display at all. No matter if there is a mix or no mix of iOS and Android environments.

[tylerqr]

Does this only affect situations with mixed iOS and Android environments?

Can you work around this with maestro -p android test someFlow.yaml and/or maestro --device=emulator-5554 test someFlow.yaml?

Yes, this works, but is untenable. The command that finally targets ios for me is something like maestro --device "59549BA3-469F-4FBF-BAB8-5A0DE37624D9" test tests/createMilk.yaml

The reason this is awful is we have to copy/paste this command each time we need to run/rerun tests or are writing new tests. It's completely untenable since our clipboards are already full of other content like commands from maestro studio, etc. It makes the whole thing unusable. Does that make sense?

The other option is to do android tests first and then ios tests after. Again, that would double the testing time and break my tests anyways since the ios account has tests that interact with the account driving the android tests because I have both platforms run tests simultaneously (it's a marketplace app with sophisticated tests that search for each other's items and buy from each other's accounts between ios and android, etc).

Please please, is there a way to bring back the way it prompted you in the CLI to select from running devices/simulators before executing the tests? Make this configurable maybe if it conflicts with whatever reason was used to remove it from 0.36 ?

[tylerqr]

I raised a PR that fixes this, at least for my use case #2401