Menu
I am developing a demo app using Firebase Cloud Messaging. However, I am facing issues with the Firebase server key. Today morning I noticed that my server key got replaced with the FCM tokens.
Screenshot :
I was having two different FCM projects in two Gmail accounts having same package name for the Android app. I thought this may be causing issue and I have deleted both the projects and changed the package name, but still no luck.
I am unable to receive the push to my device. I have researched about the issue but didn't find any solution.
270
In the Firebase console, open Settings > Service Accounts. Click Generate New Private Key, then confirm by clicking Generate Key. Securely store the JSON file containing the key.
On initial startup of your app, the FCM SDK generates a registration token for the client app instance. This is the token that you must include in targeted send requests from the API, or add to topic subscriptions for targeting topics.
FCM token for an app may change due to various reasons that are specified in the Firebase documentation.
It doesn't expire though. It renews itself if one of the following happens. According to https://firebase.google.com/docs/cloud-messaging/android/client: -The app deletes Instance ID.
I checked the Firebase release notes, but can't find any roll out regarding this change. However, looks like the server key will be deprecated soon and will be replaced by the FCM token.
If you're having issues using the server key, then consider using the FCM token now.
Basically, you'll just need to change the value of the authorization key in the request header when sending messages to client apps.
Content-Type:application/json
Authorization:key=XXXXXXXXX:APA91bHVdTcAQGdFc5bIyK_WExwd5U6uJ....
Looks like that they re-use the server key term instead of FCM token, just upgraded to the newer version, as the following screenshot:
36
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
