-
Notifications
You must be signed in to change notification settings - Fork 273
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
[BUG] - Exception in thread "pool-4-thread-1" java.io.IOException: Command failed (host:transport:emulator-5554): device offline #1289
Comments
Having same issue |
hello, I identified that it was the google api version, I downloaded version 31, it solved the problem, in versions 30 and 33 this problem is happening |
@athosoli hi! I see the same error in the 31 |
Seeing this in 33 too, but instead see tcp closed, instead of device offline. but just for running a single flow (with recording), in GH actions. Didn't have this for 16core ubuntu, but 4core is definitely a problem |
I see this in an emulator using google API version 31 :( |
This is happening on API 29 on CI as well |
Any updates on this? |
Any updates on this? How to solve this issue? This is still exist on API 30 |
I'm facing same issue (emulator is live and adb is reporting it live) but maestro fails with logs:
This is Google google_apis_playstore arm64-v8a, API level 32 image. Fresh boot. |
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. |
When running multiple tests at once with "maestro test ./android/.maestro/" command
using the Pixel 2 API 31 emulator, from android studio, this error is displayed during execution:
Exception in thread "pool-4-thread-1" java.io.IOException: Command failed (host:transport:emulator-5554): device offline
at dadb.adbserver.AdbServer.send$dadb(AdbServer.kt:99)
at dadb.adbserver.AdbServerDadb.open(AdbServer.kt:137)
at dadb.forwarding.TcpForwarder.handleForwarding$lambda-1(TcpForwarder.kt:64)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
at java.base/java.lang.Thread.run(Thread.java:1623)
The problem does not occur when I run a few features, uams 4 for example, but when there are more than 5 the error occurs on Android.
In tests with IOS, I can run all 50 test files without showing this error, see that this is only happening on android.
The text was updated successfully, but these errors were encountered: