Fix Compatibility with FCM (Firebase Messaging) 22.0.0 #1340
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
One Line Summary
To fix FCM push token registration when using Firebase Cloud Messaging version 22.0.0 switched to using the newer
FirebaseMessaging.getToken
API instead ofFirebaseInstanceId.getToken
which has been completely removed in that version.Details
Fixes
The reported symptom of this is any fresh installs getting registered to OneSignal as not subscribed and without a push token. And seeing something like this in the logcat:
Tests
Manual
firebase-messaging:19.0.0
withminifyEnabled true
firebase-messaging:22.0.0
withminifyEnabled true
This change is