-
Notifications
You must be signed in to change notification settings - Fork 299
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Device was requested, but it is not connected. #2142
Comments
+1 exact same issue. It was working fine until around the 13th of November. (Also does not work on the latest version 1.39.2) The only thing that changed in my setup was a Windows update on the 12th of November |
Same here |
Same here with version 1.39.4 |
There have been problems reported in Windows for versions after 1.36.0 - it'd be ace to see someone with an interest in seeing this working to see if they can diagnose why Windows is behaving differently to the other platforms |
I’m encountering an issue when trying to run Maestro tests with a connected Android emulator. The emulator is successfully launched, adb is running, and the emulator is visible as a connected device. However, when I attempt to run a test using Maestro, I get an error stating that the requested device is not connected.
mbarkbakkar@LPTBS-74:~/Android/Brick/Build.Apps.Tests/.maestro$ maestro --udid=emulator-5554 --host 192.168.1.27 test flow.yaml Device emulator-5554 was requested, but it is not connected.
Logs:
2024-11-15_132657.zip
The text was updated successfully, but these errors were encountered: