How can I configure the wait for emulator to boot timeout?
See original GitHub issueI’ve set the adbInitTimeout to be 12 minutes (12 * 60 * 1_000 in ms).
However I’m seeing the following exception after ~10 seconds when I attempt to run /.gradlew :lib:marathonDebugAndroidTest (with no emulators booted or booting).
com.malinskiy.marathon.exceptions.NoDevicesException: No devices found.
No devices found
The adbInit docs are a little short on what ADB init means, and it would be useful to mention if it relates at all to the amount of time to wait for emulators to boot there.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Time out after 300seconds waiting for emulator to come online ...
Go to Menu->Tools->Android and uncheck the option Enable ADB Integration Run the application. Now the emulator will be launched, but app will not...
Read more >Increasing timeout for slow booting device #14453 - GitHub
Create a new device and try to start it with appium. The device need to have never been runned ( or run with...
Read more >Wait for Android emulator - Integrations
Specify the number of seconds the Step should wait for the emulator to boot in the Waiting timeout (secs) input. Specify the location...
Read more >Fix for "Timed out after 300seconds waiting for emulator to ...
Explained a simple fix for "Timed out after 300seconds waiting for emulator to come online." error while connecting to emulator in Android ...
Read more >Desired Capabilities - Appium
UIAutomator1 ; androidDeviceReadyTimeout, Timeout in seconds used to wait for a device to become ready after booting, e.g., 30 ; androidInstallTimeout, Timeout in ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Fixed in #389
The boot wait is a bit different to NoDevices state. If there is at least one device booted then the test execution will proceed. If there are no devices after the initial 30s period (e.g. all devices are still booting) then marathon will throw the exception as I described above.