-
Notifications
You must be signed in to change notification settings - Fork 26
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
No Push Notification from Firebase on iOS #102
Comments
@Tommyten is it only data type notification? val notifier = NotifierManager.getLocalNotifier()
notifier.notify {
id= Random.nextInt(0, Int.MAX_VALUE)
title = "Title from KMPNotifier"
body = "Body message from KMPNotifier"
payloadData = mapOf(
Notifier.KEY_URL to "https://github.com/mirzemehdi/KMPNotifier/",
"extraKey" to "randomValue"
)
}
|
@mirzemehdi sending local notifications is indeed possible, so there should not be an issue with permissions. |
@Tommyten are you enabled Remote Notifications capability in xcode? Also did you upload apn key into Firebase? |
@mirzemehdi Reuploading the apn key to firebase fixed it, thank you for your help :) |
I'm sorry to have to reopen this issue, but unfortunately it seems that this issue still remains. |
I have further confirmed that, indeed the connection between apns and firebase is not the issue here. |
Hi @Tommyten , have you found any solution for this issue? I'm also facing a similar problem and would appreciate any insights. Thanks! |
@ismoilfozil I haven't unfortunately. I transitioned to a custom solution to work around my issues. |
KMPNotifier and Kotlin version:
kmpnotifier version: 1.4.0
kotlin version: 2.1.0
Describe the bug
When I use this library to receive and handle Firebase Push Notifications, no System Push Notification is created on iOS
In which platform bug occurs?
iOS
To Reproduce
Steps to reproduce the bug:
showPushNotification = true
Received Push Notification payload data
Expected behavior
On Android, when a Firebase push notification is received a System push notification is also created, therefore I expect the same behavior on iOS as well
The text was updated successfully, but these errors were encountered: