-
Notifications
You must be signed in to change notification settings - Fork 12
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
ios push notifications not recieved to Flutter #1
Comments
Thank you for your input, I added this |
I've tried, changes work's for me as well. Deeplink was handled. But overall, can't read notification inside the Flutter code, as it's not received by Firebase messaging instance. |
Did you subscribing to FirebaseMessaging.onMessageOpenedApp.listen((RemoteMessage message) => _onBackgroundPushOpenedApp(message));
FirebaseMessaging.onMessage.listen((RemoteMessage message) => _onForegroundPushDisplayed(message)); Or check if the push was received while the app terminated? RemoteMessage? remoteMessage = await FirebaseMessaging.instance.getInitialMessage(); This Also nice to have are top level function marked as an entry point for iOS app Future firebaseMessagingBackgroundHandler(RemoteMessage message) async |
Yes, those listeners are written and work correctly, because my app successfully receive notifications from backend server & test notifications from Firebase console. |
This shouldn't have been closed IMO - the last message from @drybnikov only confirmed that the firebase side is working. I am able to send from firebase and the handlers are called however if i send from Klaviyo they are not. |
Hey, I've installed your package, I has Firebase messaging which correctly work with my backend server. But, Klaviyo notifications are not received by Flutter code.
Are you sure that your app getting Klaviyo notifications data inside Flutter code???
The hack, that I've used for handling deeplinks, it's I've added handling on iOS side, like code below. The only problem that I've noticed, app receiving it twice.
The text was updated successfully, but these errors were encountered: