Google Firebase Cloud Messaging (FCM) for Android requires a new protocol for sending push notifications to Android mobile devices. To support this new Google security standard, Pega includes support in the most recent Pega Platform™ releases and provides the required hotfixes for supported Pega Platform™ versions.
Google will no longer support the Legacy API for Push Notifications on June 21, 2024.
Affected versions
All currently supported Pega Platform releases.
These versions support push notifications to Android mobile devices:
- Pega Platform™ '24.1
- Pega Platform™ '23.1.2
- Pega Platform™ 8.8.5
For estimated release dates, see the Pega Infinity Patch Calendar.
Hotfixes are available for the following versions:
- Pega Platform™ '23.1.1 - HFIX-B457
- Pega Platform™ 8.8.4 - HFIX-B456
- Pega Platform™ 8.8.3 - HFIX-B1525
- Pega Platform™ 8.7.6 - HFIX-B455
- Pega Platform™ 8.6.6 - HFIX-B333
To download available hotfix packages, create a support request with Pega Global Client Support using the My Support Portal.
Impact
Before June 21, 2024, all customers sending push notifications to Android mobile devices must update Pega Platform on the server side. No changes are needed for Pega Mobile Client™ apps.
Do the following:
- Apply the latest Pega Platform hotfix or patch release.
- Add a new Firebase service account private key file to your Android mobile certificate set, as described in “Suggested Approach.”
Suggested approach
After applying the latest Pega Platform hotfix or patch release, update your Android certificate set:
- Go to https://firebase.google.com, sign into your Firebase account, and then access the Firebase console.
- In the Firebase console, generate a private key file for your service account:
- In the Firebase console, open Settings > Service Accounts.
- Click Generate New Private Key and then click Generate Key.
- Securely store the downloaded JSON file that contains the private key.
- In App Studio, upload the private key JSON file to the certificate set for your Android app:
- In the navigation pane of App Studio, click Settings > Mobile certificates.
- Click the Android certificate set that you want to use in your Android app.
- In the Firebase service account field, click New and then upload the private key file for your service account.
Pega Platform does not store the Firebase private key in a readable format. After the file is uploaded, a mobile app developer cannot see the content.
- Click OK, and then save the certificate set.
- Test the updated certificate set by verifying that your app receives automatic and manual push notifications.
Related content
Pega Mobile Client support announcements
Pega Customer Decision Hub updates required for push notifications to Android mobile devices