[TIMOB-10534] Tooling: Android emulator silently fails
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | High |
Status | Closed |
Resolution | Fixed |
Resolution Date | 2012-10-05T05:57:19.000+0000 |
Affected Version/s | Release 2.1.1 |
Fix Version/s | Release 3.0.0, Sprint 2012-20 Core, 2012 Sprint 20 |
Components | Android |
Labels | core |
Reporter | Clayton Headley |
Assignee | Bill Dawson |
Created | 2012-08-15T08:22:45.000+0000 |
Updated | 2012-12-18T23:32:20.000+0000 |
Description
When I try to run the android emulator I see the following in the Debug output:
{noformat}
[DEBUG] C:\SDK\tools\emulator.exe -avd titanium_6_WVGA854 -port 5560 -sdcard "C:\Users\qatester\.titanium\titanium_6_WVGA854.sdcard" -logcat *:d,*,TiAPI:V -no-boot-anim -partition-size 128 armeabi-v7a
[DEBUG] signal caught: 3
[DEBUG] calling emulator kill on 3872
{noformat}
A bit of poking around finds that the emulator does not launch when the armeabi-v7a argument is attached.
{noformat}
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\qatester>C:\SDK\tools\emulator.exe -avd titanium_6_WVGA854 -port 5560 -
sdcard "C:\Users\qatester\.titanium\titanium_6_WVGA854.sdcard" -logcat *:d,*,TiA
PI:V -no-boot-anim -partition-size 128 armeabi-v7a
C:\Users\qatester>invalid command-line parameter: armeabi-v7a.
Hint: use '@foo' to launch a virtual device named 'foo'.
please use -help for more information
{noformat}
I think this has something to do with the x86 emulators I had tested against, but can not figure out how to undo that change.
Steps to reproduce:
1. Create an Android project.
2. Run the project in the emulator.
Expected results:
The app should run in the emulator or should throw a relevant error.
Actual results:
The debug shows the above message before flipping the view to waiting for the emulator to be ready which finally times out.
I don't see the extra flag when testing on Titanium Studio, build: 2.1.2.201208131642. {nocode}[DEBUG] C:\SDK\tools\emulator.exe -avd titanium_6_WVGA854 -port 5560 -sdcard "C:\Users\qatester\.titanium\titanium_6_WVGA854.sdcard" -logcat *:d,*,TiAPI:V -no-boot-anim -partition-size 128 [DEBUG] signal caught: 3 [DEBUG] calling emulator kill on 5544 ERROR: The process "5544" not found. {nocode} The emulator continues to loads correctly.
Moving issue from Studio to SDK. Bug occurs from command line. Titanium Studio: 2.2.0 Titanium SDK: 2.1.1 OS: Windows 7 Devices Tested: Android Emulator 2.2, 2.3.3
Fail case / Test case
*MUST BE DONE IN WINDOWS!* *MUST BE DONE WITH TITANIUM STUDIO NIGHTLY (e.g., 3.0.0)!*Get Required Android Version
* Using Android's SDK Manager, download Android 4.0.3 (API 15): "SDK Platform", "ARM EABI v7a System Image" *and* "Intel x86 Atom System Image".Setup Titanium Studio
*Remember*: This must be a nightly build of Studio: http://preview.appcelerator.com/appcelerator/studio/standalone/install/nightly/Titanium_Studio.exe or (if you want to get it via updates of your currently installed Studio): add http://preview.appcelerator.com/appcelerator/studio/standalone/install/nightly/ to "Available Software Sites" in Studio preferences. * On the Titanium preferences pane, set "Android 4.0.3 [armeabi-v7a]" as the default android sdk.Make and run a project
* Create a Titanium Project. Use any template you want. Target 3.0.0. (Note: if you have a problem creating the project -- there is a bug in the current nightly as I write this -- then create a 2.1.2.GA project, then after it's created change the target sdk to 3.0.0.) Note that you need to target 3.0.0 to see the bug -- it's not in 2.1.2, but rather on current master. * Run the project on Emulator. Fail case: The emulator itself will never open. And you'll eventually get some errors. On the PR branch, the emulator should open.Hopefully the above makes sense. The formatting (at least, what I'm seeing in Chrome on OSX) is horrendous in this updated JIRA. Note that you cannot do these tests until TISTUD-2333 is fixed.
PR ready: https://github.com/appcelerator/titanium_mobile/pull/3074 But do not process until TISTUD-2333 is fixed.
Testing can resume.
Verified fixed on Titanium Studio, build: 3.0.0.201212131639 using Titanium SDK 3.0.0GA. Closing ticket.