-
Notifications
You must be signed in to change notification settings - Fork 260
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
[Maestro version, e.g. v1.30.4] - Exception in thread while running ui test #1304
Comments
Experiencing this as well
|
@kojofosu If you will try Android 12 it is working fine. |
@02gaurav Thank you so much ..i did not get that error after trying with android 12 ....but hopefully we get to know why it failed with android 10 in the future..thanks for your response |
I'm experiencing this same issue on Maestro version 1.31.0 when running most Android 10 devices:
The second exception above occurs when I Ctrl+C after the first exception stops the flows from continuing. Environment information: Edit: |
Still occurring on 1.32.0 |
Describe the bug
Exception while clicking on some button, its asserting visibility correctly. Also, navigation is fine on tapping button. But after tapping on the button got this exception and remaining test cases got stuck.
Exception in thread "pool-4-thread-1" java.io.IOException: Command failed (tcp:7001): closed
at dadb.adbserver.AdbServer.send$dadb(AdbServer.kt:99)
at dadb.adbserver.AdbServerDadb.open(AdbServer.kt:138)
at dadb.forwarding.TcpForwarder.handleForwarding$lambda-1(TcpForwarder.kt:64)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630)
at java.base/java.lang.Thread.run(Thread.java:831)
Expected behavior
There should not be any exceptions and test cases should not stuck.
Environment information (please complete the following information):
The text was updated successfully, but these errors were encountered: