-
Notifications
You must be signed in to change notification settings - Fork 21.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Firebase Cloud Messaging no longer has a server key implementation #93522
Comments
thanks for bringing this to our attention. I have assigned the issue to the content author to evaluate and update as appropriate |
Update: @Grace-MacJones-MSFT I don't know where to report this to the Notification Hubs team, but please forward this to the relevant team and post back a link to an issue or somewhere we can monitor progress on this feature as many will need to re-configure their Notification Hubs in the next year. https://firebase.google.com/support/faq#fcm-23-deprecation I believe this is the relevant change:
This is how the same change was described in the email notification:
|
Are there any news about this deadline @angularsen pointed out? Someone should start looking for a solution to this problem |
Any update on this? |
I think this may answer your question: https://learn.microsoft.com/en-us/azure/notification-hubs/notification-hubs-gcm-to-fcm#current-state |
So basically there is a time window from March 1 until June 30 to complete a rather significant migration, to change client devices to register with FCM instead of legacy, remove the legacy registrations to avoid duplicates and then update the server to use FCM API. That's not a whole lot of time for absolutely everyone to jump when they say so, but at least there is a heads up now to prepare some of the migration steps. |
Please see the updated GCM to FCM migration steps: https://learn.microsoft.com/en-us/azure/notification-hubs/notification-hubs-gcm-to-fcm. As we are moving to a new feedback system, please reopen this issue or contact Microsoft Support if you still want to provide feedback on the documentation. Thank you! #please-close |
The API Key section in this tutorial is no longer applicable to Firebase Cloud Messaging. Google has changed how their Cloud Messaging services is consumed, and it's no longer a single server API key. It's unclear where an API Key should be generated in Firebase in order to link to Notifications Hubs now.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: