Home / Companies / Expo / Blog / Post Details
Content Deep Dive

FCM v1 Migration Deadline Changed to July 20th

Blog post from Expo

Post Details
Company
Date Published
Author
Chris Walter
Word Count
622
Company Posts That Month
3
Language
English
Hacker News Points
-
Post removed?
No
Summary

Developers utilizing the Expo push notifications service must migrate to the Firebase Cloud Messaging (FCM) HTTP v1 API by July 20th, as Google is discontinuing the FCM legacy API. To facilitate this transition, developers need to create a new FCM v1 credential and upload it to the Expo Application Services (EAS). While Expo has integrated support for the FCM HTTP v1 API, the migration requires manual credential updates since the credentials differ from the legacy API. After uploading the new credentials, developers can test their applications using the FCM v1 API by modifying their HTTP requests to the Expo push notification service. This change is crucial for continuing to send push notifications to Android devices, and developers are advised to update their client code to the latest versions of expo-notifications and Expo SDK 51. Support is available via Expo's support channels for any issues during the transition, and developers are encouraged to delete their legacy credentials once satisfied with the FCM v1 functionality.

Trends Found in this Post

No tracked trend matches for this post yet.

Use This Data

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.