You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But it seems the waitForAndroidEmulator is finalized by stopAndroidEmulator already (see here)
Is there any way to prevent the automatic closing of the emulator or some way to run the emulator module independent, e.g. config and start from the root build.gradle file?
The text was updated successfully, but these errors were encountered:
Hey, thanks for reaching out. No, this is not currently a supported usecase but I suppose it would be possible. I'm not actively developing on the plugin but if you are interested in contributing, I'd be happy to help you implement it yourself and review your changes.
I want to use the Plugin for instrumentation tests in multiple gradle modules.
I'm not sure if I'm missing something, but I would need to add the plugin to each module.
When I invoke the
connectedAndroidTest
task it will generate and start an Emulator instance for each module.I also tried to run the Emulator manually, e.g.:
or
But it seems the
waitForAndroidEmulator
is finalized bystopAndroidEmulator
already (see here)Is there any way to prevent the automatic closing of the emulator or some way to run the emulator module independent, e.g. config and start from the root
build.gradle
file?The text was updated successfully, but these errors were encountered: