Crash Reports On Android Devices

Solar2D Android
#1

Hi 

I’m seeing 2 crash reports on Android devices when I enter Google Play developer console. These are the reports:

java.lang.NullPointerException
at com.ansca.corona.CoronaActivity.onKeyDown(CoronaActivity.java:1792)
at android.view.KeyEvent.dispatch(KeyEvent.java:2540)
at android.app.Activity.dispatchKeyEvent(Activity.java:2280)
at com.android.internal.policy.impl.PhoneWindow$DecorView.dispatchKeyEvent(PhoneWindow.java:1819)
at android.view.ViewRoot.deliverKeyEventPostIme(ViewRoot.java:2963)
at android.view.ViewRoot.handleFinishedEvent(ViewRoot.java:2936)
at android.view.ViewRoot.handleMessage(ViewRoot.java:2102)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:132)
at android.app.ActivityThread.main(ActivityThread.java:4123)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:491)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:844)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:602)
at dalvik.system.NativeStart.main(Native Method)

java.lang.NullPointerException

at com.ansca.corona.CoronaActivity.onTouchEvent(CoronaActivity.java:1446)
at android.app.Activity.dispatchTouchEvent(Activity.java:2318)
at com.android.internal.policy.impl.PhoneWindow$DecorView.dispatchTouchEvent(PhoneWindow.java:1854)
at android.view.View.dispatchPointerEvent(View.java:4708)
at android.view.ViewRoot.deliverPointerEvent(ViewRoot.java:2448)
at android.view.ViewRoot.handleMessage(ViewRoot.java:2109)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:132)
at android.app.ActivityThread.main(ActivityThread.java:4123)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:491)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:844)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:602)
at dalvik.system.NativeStart.main(Native Method)

I packaged the app with Corona version 2012.971 (2012.11.15) 

Any idea why this may have happened? And more importantly is it anything to worry about?

Thank-you for your time on this.

Tanya.

#2

These errors are caused by race conditions that can happen while the user is backing out of your app.  We’ve fixed these specific issues as of daily build #1009.  I recommend that you build with the newest release.

#3

Thanks Joshua, I’ll do that now. Can you please tell me if the issue only affects Android? I’m wondering if I should also re-build the iOS version of the app as well?

Regards.

Tanya.

#4

Looks like I need to back track to  Corona version 2012.971. The latest build makes my scroll objects unusable. Actually it makes any page that has a scroll object in it unusable! Until that is fixed I’ll put up with the Android crash messages. Will look forward to the day I can use the latest build with scrolls.

#5

@hypergurl, do you use widget for your scroll objects?  If you do, the problem might have something to do with the upgrade to widget v2.0.  See http://www.coronalabs.com/blog/2013/02/22/widget-2-0-is-here-bam/

As noted in the blog post, if you want to use widget v1.0 with the latest build, you can get it from here:

https://github.com/coronalabs/widget-v1

If you want to migrate to widget v2.0, you’d want to look at the migration guide here:

http://docs.coronalabs.com/daily/api/library/widget/migration.html

Naomi

#6

Thank you for those links Naomi. Yes it has got to do with the upgrade to widget v2.0 as its the scroll objects in widget 2 that is causing the problem. I’ll have a read through those links. Thanks again, it’s very much appreciated :slight_smile:

#7

Those Java exceptions only happen on Android.  So, you only need to rebuild for Android.

That said, Apple has threatened to reject apps that reference their UDID API within the next 1-2 months due to security reasons.  Build 971 referenced Apple’s UDID API, which we later removed by build #1076.  I recommend that you look into upgrading your iOS app with the newest Corona release build in the near future to avoid this.

#8

Already done to the latest build, thank you Joshua :) 

#9

These errors are caused by race conditions that can happen while the user is backing out of your app.  We’ve fixed these specific issues as of daily build #1009.  I recommend that you build with the newest release.

#10

Thanks Joshua, I’ll do that now. Can you please tell me if the issue only affects Android? I’m wondering if I should also re-build the iOS version of the app as well?

Regards.

Tanya.

#11

Looks like I need to back track to  Corona version 2012.971. The latest build makes my scroll objects unusable. Actually it makes any page that has a scroll object in it unusable! Until that is fixed I’ll put up with the Android crash messages. Will look forward to the day I can use the latest build with scrolls.

#12

@hypergurl, do you use widget for your scroll objects?  If you do, the problem might have something to do with the upgrade to widget v2.0.  See http://www.coronalabs.com/blog/2013/02/22/widget-2-0-is-here-bam/

As noted in the blog post, if you want to use widget v1.0 with the latest build, you can get it from here:

https://github.com/coronalabs/widget-v1

If you want to migrate to widget v2.0, you’d want to look at the migration guide here:

http://docs.coronalabs.com/daily/api/library/widget/migration.html

Naomi

#13

Thank you for those links Naomi. Yes it has got to do with the upgrade to widget v2.0 as its the scroll objects in widget 2 that is causing the problem. I’ll have a read through those links. Thanks again, it’s very much appreciated :slight_smile:

#14

Those Java exceptions only happen on Android.  So, you only need to rebuild for Android.

That said, Apple has threatened to reject apps that reference their UDID API within the next 1-2 months due to security reasons.  Build 971 referenced Apple’s UDID API, which we later removed by build #1076.  I recommend that you look into upgrading your iOS app with the newest Corona release build in the near future to avoid this.

#15

Already done to the latest build, thank you Joshua :)