[
https://issues.apache.org/jira/browse/CB-9489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15206925#comment-15206925
]
Richard B Knoll commented on CB-9489:
-------------------------------------
A related problem is that if the emulator fails to start (for whatever reason),
our script does not fail (hence the wait forever). I actually added a timeout
to the script to support cordova-medic because we were seeing that problem in
the CI, I just didn't surface it in the CLI. Should this command time out? We
can easily enable a default wait time or add a flag for it.
> "cordova run android", "Waiting for emulator..." waits forever...
> -----------------------------------------------------------------
>
> Key: CB-9489
> URL: https://issues.apache.org/jira/browse/CB-9489
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
> Affects Versions: 5.1.1
> Environment: Windows 10 Enterprise 64 bits, new empty project, Android
> Reporter: Diego Geffner
> Labels: triaged
>
> I try to run the project in android, and it waits forever, and it never ends
> waiting (the emulator is not appearing):
> >cordova run android
> Running command: cmd "/s /c
> "C:\Users\user\my_project\platforms\android\cordova\run.bat""
> ANDROID_HOME=C:\Users\user\AppData\Local\Android\sdk
> JAVA_HOME=C:\Program Files (x86)\java\jdk1.7.0_55
> WARNING : No target specified, deploying to emulator
> WARNING : no emulator specified, defaulting to
> AVD_GalaxyNexus_ToolsForApacheCordova
> Waiting for emulator...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
