Created
October 18, 2013 12:02
-
-
Save AppWerft/7040580 to your computer and use it in GitHub Desktop.
Crash log by using on 2.3.5 android
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
D/com.appcelerator.cloud.push.CCPushService(19090): GCM RegistrationId not found. Need to make request to generate. | |
W/dalvikvm(19090): Exception Ljava/lang/RuntimeException; thrown while initializing Landroid/os/AsyncTask; | |
W/dalvikvm(19090): threadid=12: thread exiting with uncaught exception (group=0x4001d5a0) | |
E/TiApplication(19090): (Thread-13) [168,177] Sending event: exception on thread: Thread-13 msg:java.lang.ExceptionInInitializerError; Titanium 3.1.3,2013/09/18 12:01,222f4d1 | |
E/TiApplication(19090): java.lang.ExceptionInInitializerError | |
E/TiApplication(19090): at com.appcelerator.cloud.push.CCPushService.registerGCMServiceBackground(CCPushService.java:482) | |
E/TiApplication(19090): at com.appcelerator.cloud.push.CCPushService.registerGCM(CCPushService.java:443) | |
E/TiApplication(19090): at ti.cloudpush.CloudpushModule$1.receivedGCMSenderId(CloudpushModule.java:613) | |
E/TiApplication(19090): at com.appcelerator.cloud.push.CCPushService$1.run(CCPushService.java:98) | |
E/TiApplication(19090): at java.lang.Thread.run(Thread.java:1027) | |
E/TiApplication(19090): Caused by: java.lang.RuntimeException: Can't create handler inside thread that has not called Looper.prepare() | |
E/TiApplication(19090): at android.os.Handler.<init>(Handler.java:121) | |
E/TiApplication(19090): at android.os.AsyncTask$InternalHandler.<init>(AsyncTask.java:421) | |
E/TiApplication(19090): at android.os.AsyncTask$InternalHandler.<init>(AsyncTask.java:421) | |
E/TiApplication(19090): at android.os.AsyncTask.<clinit>(AsyncTask.java:152) | |
E/TiApplication(19090): ... 5 more | |
E/AndroidRuntime(19090): FATAL EXCEPTION: Thread-13 | |
E/AndroidRuntime(19090): java.lang.ExceptionInInitializerError | |
E/AndroidRuntime(19090): at com.appcelerator.cloud.push.CCPushService.registerGCMServiceBackground(CCPushService.java:482) | |
E/AndroidRuntime(19090): at com.appcelerator.cloud.push.CCPushService.registerGCM(CCPushService.java:443) | |
E/AndroidRuntime(19090): at ti.cloudpush.CloudpushModule$1.receivedGCMSenderId(CloudpushModule.java:613) | |
E/AndroidRuntime(19090): at com.appcelerator.cloud.push.CCPushService$1.run(CCPushService.java:98) | |
E/AndroidRuntime(19090): at java.lang.Thread.run(Thread.java:1027) | |
E/AndroidRuntime(19090): Caused by: java.lang.RuntimeException: Can't create handler inside thread that has not called Looper.prepare() | |
E/AndroidRuntime(19090): at android.os.Handler.<init>(Handler.java:121) | |
E/AndroidRuntime(19090): at android.os.AsyncTask$InternalHandler.<init>(AsyncTask.java:421) | |
E/AndroidRuntime(19090): at android.os.AsyncTask$InternalHandler.<init>(AsyncTask.java:421) | |
E/AndroidRuntime(19090): at android.os.AsyncTask.<clinit>(AsyncTask.java:152) | |
E/AndroidRuntime(19090): ... 5 more | |
W/ActivityManager( 1371): Force finishing activity de.appwerft.nachtdeswissens/.NachtDesWissensActivity | |
D/WindowManagerImpl( 1371): addView, new view, mViews[2]: com.android.internal.policy.impl.PhoneWindow$DecorView@409e6660 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment