Firebase Cloud messaging service key not working correctly - firebase-cloud-messaging

Is the Firebase cloud messaging key present at the following two places same?
1) Firebase Console -> Settings -> cloud messaging
2) google-services.json under api_key-> current_key
My project has different keys at both the places. I am unable to send any messages to my server post migration to FCM

The API-KEY for sending FCM messages is the key present in:
Firebase Console -> Settings -> cloud messaging
The apy_key written in google_services.json is not used for FCM.

Related

Where to find Firebase server key, I have enabled Cloud Messaging API V1 but i can't find it

I'm having trouble finding the server key, I have set up a new project in firebase console, in my project settings I have enabled Cloud Messaging API V1, but cant see the server key my Cloud Messaging is showing disabled, where can I find it? Thanks
you have to enable the Cloud Messaging API from the console.cloud.google.com by clicking on this link or in firebase console there are three dots and clicking on the "Manage API in Google Cloud Console"after enabling the API go back to firebase and refresh then you will get the FCM key for messaging

I can't get firebase cloud messaging legacy key

I can't find my Firebase Cloud Messaging legacy key. Here's the screenshot of Settings>Project settings>Cloud Messaging:

FCM get registration token via robot framework

I want to get generated registration token which generated by a client such as (Web JS, Android/IOS App...) via robot todo automation testing
I'm thinking to use mountebank to add JS SDK but not simple because related to grant notification permission issue (It's required to able to generate registration token)
Anybody have an idea to get that token via robot please share
Thanks in advance!!!
What is FCM?
Firebase Cloud Messaging (FCM) is a cross-platform messaging solution that lets you reliably send messages at no cost.
Using FCM, you can notify a client app that new email or other data is available to sync. You can send notification messages to drive user re-engagement and retention. For use cases such as instant messaging, a message can transfer a payload of up to 4KB to a client app.
Using deprecated Google Cloud Messaging APIs? Learn more about how to migrate to FCM.
https://firebase.google.com/docs/cloud-messaging

Sending Push Notification To All People Who Have Enabled Notifications For My Progressive Web App

I am in the process of developing a new site and have decided to add progressive web app capabilities to the site. I have set it all up correctly and I can send push notifications to devices with whom I know the endpoint via FCM with a cURL command.
My question is how do you send one to all users who have enabled notifications on my site without knowing a list of all users unique endpoints.
If you are using the Firebase Cloud Messaging Web SDK you should be able to get the Firebase token and subscribe that token a topic using the server side API and then you can message the topic.
NOTE: This requires the use of the Firebase Web SDK to work. This is not supported with the raw Web Push API.

Unable to create plateform for gcm on AWS

I have created plateform for ios app and it is created fine on aws server but when I have tried to create gcm plateform on sns section it is giving error. I have attached the image.
I got exactly same issue as yours. It seems google is migrating Firebase Cloud Messaging (FCM) to Google Cloud Messaging, and the API Key created via Credentials in API Manager of Google Cloud Platform is not working.
And here is how I get it to work.
Go to Firebase Console and import Google Cloud Project.
Go to Project settings on Firebase Console and you should see the Web API
Key of your project.
Go back to your Google Cloud Platform, and go to Credentials of API Manager, you should see there are two API keys have been generated. Browser key (auto created by Google Service) and Server key (auto created by Google Service)
The Server key (auto created by Google Service) is what you need to
use on the Amazon SNS.
Hope it can resolve your problem, and hope it is only a temporary solution that after Google done the migration, we can directly use the API key created in API Manager.
You should check if you are using the correct server key. It should be something like AIzaSyZ-1u...0GBYzPu7Udno5aA.