Deleting the Instance ID token does not trigger onNewToken

[READ] Step 1: Are you in the right place?

Yes

[REQUIRED] Step 2: Describe your environment

• Android Studio version: 4.1.1
• Firebase Component: Messaging
• Component version: 21.0.1

[REQUIRED] Step 3: Describe the problem

Inconsistency between iOS and Android SDKs when a token is deleted. On iOS, there was an update to the SDK to make sure the listener refreshed, please see p/r https://github.com/firebase/firebase-ios-sdk/pull/5339. Unable to reproduce same behaviour on Android.

Steps to reproduce:

1. get Firebase Messaging Token FirebaseInstanceId.getInstance().getToken();
2. delete Firebase Messaging Token FirebaseInstanceId.getInstanceId().deleteInstanceId()
3. get Firebase Messaging Token FirebaseInstanceId.getInstance().getToken();

Token is updated, but FirebaseMessagingService onNewToken is not triggered, unlike on iOS.

[ciarand]

I’ve put together a fix for this (internal ref 365888536) and it should be rolling out in the next FCM release.

But, I’ve seen that FirebaseInstanceId is deprecated, and that either FirebaseMessaging.getToken() or FirebaseInstallations.getToken(boolean forceRefresh) should be used instead, taken from the docs:

Yes, in general the future is to go through either FirebaseInstallations (for IDs) or FirebaseMessaging (for FCM registration tokens). The FirebaseInstallations.getToken method returns an installations auth token, which is distinct from the FCM registration token. For sending an FCM message to an app instance, the FirebaseMessaging.getToken method is the right one to use.

[mikehardy]

@ciarand great! @helenaford note this is packaged in firebase-android-sdk 27.0.0 which is a breaking change for react-native-firebase and we haven’t ported yet 😅 https://github.com/invertase/react-native-firebase/issues/5150

I believe based on BoM comparision if you are not using the admob module that you can overrde the sdk and everything will be fine but it’s untested as of yet