FCM API Upgrade

Google is updating the underlying infrastructure for sending push notifications. The legacy infrastructure will be deprecated by Google on June 20, 2024. You can find more information about Google’s migration from legacy FCM APIs to the new HTTP v1 API here.

Q. Do I need to take any action?

If you send push notifications or in-app notifications from the Blueshift platform, then ‘yes’. You will need to add your Service Account JSON file to all your active Blueshift Push adapters in the App Hub before  June 20, 2024. This key ensures your app receives notifications from Blueshift. The section below outlines the steps you need to take.

Updating The Blueshift Push Adapter

Step 1 Get your Firebase private key

First, you will need to download the private key JSON from the Firebase console.

  1. Log in to your Firebase console and open your project.
  2. Click the gear icon next to Project overview and choose Project settings from the drop-down list.

  3. Navigate to the Service accounts tab, and then click Generate new private key to download the private key JSON file.

Step 2: Update the Blueshift Push adapter

Once you have generated the key, continue with the following steps to update the Blueshift Push adapter.

  1. Log in to your Blueshift account and navigate to the Blueshift Push app configuration screen. You will see a list of all the push adapters for your account.
  2. For every adapter that you want to continue using, click the Edit Adapter button.
  3. Under the Firebase/Google Cloud Messaging section, click the Choose file button in the Service account JSON File field.

    Screenshot 2024-04-10 at 2.12.50 PM (2).png

  4. Upload the file you downloaded in Step 1.
Was this article helpful?
0 out of 0 found this helpful



Please sign in to leave a comment.