-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Remote notifications message is null when payload uses body_loc_key in foreground #1836
Comments
Hi @plus- Please refer to: Also note that the iOS library doesn't use Firebase. Regards, |
@Dallas62 this is an issue with Android. I have no problem with IOS. See table 2.b is for Android |
thanks for reopening this issue, I believe this could be extended with If this is not a priority for you to add I can understand. Let me know. |
The issue is coming from: Which is using the
https://stackoverflow.com/questions/7493287/android-how-do-i-get-string-from-resources-using-its-name I will try to look at it this week-end, if you have time, feel free to make a PR 😉 Regards, |
I did a PR, I don't have a Java environment right now, so I couldn't test it. |
Thanks for the PR, If you have your project, you can apply your change directly in the node_modules, it's not perfect but it's help to test 😉 I will look this weekend and release it ASAP. |
Bug
This is a bug on Android.
I have an issue when trying to internationalize my notifications messages using the
body_loc_key
parameter See table 2.bWhen the app is in foreground the notification message property is null. In background the notification will display properly and show the value of the resources string.
Using the
body
parameter will properly work in background and foreground (message is the body value)Environment info
"react-native-push-notification": "^7.0.0",
react-native info
output:The text was updated successfully, but these errors were encountered: