expo-notifications FCM V1 Migration Tracking Issue
Problem
This is a tracking issue for user-reported issues related to the Spring 2024 migration of Expo Push Notifications from FCM Legacy to FCM V1 for Android devices. There have been reported instances of brokenness in production when moving from FCM Legacy to FCM V1, and this issue will serve as a central place to track our investigation and resolution of these issues. Recommend that users should now be on `expo@51.0.24` and `expo-notifications@0.28.15` or later. The remaining issues (as of 2024-08-06) are as follows: - Issues with channel ID and vibration pattern not being set correctly in notifications - Status: In progress - ENG-12759 and ENG-12770 - Vibration pattern issue being fixed in https://github.com/expo/expo/pull/30495 - Channel issue is being worked in #30762 - Issue with custom sound not working when app in background - Status: Investigating - https://github.com/expo/expo/issues/27978 and ENG-12780 - Issue with complex remapping of notification payload on Android FCMv1 - Status: Investigating - https://github.com/expo/expo/issues/30533 Fixed issues: - null `data` payload in client when receiving push notifications - See https://github.com/expo/expo/pull/28938 - handlers are not being called when app is backgrounded - See these comments from @douglowder - handlers are being called when app is foregrounded, but app resets itself (seen in development build, unconfirmed in production) - Notification icon not working - See https://github.com/expo
Unverified for your environment
Select your OS to check compatibility.
1 Fix
Solution: expo-notifications FCM V1 Migration Tracking Issue
> #24844 (comment) For me, the plugin here is unnecessary because the AndroidManifest that's created seems fine. I have 2 notification_icon additions. `<meta-data android:name="com.google.firebase.messaging.default_notification_icon" android:resource="@drawable/notification_icon"/>` and `<meta-data android:name="expo.modules.notifications.default_notification_icon" android:resource="@drawable/no
Trust Score
3 verifications
- 1
For me, the plugin here is unnecessary because the AndroidManifest that's create
`<meta-data android:name="com.google.firebase.messaging.default_notification_icon" android:resource="@drawable/notification_icon"/>` and `<meta-data android:name="expo.modules.notifications.default_notification_icon" android:resource="@drawable/notification_icon"/>` I also see mapping files declaring the png and naming it to the correct asset name. I am on expo 51.0.2 and expo-notifications 0.28.1 (both latest). On prebuild, the png file is processed and correctly placed into all the xdpi drawable asset out put folders. I've also triple checked with our UX designer that the requirements are
Validation
Resolved in expo/expo GitHub issue #28656. Community reactions: 2 upvotes.
Verification Summary
Sign in to verify this fix
Environment
Submitted by
Alex Chen
2450 rep