react-native-firebase icon indicating copy to clipboard operation
react-native-firebase copied to clipboard

[🐛] iOS Notification Images not displayed in background mode + setBackgroundMessageHandler not triggering

Open haytamBn opened this issue 1 year ago • 2 comments

Bug Summary:

I followed the iOS Notification Images documentation for showing an image in a push notification while the app is in the background, but the image does not display. Additionally, the setBackgroundMessageHandler function is not being triggered as expected in background mode on iOS. Environment Info:

React: 18.3.1 React Native: 0.75.2 @react-native-firebase/app: "^21.0.0", @react-native-firebase/messaging": "^21.0.0", Node: 18.19.0 Yarn: 3.6.4 NPM: 10.2.3 iOS SDK: 17.5 Testing Device: Real device ios version (17.6.1) Steps to Reproduce:

Set up Firebase Cloud Messaging and configure it according to the iOS Notification Images documentation. Use setBackgroundMessageHandler to handle background messages. Send a notification with an image URL in the payload. Test the app in background mode on iOS. Expected Behavior:

The image should be displayed in the notification when the app is in background mode. The setBackgroundMessageHandler should trigger when a message is received in the background. Actual Behavior:

The image does not appear in the notification when the app is in background mode. The setBackgroundMessageHandler function is not triggered.

haytamBn avatar Sep 28 '24 12:09 haytamBn

same issue

haidarmy avatar Oct 05 '24 08:10 haidarmy

same issue image not working

truongngodang avatar Oct 19 '24 13:10 truongngodang

Have you followed the documentation for sending a notification with an image? https://rnfirebase.io/messaging/server-integration#send-messages-with-image

Also - if your background message handler is not firing, it makes me wonder if there is a more fundamental issue with your setup that has been incorrectly configured.

russellwheatley avatar Oct 24 '24 16:10 russellwheatley

Hello 👋, to help manage issues we automatically close stale issues.

This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?

This issue will be closed in 15 days if no further activity occurs.

Thank you for your contributions.

github-actions[bot] avatar Nov 21 '24 16:11 github-actions[bot]

I want to keep this open a bit - I'm closing in on a reproducer / test platform for FCM + Apple platforms and this is a case that should be validated

mikehardy avatar Nov 21 '24 16:11 mikehardy

+1 having the same issue

sen46Sko avatar Dec 19 '24 12:12 sen46Sko

+1 I'm also having the same issue. Is there any update on this?

Aqhamza avatar Dec 26 '24 07:12 Aqhamza

Hello 👋, to help manage issues we automatically close stale issues.

This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?

This issue will be closed in 15 days if no further activity occurs.

Thank you for your contributions.

github-actions[bot] avatar Jan 23 '25 07:01 github-actions[bot]

Hello 👋 When going to Prod, either test flight or App Store (Prod), it works fine.

haytamBn avatar Jan 24 '25 11:01 haytamBn