Expo adds support for FCM HTTP v1 API
Blog post from Expo
Google's shutdown of the FCM legacy API in June necessitates developers to transition to the FCM HTTP v1 API, with Expo providing support for this migration. The process requires developers to create new credentials via the Firebase console and upload them to the EAS project, either through the credentials page or using the EAS CLI. Initially, the Expo push notification service will default to the legacy API until May 13, 2024, but developers can test the v1 API by including a specific query parameter in their HTTP requests. After May 13, the service will switch to default to the v1 API, eventually requiring all projects to use it exclusively after June 20, 2024. Developers are encouraged to ensure the v1 API works correctly before optionally deleting their legacy credentials. Expo plans to introduce a new user interface for push notifications to enhance monitoring capabilities, with more details expected in May.
No tracked trend matches for this post yet.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.