Mapp Engage: Mobile Push Migration to HTTP v1
    • 1 Minute to read
    • Dark
      Light

    Mapp Engage: Mobile Push Migration to HTTP v1

    • Dark
      Light

    Article summary

    16 May 2024 We're implementing Google's new authentication method for Android applications in our Channels Management process! In the coming weeks, you'll need to make some adjustments to continue sending Mobile Push messages to Android users.

    Key Benefits

    • Stay up to date with Google's latest requirements.

    • A shortened use time for tokens increases security. Read more about the new advantages from Google here.

    How does it work?

    When you set up new channels in Engage, you don't need to make any changes. However, you will need to reconfigure or deactivate any existing channels.

    Please note that you will need additional permissions to generate the JSON file. If an IAM (Identity and Access Management) user has the permission of "Firebase Cloud Messaging Admin", this gives them access to the Firebase messaging console and to the projects within the console. To generate the file, they will also need:

    • Firebase Admin (roles/firebase.admin)

    • Firebase Grow Admin (roles/firebase.growthAdmin)

    • Firebase Admin SDK Administrator Service Agent (roles/firebase.sdkAdminServiceAgent)

    • Firebase SDK Provisioning Service Agent (roles/firebase.sdkProvisioningServiceAgent)

    Please visit Google's documentation for more information about these permissions.

    First, you must update your Firebase authentication for your channels from the Firebase Cloud Messaging (FCM) key to FCM JSON Credentials. See our guides on Android Application Setup for Mapp Cloud for more information. Then:

    1. Create or Edit a Chanel:

      1. From a new channel, select Administration > Channels> Mobile Applications >Create App Channel. Then, on the “Info“ step, choose Android > Step 2: Configuration

      2. From an existing channel go to Administration > Channels > Mobile Applications and select your Android channel that’s in the DRAFT or INACTIVE status. Choose to Edit or View channel, then Step 2: Configuration.

    2. Configure your FCM Credentials.

    3. Save and Activate the channel.

    Proceed to create a mobile push notification with the newly configured channel.

    Availability

    This update will be rolled out over the next week. Please reach out to your Customer Success Manager if you have questions. We will be supporting the old FCM settings until June 20th, 2024. If you would like help updating your credentials, please contact your Customer Success Manager.

    Related Topics

    Migrate from legacy FCM APIs to HTTP v1

    Channel Creation (Window)

    Android Application Setup for Mapp Cloud


    Was this article helpful?