[TIMOB-13539] Android: intermittent Packaging succeeds, app freezes at splash screen
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | Medium |
Status | Closed |
Resolution | Cannot Reproduce |
Resolution Date | 2013-08-07T19:16:26.000+0000 |
Affected Version/s | Release 3.1.0 |
Fix Version/s | n/a |
Components | Android, Tooling |
Labels | androidbuild, qe-3.1.0, triage |
Reporter | Dustin Hyde |
Assignee | Chris Barber |
Created | 2013-04-12T17:55:28.000+0000 |
Updated | 2014-01-03T18:06:47.000+0000 |
Description
Android: Packaging succeeds, app freezes at splash screen.
This is a regression. Works in Titanium Studio 3.0.2 (no Android CLI).
Runtime error:
E/TiApplication(13093): (KrollRuntimeThread) [295,332] APP PROXY: ti.modules.titanium.app.AppModule@42218140
Titanium Studio 3.0.2 w/o CLI (app loads successfuly):
"/usr/bin/python" "/Users/dhyde/Library/Application Support/Titanium/mobilesdk/osx/3.0.2.GA/android/builder.py" "distribute" "TitaniumProject" "/Users/dhyde/Desktop/android/android-sdk" "/Users/dhyde/Desktop/TitaniumStudio/3.0.2-Stable/Workspace/TitaniumProject" "com.titaniumproject" "/Users/dhyde/Desktop/android/android-keystore/release-key.keystore" "*******" "release" "/Users/dhyde/Downloads" "2"
Titanium Studio 3.1.0 w/CLI (build succeeds, app fails to load):
"/usr/local/bin/titanium" "--no-colors" "--no-prompt" "build" "--platform" "android" "--sdk" "3.0.2.GA" "--log-level" "trace" "--target" "dist-playstore" "--android-sdk" "/Users/dhyde/Desktop/android/android-sdk" "--alias" "release" "--keystore" "/Users/dhyde/Desktop/android/android-keystore/release-key.keystore" "--password" "bnorhwe" "--output-dir" "/Users/dhyde/Downloads" "--api-level" "8"
Test Steps:
1. Open Titanium Studio 3.1.0.
2. Create Titanium Project.
3. Package > Android (Google APIs 2.2).
4. Run on Device (Android 4.1.1).
Test Result:
Packaging operation succeeds, app freezes on splash screen at launch. This works in Titanium Studio 3.0.2 using the old python build script.
Attachments
File | Date | Size |
---|---|---|
cli-build-log.txt | 2013-04-12T17:55:28.000+0000 | 32622 |
runtime-log.txt | 2013-04-12T17:55:28.000+0000 | 457825 |
TiProject.zip | 2013-04-12T23:10:59.000+0000 | 6066907 |
TitaniumProject.zip | 2013-04-12T21:57:04.000+0000 | 6054251 |
Attaching 'TitaniumProject.zip', rename to 'TitaniumProject.apk'. Install using adb install TitaniumProject.apk This was created in Titanium Studio 3.0.2. This project runs correctly on Android 4.1.1 Device.
Attaching 'TiProject'. This is a project affected by the bug. It could be related to the project name: TiProject
This same app runs sometimes, and only loads the splash screen and freezes other times. See log for failures.
I can't reproduce the failure reliably, but the attached app failed the first time it was run.
Worth noting alloy projects have this error no matter what.
I was able to reproduce this issue once with Alloy Project only. App froze at "Alloy"splash screen. Quit and relaunch the app could not reproduce the issue. App launched with "appcelerator" red splash screen. Titanium Studio, build: 3.1.0.201304101819 SDK, build: 3.1.0.v20130411190058 CLI 3.1.0-cr Device: Galaxy Nexus 4.1.1
I've seen this bug about 10/20 times today.
I have tested this on a Motorola Droid Razr Max HD running 4.1.2 and a Nexus 10 running 4.2 and I was unable to reproduce the problem.
I tried more than 10 times but could not reproduce this issue. Environment used - SDK Build - 3.1.0.v20130412191547 Titanium Studio build - 3.1.0.201304121929 Mac OS - 10.8.2 CLI - 3.1.0-cr alloy - 1.1.0-cr node-appc - 0.1.29-cr node - v0.8.22 npm - 1.2.14 Device - HTC Desire (v4.0.3)
It was speculated and verified in source code that this is caused by the debugger anomalously attaching to a packaged app.
It sounds like this is not a regression, but the ability to package a debugger-ready app. Downgrading priority, but we should prevent this possibility.
Nobody can seem to reliably reproduce this (including me and the reporter), so I'm marking this as cannot reproduce.
This eventually went away, it only affected alloy. It seemed when I changed networks, the apps started loading again, whether or not that has anything to do with the bug.