-
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
[v1.34.0] Android driver unreachable whilst running flow #1570
Comments
@DavidREntwistle does this happen consistently or every now and then for you? What if you try different emulators / device models? |
@axelniklasson it seems inconsistent across devices whilst running locally. But it looks to be consistently occurring when running on CI.
This looks related to this issue I raised here: #1525 It appears that now in v1.34.0 after this issue occurs, the flows continue to run with the "Android driver unreachable" message as the reason (this I feel is better). I can't think of any reason why the device would go offline mid-execution. |
Got it -- thanks for that context @DavidREntwistle. I would recommend running a separate process on your CI box that checks whether the device you're working with is online or not during the execution to rule out any environment specific issues. If it turns out that the device is online and functioning it does point towards a maestro issue, so let us know if that is the case. Thanks! |
Thank you @axelniklasson I'll take a look at that from our side and feedback. |
@axelniklasson I'm also facing the same issue after upgrading to Maestro 1.34.1. I've checked that emulator is running and responsive, yet maestro throws a "device offline" error and then all tests start failing with "Android driver unreachable". I also checked maestro.log and found this:
|
I've experienced the Looking into the
Though the above "ERROR" was a Had a check within the commands json file for the flow when the error occurred, here is the below stack trace for the
Followed by another
|
i have the same issue when running it locally for one flow , but its happening time to time not always |
Experiencing this issue on Maestro v1.35.0 also.
|
I've been able to simulate this issue here and I have left steps to replicate: I'm wondering if this "Android driver unreachable whilst running flow" & the "Exception in thread "pool-4-thread-1"" issues I've raised could be related to something similar to this google issue raised. If the device reconnects following the initial error, after 4 minutes the tests re-continue. |
@axelniklasson Also hitting this issue on v1.35.0
|
Also encounter this issue on v1.35.0 |
Got the exact same issue running our flows |
We are also facing the same issue when running on a macbook as a Azure local agent, Did anyone solve this please advice, |
@adithyaam I found one cause to be our ci agent timing out because of the long execution time/the timeout set to an hour when the flows took longer than an hour. Another reason was caused by the actual android emulator crashing, it seems some API versions are more stable than others. |
The #1733 (not released yet) upgrades uiautomator to 2.3.0, so it should address this issue. Wondering if there's a way to test snapshot builds of Maestro... |
@dmitry-zaitsev Should a new version be released now that #1733 has been merged? |
I'm on 1.38.1 and facing this issue as well is there any confirmation if #1733 has already fixed this issue? |
Based off the merge commit, the 'fix' has been in there since 1.37.0. We've been experiencing this issue as well but on 1.36.0. Was interested in upgrading but if this issue still occurs for you on 1.38.1, doesn't bode well for us :'( |
@iqbalmineraltown can you check if when you're running into it, there's a |
@robin-pham there is. Any idea ?
|
as mentioned on #1573 (comment) |
Has this not been fixed yet? |
Sadly this is still an issue and I haven't found a workaround @pntgoswami18 |
I'm having the same problem. |
I have increased my android emulator memory to 4GB and this seems to help this issue, by default it was at 2GB. I'm thinking the emulator/maestro driver crashed due to low memory usage. 4GB (4096) + seems more stable / less android driver unreachable errors occur. Headless 4GB Emulator E.g. |
ty @DavidREntwistle, we bumped it to 8192 and it's been much more stable ever since! |
It works, too! Thanks 🙏 |
Describe the bug
Whilst running a flow that previously passed, the following error occurred:
UPDATE 27th November 2023:
See post here.
To Reproduce
Unable to reproduce at this moment.
Expected behavior
To not fail getting the view hierarchy.
Screenshots
Environment information
Maestro version [v1.34.0]
Platform: [Android 13.0]
Framework: [Native Android]
Device model and OS version: [Pixel]
Emulator device
Host [Apple MacBook Pro M2 Max]
Additional context
This was not an issue on v1.33.1 for Android.
iOS v1.33.1 & v1.34.0 is not an issue.
The text was updated successfully, but these errors were encountered: