maestro
maestro copied to clipboard
Android driver timeout
I work with a custom made device which has some fairly modest hardware specs which keeps timing out whenever I try to run a test.
java.util.concurrent.TimeoutException: Maestro Android driver did not start up in time
at maestro.drivers.AndroidDriver.awaitLaunch(AndroidDriver.kt:119)
at maestro.drivers.AndroidDriver.open(AndroidDriver.kt:83)
Changing the timeout fixed this issue for us. Is there any specific reason why SERVER_LAUNCH_TIMEOUT_MS is kept at 5s? Could we bump it up to 10s instead? Another option would be to accept the timeout as a command argument and fallback to the built-in one if not specified by the user.
I think this is a duplicate of this closed (but still ongoing) issue - https://github.com/mobile-dev-inc/maestro/issues/144
Also encountering this issue trying to get Android tests up and running on CI.
@carlosmuvi-stripe @simon-gilmurray @ebarrenechea we have tweaked the timeout to be 15 seconds which should give enough time to start the maestro server.
PR: https://github.com/mobile-dev-inc/maestro/pull/316
It should be available in the latest version: 1.11.4
Let me know if this works for you 🙌
Feel free to reopen if this is still an issue!
Thanks @amanjeetsingh150 unfortunately this still seems to be causing the same issue on our CI using a Genymotion emulator. I need to do some more investigating in to why as I can see from a screenshot that the emulator seems to be displaying a system popup that could potentially be interfering.
@amanjeetsingh150 version 1.11.4 works great with our custom device, thanks! 🙌
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!