[FirebaseMessaging] fid Change on every app launch 11.8.0

[Harry-postnord]

Description

Since we update to 11.8.0, we are getting delegate call for FCM token two times. First call with old token and then new FCM token.

One thing I notice when enabling Firebase debug option is that

[FirebaseInstallations][I-FIS001001] Sending request: <NSMutableURLRequest: 0x3028d9bc0> { URL: https://firebaseinstallations.googleapis.com/v1/projects/postnord-prod/installations/ }, body:{"appId":"","fid":"flig2_M8Wk2On9N8ZDN7fY","authVersion":"FIS_v2","sdkVersion":"i:11.8.0"}, headers: { "Content-Type" = "application/json"; "X-Goog-Api-Key" = ""; "X-Ios-Bundle-Identifier" = "*******"; }.

****** is being used to hide details.

fid is changing every time but we have checked on 10.9.0, it doesnot.

Reproducing the issue

No response

Firebase SDK Version

11.8.0

Xcode Version

16

Installation Method

Swift Package Manager

Firebase Product(s)

Messaging

Targeted Platforms

iOS

[google-oss-bot]

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

[rizafran]

Thanks for reporting, @Harry-postnord. You mentioned that your fid is changing. May I know if you uninstall and reinstall your app? I'm unable to reproduce it when I tried re-launching my app. Also, note that there are some cases where FIDs could be deleted or rotated:

• Uninstallation or reinstallation of the app, for instance when an end user installs on a new device
• The end user clears the cache of the app or the device
• FID deletion is triggered in the backend due to app inactivity

See our docs for more details.

Regarding the didReceiveRegistrationToken being called twice which returned the old and new fcm token, this is working as intended. You may check this ticket for more info.

[google-oss-bot]

Hey @Harry-postnord. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

[google-oss-bot]

Since there haven't been any recent updates here, I am going to close this issue.

@Harry-postnord if you're still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this.