Update your apps to the latest Firebase Cloud Messaging APIs and SDKs
What
Google notified Firebase customers in December 2023 that legacy Firebase Cloud Messaging (FCM) APIs would be discontinued on June 20, 2024. That deadline has passed, so this page is mainly useful for confirming the required FileWave and Google-side configuration for Chromebook messaging.
We’re writing to remind you that starting June 20, 2024 the legacy Firebase Cloud Messaging (FCM) APIs will be discontinued.
What do you need to know?On June 20, 2024, we’re reducing the number of Firebase Cloud Messaging (FCM) legacy register APIs and legacy send APIs that provide similar functionality. This step will allow us to provide you with a more consistent experience and align with Google security standards to improve security, reliability and performance.
Because of these API decommissions, some already-deprecated SDKs and features will stop working after June 20, 2024.
Please consult the tables below to find which Firebase Cloud Messaging (FCM) APIs and corresponding services/SDKs/features will be discontinued and replaced with new alternatives.
When/Why
-
Official Release with 15.4:
-
FileWave 15.4 added support for Google's newer FCM APIs.
-
How
What to check
- Run FileWave 15.4 or later for Chromebook FCM support.
- Confirm the required Firebase APIs are enabled in Google Cloud.
- Use the linked Chromebook articles below when validating the setup.
Action Required:
-
Update to FileWave 15.4 or later if you manage Chromebooks with FileWave. Then follow Confirming Firebase APIs are enabled for Chromebooks (15.4+) to verify the Google-side API configuration.
If Chromebook push behavior is still failing after the FileWave upgrade and Firebase API check, contact FileWave Support with the affected Chromebook details and the API-verification results.