Hi,
I noticed that this OutSystems supported Firebase Cloud Messaging (FCM) component still uses Firebase's 'Legacy' HTTP API.
Firebase strongly recommends using the FCM HTTP v1 service API for any new developments. That API, among other things, uses OAuth 2.0 for authentication. It has been around since 2018 by the way, so more than 4 years.
Are there any plans to update this component to use the new v1 API?
Regards,
Steven
Hello OutSystems Community and Developers,
I've noticed that the OutSystems-supported Firebase Cloud Messaging (FCM) component still uses the 'Legacy' HTTP API. Given that Firebase strongly recommends the FCM HTTP v1 API, are there any plans to update this component? The v1 API offers several benefits, such as:
Enhanced Security: OAuth 2.0 for authentication.
Advanced Features: Support for better message targeting and more platforms.
Future-proofing: Google is more likely to maintain and update the v1 API.
This update is crucial for us, especially in planning for future projects requiring a secure and efficient FCM implementation. Could you please provide an update on this?
Best Regards, Humberto
This supported plugin needs updated asap. The current version of the api that it uses will be turned off this coming June.