Push notifications crash application

Solar2D Android
#1

Anyone else seen weird behaviour with google push notifications? It seems that clicking on push notification while the application is in the background crashes the app. I initially thought that I had some errors on my code but I tested this with the “GooglePushNotifications” sample application with the same results. So, everything works well until I exit the app with device back button. When a notification arrives and I click it after I have exited the app the application crashes instead of opening up. The same does not happen when using home button to exit the app.

I’m running build 2014.2224 and testing with SG4+ (i9506)

Logcat outputs the following exception:

04-01 22:59:38.988: E/AndroidRuntime(31313): FATAL EXCEPTION: main
04-01 22:59:38.988: E/AndroidRuntime(31313): java.lang.RuntimeException: Unable to start receiver com.ansca.corona.notifications.StatusBarBroadcastReceiver: java.lang.NullPointerException
04-01 22:59:38.988: E/AndroidRuntime(31313):     at android.app.ActivityThread.handleReceiver(ActivityThread.java:2554)
04-01 22:59:38.988: E/AndroidRuntime(31313):     at android.app.ActivityThread.access$1600(ActivityThread.java:168)
04-01 22:59:38.988: E/AndroidRuntime(31313):     at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1405)
04-01 22:59:38.988: E/AndroidRuntime(31313):     at android.os.Handler.dispatchMessage(Handler.java:99)
04-01 22:59:38.988: E/AndroidRuntime(31313):     at android.os.Looper.loop(Looper.java:176)
04-01 22:59:38.988: E/AndroidRuntime(31313):     at android.app.ActivityThread.main(ActivityThread.java:5493)
04-01 22:59:38.988: E/AndroidRuntime(31313):     at java.lang.reflect.Method.invokeNative(Native Method)
04-01 22:59:38.988: E/AndroidRuntime(31313):     at java.lang.reflect.Method.invoke(Method.java:525)
04-01 22:59:38.988: E/AndroidRuntime(31313):     at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1209)
04-01 22:59:38.988: E/AndroidRuntime(31313):     at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1025)
04-01 22:59:38.988: E/AndroidRuntime(31313):     at dalvik.system.NativeStart.main(Native Method)
04-01 22:59:38.988: E/AndroidRuntime(31313): Caused by: java.lang.NullPointerException
04-01 22:59:38.988: E/AndroidRuntime(31313):     at com.ansca.corona.notifications.StatusBarBroadcastReceiver.onReceive(StatusBarBroadcastReceiver.java:64)
04-01 22:59:38.988: E/AndroidRuntime(31313):     at android.app.ActivityThread.handleReceiver(ActivityThread.java:2538)
04-01 22:59:38.988: E/AndroidRuntime(31313):     … 10 more
 

#2

Can I get you to file a bug report, since it happens with the sample app.

Thanks

Rob

#3

Yep, it’s case 31726: Google push notifications crash application.

#4

Same issue here. I sent a build out with version 2014.2224 and i got a few reports the next morning saying that notifications are now crashing the app on Android devices. 

Sape, do you happen to know a recent safe build i can fall back to?  

Thanks,

Jamie

#5

Latest build that will not cause application to crash seems to be 2014.2210. I downgraded all the way to that version and all builds above that crashed. So I suppose it’s safe to use 2014.2210.

#6

Did you include that information in the bug report?  You can reply to the email and add if if you didn’t.

Rob

#7

I tested different build versions after creating the bug so initially the information was not in the bug report. Anyways, I now replied to the mail and added this information to the bug.

#8

Can I get you to file a bug report, since it happens with the sample app.

Thanks

Rob

#9

Yep, it’s case 31726: Google push notifications crash application.

#10

Same issue here. I sent a build out with version 2014.2224 and i got a few reports the next morning saying that notifications are now crashing the app on Android devices. 

Sape, do you happen to know a recent safe build i can fall back to?  

Thanks,

Jamie

#11

Latest build that will not cause application to crash seems to be 2014.2210. I downgraded all the way to that version and all builds above that crashed. So I suppose it’s safe to use 2014.2210.

#12

Did you include that information in the bug report?  You can reply to the email and add if if you didn’t.

Rob

#13

I tested different build versions after creating the bug so initially the information was not in the bug report. Anyways, I now replied to the mail and added this information to the bug.