22
Views
1
Comments
Migrate from legacy FCM APIs to HTTP v1-Firebase mobile plugin
Application Type
Mobile

Hi 

From google announcement firebase  will deprecated in June 20th 2024 and have to Migrate from legacy FCM APIs to HTTP v1.

In Firebase mobile plugin FCM server key only we are using as by changing the FCM APIs to http V1

Access token needs to add instead of server key.

How could I change  the access token in firebase mobile plugin ?

Is that it works  like access token value  in FCM server key parameter in firebase mobile.




Thanks in Advance 

Soundarya

2025-09-25 14-38-22
Lokesh Kumar Yadav

Hi,

You're right—Firebase is deprecating the legacy FCM API and requiring a move to HTTP v1 using access tokens. The current Firebase Mobile Plugin uses the FCM server key, which won't work with HTTP v1 since it now requires an OAuth 2.0 access token instead.

To support this change, the plugin would need to be updated to generate and include the access token using a service account and scope-based authentication (like https://www.googleapis.com/auth/firebase.messaging).

So no, we can’t just replace the FCM Server Key with an access token in the same parameter. A structural update to the plugin is needed. If you’re planning a workaround or update, happy to support with the service account setup or HTTP v1 structure!

Let me know if you'd like a quick example.

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.