[
https://issues.apache.org/jira/browse/CB-9172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14649079#comment-14649079
]
ASF subversion and git services commented on CB-9172:
-----------------------------------------------------
Commit 64f89c5edab7526b2983fd46291db1085b7554b5 in cordova-android's branch
refs/heads/master from [~alsorokin]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-android.git;h=64f89c5 ]
CB-9172 Improved emulator deploy stability. This closes #188.
- Use UUID to distinguish between launched emulators
- Wait for android.process.acore instead of init.svc.bootanim on emulator boot
- Increased retry timeout when installing app to the emulator
- If there is already a started/starting emulator, wait for it's boot instead
of trying to deploy to it right away
> Android "cordova run" sometimes locks up the emulator
> -----------------------------------------------------
>
> Key: CB-9172
> URL: https://issues.apache.org/jira/browse/CB-9172
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
> Affects Versions: Master
> Environment: Android on OSX and Windows
> Reporter: Dmitry Blotsky
> Labels: adb, android, found-by-ci
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> ADB commands used in "cordova run" for Android don't always wait for proper
> success conditions on Android, sometimes calling operations at the wrong
> time. For example, sometimes installation happens too soon after emulator
> boot, and the emulator locks up.
> The implementation of "cordova run" for Android should be made more robust. A
> reference implementation can be found in the Jenkins Android code, here:
> https://github.com/jenkinsci/android-emulator-plugin/blob/master/src/main/java/hudson/plugins/android_emulator/InstallBuilder.java.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
