quickstart-android: NullPointerException in FirebaseMessagingService
I got this crash today. First day in production. The crash report is from Crashalytics.
Fatal Exception: java.lang.NullPointerException
at com.google.firebase.messaging.FirebaseMessagingService.zzT(Unknown Source)
at com.google.firebase.messaging.FirebaseMessagingService.zzn(Unknown Source)
at com.google.firebase.messaging.FirebaseMessagingService.zzm(Unknown Source)
at com.google.firebase.iid.zzb$2.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1076)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:569)
at java.lang.Thread.run(Thread.java:856)
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Reactions: 6
- Comments: 58 (17 by maintainers)
Another similar crash:
Device: Batmobile XT320 Android v4.3.1 Rooted Firebase 9.4.0
I also got this crash report from Crashlytics:
Fatal Exception: java.lang.NullPointerException at com.google.firebase.messaging.FirebaseMessagingService.zzT(Unknown Source) at com.google.firebase.messaging.FirebaseMessagingService.zzn(Unknown Source) at com.google.firebase.messaging.FirebaseMessagingService.zzm(Unknown Source) at com.google.firebase.iid.zzb$2.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1076) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:569) at java.lang.Thread.run(Thread.java:856)
Device: GI-I9500_TMMARS OS: 4.1.1 ROOTED: Yes
I’m not checking for Google Play Services.
@pedrofsn @triveous as mentioned in previous comments we believe that the
TMMARS
andBatmobile
devices are not real users but some sort of automated testing device/emulator bank and therefore they do not behave correctly. The current suggestion is to ignore those users.Crashing on firebase
9.4.0
Fabric reported device : GI-I9500_TMMARS 4.1.1Noticing the same issue on a rooted Batmobile XT320 (Firebase 10.0.1), happy to help with logs.
Here is the stacktrace that we have: http://crashes.to/s/3c3ee631725
We also have the same devices. ie.
GI-I9500_TMMARS
andBatmobile
. I’m not sure but I am suspecting that these devices can be the ones in Firebase Test Lab that are used for Noto tests when we upload APKs to Play Store.org.gdg.frisbee.android_issue_305_crash_57f77893024d00010898d55c04266948.txt
Having the exact same issue on 9.4.0 a few hours after going to production
@sibelius @andytriboletti ok I have an update here. The SDK team knows about this issue and has a fix in place (it’s a simple null check, of course). I can’t guarantee exactly when this fix will be integrated into the publicly released SDK, unfortunately.
As that’s all we can do here I am going to close this issue. Thank you everyone for your feedback and help identifying this.
@samtstern no we haven’t experienced this bug on any of our test devices. We saw it from the Crashlytics log
same her: crashing with Firebase 9.4.0. 1 day in production. For me it seems strange that everbody has the exactly the same device in their crashreport: GI-I9500_TMMARS 4.1.1 and rooted. I am quiet sure that no one tried my app with a rooted phone because it did not promote the app in any way…