Closed fauzisunarya closed 2 weeks ago
This issue has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar problem, please file a new issue. Make sure to follow the template and provide all the information necessary to reproduce the issue. Thank you for helping keep us our issue tracker clean!
Is there an existing issue for this?
Steps to reproduce
.
Actual results
Hello, I found a bug when I wanted to run a test, it did not automatically connect to the emulator, even though I had run the emulator.
The syntax I ran was as follows:
maestro --host 192.168.1.7 test Regiser_PhoneAlreadyRegister.yaml
But if I run the syntax: maestro --host 192.168.1.7 record Regiser_PhoneAlreadyRegister.yaml
It automatically detects the emulator that is already active
Please tell me the solution
Expected results
Hello, I found a bug when I wanted to run a test, it did not automatically connect to the emulator, even though I had run the emulator.
The syntax I ran was as follows:
maestro --host 192.168.1.7 test Regiser_PhoneAlreadyRegister.yaml
But if I run the syntax: maestro --host 192.168.1.7 record Regiser_PhoneAlreadyRegister.yaml
It automatically detects the emulator that is already active
Please tell me the solution
About app
flutter
About environment
openjdk 21
Logs
Logs
``` ```Maestro version
latest
How did you install Maestro?
install script (https://get.maestro.mobile.dev)
Anything else?
No response