-
Notifications
You must be signed in to change notification settings - Fork 578
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NullPointerException on FirebaseInstallations.registerFidWithServer #1787
Comments
I found a few problems with this issue:
|
Hi @francescocervone this issue was addressed in #1714 but we haven't made a release including with the fix yet. I'll keep this issue updated when the fix is out in a release. |
Is this caused by clearing SharedPreferences?
After clearing SharedPreferences, this crash might happen. |
Same issue. Below dependencies used in my project.
and stacktrace:
|
Anything we can do to temporarily stop this crash from happening? |
@searchy2 That's highly likely. Do you or others who are reporting crash clear the shared prefs? @wugeo0824 We are rolling out a fix this week which should be released either by Friday or Monday next week. Updating to the latest version of FCM releasing this week should fix the issue. |
This crash did start popping up for me after I renamed a shared preference's key value. |
@ankitaj224 We are noticing this issue on a new app install. Looking forward to the library update with the fix. |
Is this issue fixed ? It's mentioned in the latest release note but the ticket is still open |
We have version 16.3.2, and we have this crash. So it's weird that it's mentioned as a fix in 16.3.2. Note that 16.3.2 is also the version mentioned in the description of this ticket. |
Looks like a typo in the release note. 16.3.2 was rollout awhile ago. I'm trying to update to 16.3.3 to see if it fix. |
@lucas34 You are right, that's a typo. Thanks for catching it, we will fix the release notes in a short while. firebase-installations:16.3.3 or firebase-messaging:20.2.4 contain the probable fix. |
Please let us know if anyone has tried out the fix. |
@ankitaj224 - I am confused..the current version of crashlytics is firebase-crashlytics:17.1.1. How do we use firebase-installations if we are using the crashlytics SDK? |
@menting311 Thanks for reaching out & sorry for the confusion. You have two options:
|
We updated to 16.3.3 and it solved the issue. Thanks ! |
@lucas34 Thank you so much for confirming. I will go ahead and close this issue. Please feel free to reach out if you continue to see this issue. |
@ankitaj224 - So is this fix in crashlytics 17.2.1? I was looking at the release notes on this and I am not seeing anything referring to this? https://firebase.google.com/support/release-notes/android#crashlytics_v17-2-1 |
@menting311 Yes, crashlytics 17.2.1 transitively get this fix as it depends on firebase-installations:16.3.3. https://firebase.google.com/support/release-notes/android#installations_v16-3-3 |
it's been two days that this crash happens in crashlytics:17.1.1 only for android 4 meanwhile versions that contains 17.1.1 its been live from about one week ago. |
@MahdiYusefi Its possible probably some disk write issue. I would recommend updating to crashlytics 17.2.1 and that should fix the issue. Thanks. |
Environment
3.6.3
firebase-analytics
,firebase-messaging
,firebase-config
,firebase-crashlytics
->firebase-installations
firebase-analytics:17.4.3
,firebase-messaging:20.2.1
,firebase-config:19.1.4
,firebase-crashlytics:17.1.0
->firebase-installations:16.3.2
Description
Crashlytics reported some crashes on some OnePlus 6 devices with Android 10 on 19/07/2020.
Stacktrace
The text was updated successfully, but these errors were encountered: