[TIMOB-1872] Android: Fix AVD naming scheme
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Low |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2013-09-06T22:23:27.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | 2013 Sprint 18 Core, 2013 Sprint 18, Release 3.2.0 |
| Components | Android, Tooling |
| Labels | android, androidbuild, ay-verified, cb-verified, defect |
| Reporter | Don Thorp |
| Assignee | Chris Barber |
| Created | 2011-04-15T03:04:26.000+0000 |
| Updated | 2013-11-11T19:52:11.000+0000 |
Description
The current script for naming AVDs is based on the download order of the emulators. For instance if you download API 4 and API 8 and run the API 8 emulator. Then later you download the Google API emulator 4. It will launch the API 8 emulator.
If possible, we should also try and detect that the problem exists in their environment and fix the AVDs name to the new solution based on the contents of the AVD configuration file.
Pull request: https://github.com/appcelerator/titanium_mobile/pull/4646
The CLI for Android has been completely restructured. As such, the AVD naming convention is no longer as it was. We have verified the new "create your own" methodology and the backwards-compatibilty regarding existing AVDs. Closing as such.