We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hey love the lib,
But ideally public fun onPushNotification(title: String?, body: String?) {} should also take nullable payload.
public fun onPushNotification(title: String?, body: String?) {}
Most cases one would filter these messages and decide to show them based on if the user is logged in (pushes include userId).
Theres a couple of quick fixes:
public fun onPushNotification(title: String?, body: String?, data: PayloadData?) {}
Or you can pipe the notification title/body into the payload (which is what I used to do)
val payloadData = message.data.toMutableMap() message.notification?.also { payloadData["title"] = it.title ?: payloadData["title"] payloadData["body"] = it.title ?: payloadData["body"] } notifierManager.onPushPayloadData(data)
Or you can pass the notification to onPushPayloadData(title, body, data)
onPushPayloadData(title, body, data)
The TLDR is that these shouldn't be seperate methods, it should be up to the consumer how the handle show incoming messages.
The text was updated successfully, but these errors were encountered:
onPushNotificationWithPayloadData
Implemented in #110
Sorry, something went wrong.
No branches or pull requests
Hey love the lib,
But ideally
public fun onPushNotification(title: String?, body: String?) {}
should also take nullable payload.Most cases one would filter these messages and decide to show them based on if the user is logged in (pushes include userId).
Theres a couple of quick fixes:
Or you can pipe the notification title/body into the payload (which is what I used to do)
Or you can pass the notification to
onPushPayloadData(title, body, data)
The TLDR is that these shouldn't be seperate methods, it should be up to the consumer how the handle show incoming messages.
The text was updated successfully, but these errors were encountered: