Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-8416] Android: 3.X and 4.X Emulator: Intermittent launcher stopped deployment failure

GitHub Issuen/a
TypeBug
PriorityMedium
StatusClosed
ResolutionWon't Fix
Resolution Date2012-08-23T10:06:32.000+0000
Affected Version/sRelease 2.0.0
Fix Version/sn/a
ComponentsAndroid
Labelsqe-and031912, qe-and051412
ReporterDustin Hyde
AssigneeNeeraj Gupta
Created2012-03-29T11:06:57.000+0000
Updated2013-05-01T20:11:09.000+0000

Description

When deploying to Android emulator, launch fails with launcher stopped dialog box. Steps to Reproduce: 1. Run app on emulator. Expected Result: App should run. Actual Result: Intermittent launcher stopped failure.

Attachments

FileDateSize
3.0.png2012-03-29T11:40:27.000+000093086
launcher stopped.png2012-03-29T11:06:57.000+0000440630
log.txt2012-03-29T11:06:57.000+0000486398

Comments

  1. Dustin Hyde 2012-03-29

    Also occurs on Emulator 3.0. Screenshot attached.
  2. Dustin Hyde 2012-05-30

    Bug persists. Studio: 2.0.2.201205292259 SDK: 2.0.2.v20120530102130 Android Runtime: V8 Android Emulator: 3.0 OS: Snow Leopard, Lion, Ubuntu 12.04
  3. Bill Dawson 2012-08-23

    We have truly no control whatsoever as to whether or not the Emulator's Launcher app starts successfully. It has nothing to do with how we launch our apps. I have also seen this, particularly when running in VMs, low memory conditions, or when CPU is being considerably used up by another process. (I.e., under conditions where the Emulator is starting up really slowly.) So unless I see a logcat that indicates that the launcher failure has anything to do with a titanium app, I consider this a "won't fix."
  4. Bill Dawson 2012-08-23

    I believe this can also be caused by a corrupt emulator instance (AVD). The attached log.txt looks like everything under the sun went haywire.
  5. Dustin Hyde 2013-05-01

    Closing.

JSON Source