Announcing FCM HTTP v1 Support

Action may be required.

What is changing?

To be in line with Google's recent announcement regarding depreciation of the Firebase Cloud Messaging (FCM) APIs for HTTP and XMP, we are pleased to announce that we have successfully integrated support for FCM HTTP v1. As communicated earlier, the legacy APIs will be deprecated and discontinued by Google by the end of June 2024, and as result all apps using FCM shall migrate to the new FCM v1 API until this deadline.

We highly encourage you to enable Firebase Cloud Messaging API (V1) on your Firebase Project and to update your credentials on Futurae Admin Dashboard before the June 2024 deadline to guarantee uninterrupted push notification delivery.

Required Actions

SDK Apps

To continue receiving push notifications on your app that integrates the Futurae Android SDK, enable Firebase Cloud Messaging API (V1) on your Firebase Project and update your FCM credentials on Futurae Admin Dashboard as follows:

- Acces Futurae Admin Dashboard 

- Select the Futurae Service for which you want to update your FCM credentials

- Select Settings > Mobile SDK

- Click the “Edit” icon next to FCM Credentials

- Ensure the FCMv1 option is selected

- Enter your Project ID and Service Account details (available in your Firebase Project console under Project Settings > Cloud Messaging).

Apps developed by Futurae

Futurae team will handle the setup of new FCM v1 credentials for Android apps developed by us, so there are no required actions for Access Apps customers.

Customers will be contacted in a timely manner once FCM v1 credentials setup process is initiated for Access Apps developed by Futurae.

Does this change have any impact on my Futurae integration?

No changes are required on your Futurae API implementation.

There are no expected changes required on Android apps that integrate Futurae Android SDK, therefore it won't be necessary to release new versions of the app.

For any inquiries, do not hesitate to contact support@futurae.com.