Getting new FCM Token on every new app launch ( iOS - After SWIPE AWAY the app)

[TommyLeong]

Hello all,

Understand that, by default there's a auto registration for iOS for remote message. Hence, for us to get the FCM token and pass back to our backend server, we'll just call await messaging().getToken() ?

If that's how it work, im guess im doing right so far. But I'm getting a new FCM Token on every app launch which is kinda weird right?

Suppose I'm expecting a FCM token should only get renew after deleting and reinstalling the app. Please help to correct me if I'm wrong. 🙏

Thank you

[TommyLeong]

Then I realize the method didReceiveRegistrationToken was called on app launch. I put a breakpoint here to debug..

So the method was entered twice.

• On the first round, when I try to print out the fcmToken, it returns me the "existing FCM token".
• On the second time, when I try to print out the fcmToken, it returns me a new FCM token

😞

[TommyLeong]

I'm uncertain whether this is an issue from RNFirebase, so I decided to discuss here before creating a ticket. You're right, I'm suppose to provide the versioning i'm using.

    "@react-native-firebase/analytics": "^7.3.1",
    "@react-native-firebase/app": "^8.3.0",
    "@react-native-firebase/crashlytics": "^8.1.2",
    "@react-native-firebase/messaging": "^7.8.4",

I look through my code, I can't find any method that's performing any invalidation anywhere. When you say invalidate, i assume you are saying messaging().deleteToken().

Back to what you mentioned about #4299 (comment)
You mean to say I should include the following in my podfile? 🤔🤔🤔

 # Set up Firebase SDK version
  $FirebaseSDKVersion = '6.34.0'
  pod 'FirebaseFirestore', :git => 'https://github.com/invertase/firestore-ios-sdk-frameworks.git', :tag => $FirebaseSDKVersion
  pod 'FirebaseInstanceID', :git => 'https://github.com/invertase/firebase-ios-sdk.git', :branch => 'release-6.34.0-patched'

[mikehardy]

the FirebaseFirestore reference is optional - it's an optimization of build times for Firestore users. the FirebaseInstanceID line though, definitely - that's the trick

[mikehardy]

and your versions are out of date

[TommyLeong]

Adding both them in don't solve the issue for me. Perhaps this is a different issue to what you are linking mine too. Yes, i did follow this cd ios && rm -f Podfile.lock && pod install --repo-update.
As soon as I kill the app, and relaunching it. I'm getting a new FCM Token again.

[TommyLeong]

I'm still uncertain on the root cause on what causing it to refresh my app a new FCM Token. However from what I troubleshoot, com.firebase.iid.notif.refresh-token was the key that trigger this refresh. It seems to trigger the observer that was appended earlier added by method setupNotificationListeners

[TommyLeong]

Solved.
To wrap up this issue...

Earlier, the issue for this "new FCM Token" on every app launch (after SWIPE AWAY the app). It seems to be a conflict between RNFirebase SDK with another 3rd party SDK of mine in project.

The 3rd party SDK did certain action on

• Firebase App Configuration
• passing APNS token to Firebase
• etcs (which I'm not aware of, since it's a framework..I'm unable to read the code inside)

They then removed the "Firebase part" within their SDK, turns out.. the FCM token behave as it is. No longer changing on every app launch.

Thanks Mike for joining the discussion! Appreciate 👍

[mikehardy]

Glad to hear this is resolved, and now matches my work project - I have stable tokens