Migrate to using Firebase Installation ID (FID) instead of now deprecated Cloud Messaging Token

[tobias-kuendig]

Bug Report

See firebase/firebase-android-sdk#8087

Plugin(s)

• @capacitor/push-notifications

Capacitor Version

Installed Dependencies:

  @capacitor/ios: not installed
  @capacitor/cli: 8.4.2
  @capacitor/android: 8.4.2
  @capacitor/core: 8.4.2

Platform(s)

• Android

Current Behavior

MessagingService.java uses onNewToken to receive a FCM cloud messaging token.

This method (and the usage of tokens) has been deprecated: https://firebase.google.com/docs/reference/android/com/google/firebase/messaging/FirebaseMessagingService#onRegistered(java.lang.String)

Expected Behavior

The new onRegistered must be used to receive a Firebase Installation ID, which replaces tokens.

[OS-pedrogustavobilro]

Hey @tobias-kuendig we are aware of this deprecation. However currently the push-notifications plugin is using version 25.0.1 of the Firebase Messaging Android SDK, so you should not get a deprecation warning on your app yet (unless you have updated the variable in your app's variables.gradle).

We're not yet sure when we'll be going with this update to the plugin, as it seems the use of FID instead of push tokens is still in an early transitionary phase, and the SDK itself has very recently had bugfixes for FIDs.

[eric-horodyski]

Hi @tobias-kuendig, thanks for raising this!

As @OS-pedrogustavobilro mentioned, we've decided against migrating to FID for now. No migration deadline currently exists, and Firebase has stated that both approaches are fully co-supported.

We'll plan to revisit this during our yearly Android/iOS SDK updates in the back-half of 2027, unless Firebase announces an EOL date for Cloud Messaging Tokens outside of our typical timeframes.

That said, I'm going to close this Issue.

[ionitron-bot]

Thanks for the issue! This issue is being locked to prevent comments that are not relevant to the original issue. If this is still an issue with the latest version of the plugin, please create a new issue and ensure the template is fully filled out.