Heads Up, Quickblox Developers: Time to Migrate Your FCM Push Notifications!
This guide is for all Quickblox users who rely on Firebase Cloud Messaging (FCM) for push notifications in their apps. Firebase is retiring their legacy API on June 20, 2024. Don’t worry, this update won’t disrupt your notifications – but you’ll need to migrate to the new HTTP v1 API as soon as possible to keep them flowing. This guide will walk you through the process step-by-step, ensuring a smooth transition. Let’s get started!
Note: No changes are required on QuickBlox client side SDKs.
To generate a new service account key, you need to:
To navigate to the push notifications section:
Note: we will remove the Server key tab when it will be discontinued by FCM, you will by default only have the service account key section on the dashboard.
To upload your service account key:
Note: When setting up your environment, it’s important to distinguish between development and production modes. If you’ve uploaded a development certificate, it will only function for subscriptions created in the development environment, and likewise for production. This separation ensures seamless testing and deployment of push notifications across different environments.
After uploading your service account key, you should test if your push notifications are working properly or not.
Note: Before sending the push notification make sure you have the proper service account key setup in the settings page and you have at least 1 valid subscription to receive the push notification.
To test your push notifications:
Voila! You should now receive the push notification on your mobile device(s).