Firebase
- Home
- Firebase
Your app is at Risk
Act right and remediate at the earliest
- 00Days
Legacy Firebase Cloud Messaging (FCM) APIs to Be Discontinued
How does the discontinuation of Legacy Firebase Cloud Messaging (FCM) APIs affect the functionality of the app?
Legacy Firebase Cloud Messaging (FCM) refers to the older version of the Firebase Cloud Messaging service provided by Google. It was used by developers to send push notifications, messages, and data to their Android, iOS, and web applications.
The discontinuation of Legacy Firebase Cloud Messaging (FCM) APIs means that Google will stop supporting and maintaining the older version of the FCM service. This discontinuation can affect the functionality of apps that rely on Legacy FCM APIs in several ways
- Compliance: With the discontinuation of Legacy FCM APIs, apps may no longer comply with Google’s policies and guidelines for app development and distribution. This could potentially lead to the removal of the app from the Google Play Store or other app stores.
- Compatibility: Apps using Legacy FCM APIs may not be compatible with newer operating system versions or Firebase SDK updates. This can lead to potential issues and malfunctions in the app’s notification system.
- Security: Unsupported software can pose security risks as it may not receive necessary updates or patches to address vulnerabilities. This could make the app more susceptible to security breaches or attacks.
- Feature Updates: New features and improvements introduced in the newer versions of Firebase Cloud Messaging will not be available to apps using Legacy FCM APIs. This could limit the app’s ability to leverage advanced functionality and optimize user engagement.
- Reliability: Unsupported APIs may become less reliable over time due to a lack of maintenance and updates. This could result in unreliable delivery of push notifications or messages to app users.
To mitigate the impact of the discontinuation of Legacy FCM APIs, developers are encouraged to migrate their apps to the latest version of Firebase Cloud Messaging and update their implementation accordingly. This involves updating the Firebase SDK, integrating the latest FCM APIs, and ensuring compatibility with the latest operating system versions and Firebase services.
Which are the APIs that are getting deprecated?
Check out the following link for the list of deprecated APIs: https://firebase.google.com/support/faq#fcm-23-deprecation
Impact on mobile applications
Mobile applications that continue to utilize the outdated FCM APIs (both HTTP and XMPP) must transition to the HTTP v1 API promptly. These APIs were marked as deprecated and are set to be eliminated, which could result in the loss of messaging capabilities for your app. Additionally, Onesignal, which previously supported legacy FCM APIs, has updated its integration approach.
What's the deadline for updating the library?
The deadline for migrating legacy FCM APIs to the HTTP v1 API is June 20, 2024.
What occurs in the aftermath following the deadline?
Applications utilizing outdated APIs will cease to receive FCM messages following June 2024.
How does the discontinuation of Legacy Firebase Cloud Messaging (FCM) APIs affect the functionality of the app?
Typically, FCM reliably delivers messages to an app on iOS or Android, even if the app is running in the background or has been closed. These messages serve various purposes such as alerts, updates, reminders, or marketing campaigns. FCM allows for targeted messaging, sending messages to individual devices, or groups of devices based on topics or user segments or broadcasting to all users of the app. Additionally, FCM facilitates the capture of user actions on notifications, like taps or button clicks, and manages them within the app’s logic.
Common uses of push notifications include:
- facilitating chat
- delivering announcements
- notifying users of app usage
- automatically updating applications
- issuing warning notificationsÂ
Previously, these functionalities were often managed using the FCM Legacy API. Failure to update to the HTTP v1 API will render these functionalities non-functional.
Which are the APIs that are getting deprecated?
Impact on mobile applications
What's the deadline for updating the library?
The deadline for migrating legacy FCM APIs to the HTTP v1 API is June 20, 2024.