We have enabled the registration of Firebase private keys as certificates in the Repro Dashboard.
This enables the utilization of the FCM HTTP v1 API for push notifications on Android.
Release Date
October 23, 2023
Background for the Update
Until now, Repro only supported the "Legacy HTTP Protocol" for delivering push notifications to Android devices.
However, the "Legacy HTTP Protocol" is scheduled for deprecation around June 2024, prompting the need to consider transitioning to the new communication method, "FCM HTTP v1 API."
Reference: Transitioning from Previous HTTP to HTTP v1
Customer action is required to transition in Repro's push notifications as well.
Following this release, registering Firebase private keys with Repro completes the transition to FCM HTTP v1.
Note: While using FCM Server Key for delivery, the deprecated Legacy HTTP Protocol will continue to be utilized.
Please refer to the "Actions Required from Customers" section below, register your Firebase private keys, and collaborate with us in transitioning to the FCM HTTP v1 API.
Customers Requiring Transition to FCM HTTP v1 API
All customers meeting both of the following conditions are subject to the transition:
- Utilizing ReproApp (ReproAndroidSDK)
- Utilizing push notification functionality for Android devices
Even if push notifications are successfully delivered via registering FCM Server Key from the push notification settings screen, action is still required.
Impact of Non-compliance with Transition
Failure to transition will result in Repro being unable to deliver push notifications to Android devices.
While Google has announced the deprecation of the Legacy HTTP Protocol around June 2024, we kindly request you to register Firebase private keys promptly to allow ample time for transition.
Additionally, the registration of FCM Server Key in the Repro Dashboard will no longer be possible around March 2024. New users of Repro are requested to register only Firebase private keys.
Changes in Delivery Logic Related to this Update
As part of the preparation for this update, certain changes have been made to the delivery logic of push notifications using custom payloads since October 11, 2023.
For details, please refer to past announcements.
Actions Required from Customers
Create Firebase private keys from Firebase Console and register them in the Repro Dashboard.
The transition can be completed in the following 3 steps, so please proceed according to the development documentation:
- Access the Firebase project page embedded in the app using Repro and Enabling Firebase Cloud Messaging API (V1)
- Generate Firebase private key
- Register Firebase private keys with Repro
FAQs
Q: How can I confirm if "FCM HTTP v1 API" is enabled in my Firebase project?
Navigate to [Project Settings] from the gear icon on the left sidebar of the Firebase project.
By clicking the [Cloud Messaging] tab, you can confirm if "Firebase Cloud Messaging API (V1)" is enabled.
If it's not enabled, secret keys cannot be uploaded to Repro. Please enable it from the Google Developer Console.
Q: Is SDK or app update necessary to use "FCM HTTP v1 API"?
No, updates are not necessary if the push notification-related implementation is complete.
Q: If FCM Server Key is already registered, is action required?
Yes, action is required.
Even if FCM Server Key is registered in the Repro Dashboard, registering Firebase private keys is necessary.
Q: Can FCM Server Key and private keys be registered simultaneously?
Yes, they can.
Upon registration of Firebase private keys in Repro, they will be prioritized over FCM Server Key for delivery.
Therefore, there is no need to delete the registered FCM Server Key.
Q: Until when can FCM Server Key be used?
Registration of FCM Server Key in the Repro Dashboard is scheduled until around March 2024.
After that, registration of Firebase secret keys will be necessary.
For inquiries regarding this update
Please contact our Customer Success team or inquire through the chat feature in the Dashboard.