You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the existing issues and didn't find mine.
Steps to reproduce
Open multiple devices e.g. x1 iOS simulator & x1 Android Emulator.
Run the maestro test yourFlow.yaml command.
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.
Is there an existing issue for this?
Steps to reproduce
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:
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
About environment
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.
The text was updated successfully, but these errors were encountered: