[TIMOB-2649] Android: Detecting Second Instance causes NPE.
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Medium |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2011-04-17T01:59:42.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | Release 1.6.0 M03 |
| Components | Android |
| Labels | android, defect, regression, release-1.5.2, release-1.6.0, reported-1.5.1 |
| Reporter | Don Thorp |
| Assignee | Don Thorp |
| Created | 2011-04-15T03:25:49.000+0000 |
| Updated | 2011-04-17T01:59:42.000+0000 |
Description
When launching the app from the install point, not the home launcher on device, an NPE is generated when trying to release modules because it assumes that the app is already set up.
See http://developer.appcelerator.com/question/92671/android---freezing-on-startup"> Q&A 92671
~~~
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:626)
12-20 12:46:09.205: ERROR/AndroidRuntime(13433): at
dalvik.system.NativeStart.main(Native Method)
12-20 12:46:09.205: ERROR/AndroidRuntime(13433): Caused by:
java.lang.NullPointerException
12-20 12:46:09.205: ERROR/AndroidRuntime(13433): at
org.appcelerator.titanium.TiRootActivity.onDestroy(TiRootActivity.java:420)
12-20 12:46:09.205: ERROR/AndroidRuntime(13433): at
android.app.ActivityThread.performDestroyActivity(ActivityThread.java:3861)
12-20 12:46:09.205: ERROR/AndroidRuntime(13433): ... 11 more
~~~
(from [86ad0ed0cb9ef1a58aca6ad657c3db2b56f53de1]) [#2649 state:fixed-in-qa] Added null checking. https://github.com/appcelerator/titanium_mobile/commit/86ad0ed0cb9ef1a58aca6ad657c3db2b56f53de1"> https://github.com/appcelerator/titanium_mobile/commit/86ad0ed0cb9e...
(from [9a159e763acfefd09606a665102e595b506795f4]) [#2649 state:fixed-in-qa] Added null checking. https://github.com/appcelerator/titanium_mobile/commit/9a159e763acfefd09606a665102e595b506795f4"> https://github.com/appcelerator/titanium_mobile/commit/9a159e763acf...
adding release-1.5.2 tag for tracking fix pushed to 1_5_X branch.
"an application restart is required" 2.2.1 (G2), 1.6 (G1) Titanium SDK version: 1.5.2 (01/05/11 08:30 981dff2) and Titanium SDK version: 1.6.0 (01/04/11 08:01 e49700d)
This is still occurring for me on today's (21/02/2011) current Continuous 1.6.0 builds.
If I install the App from the marketplace and click from the Point Of Install, (Marketplace or Notifications Bar), the App crashes on first run.
If I open it for first run from the Homescreen the App launches without error.
Tracelog pastie http://pastie.org/1589654t" title= "Here">Here
Question on Developer Q&A http://www.google.co.uk/search?sourceid=chrome&;ie=UTF-8&q=Appcelerator%2Bapp%2Bcrash%2BOTA" title="Here">Here
Correction:
Question on Developer Q&A http://developer.appcelerator.com/question/114801/android-force-close-on-first-run-after-submitted-to-market" title="Here">Here
Old Related Question (Now Closed) http://developer.appcelerator.com/question/92811/help-runs-fine-on-android-simulator---stops-at-the-splash-screen-on-device" title="Here">Here
Sorry I've made a mistake, after taking another look at the Stack Trace I realised that this is not the same issue, but a different issue which causes the same results. (Crash when launched from point of install).