-
Notifications
You must be signed in to change notification settings - Fork 236
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with notification.data being empty in Notifee #1103
Comments
I am also experiencing the same issue! Notifee Version: 9.1.1 |
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?
Thank you for your contributions. |
Experiencing the same issue in iOS as well. Notifee Version: |
I have the same issue, and after spending 2 hours figuring it out, you need to set the
|
I have the same issue of UPDATE: This should be in the documentation. Added the
|
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?
Thank you for your contributions. |
I am encountering an issue with the notification.data object being empty when receiving notifications in my React Native application. Here are the details:
Issue Description:
When I send a notification with both notification and data payloads from my PHP server, the data field in the notification is empty when handling the notification click event in Notifee.
Example FCM Payload Sent from Server:
Expected Behavior:
I expect the notification.data object to contain the keys bookingId and otherInfo when clicking on the notification.
Current Behavior:
The notification.data object is empty when the notification is clicked.
I would appreciate your assistance in resolving this issue.
Thank you!
The text was updated successfully, but these errors were encountered: