-
Notifications
You must be signed in to change notification settings - Fork 243
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
Flutter Amplify Push Notification. Can't send push message in IOS via Amazon Pinpoint FCM #5451
Comments
Hello @gigamike, I'm sorry but iOS Amplify only supports APN currently and thus will only generate APN tokens from onTokenReceived. We have a guides for setting up APN and for connecting it to Pinpoint. Please let me know if you have any other questions, otherwise Ill keep this issue open as a feature request for FCM support for iOS. To avoid additional confusion in the future, iOS push notifications will use APN Sandbox unless you install the app via the App Store, Tesflight, or directly from an ipa. |
Thanks for the reply @tyllark , now makes sense. Hopefully, someday Amplify Push Notification FCM support for iOS. |
Description
Hello,
The Flutter Amplify Docs is not very helpful. I don't know if this is a bug or if we can't send push notifications to iPhone/IOS using Amazon Pinpoint. Based on Amazon Pinpoint
"Firebase Cloud Messaging (FCM) – For sending messages to Android devices and web apps. It can also be used to send messages to iOS devices."
So via FCM we can send both Android and IOS.
But when I calling this
Amplify.Notifications.Push.onTokenReceived.listen((event) { print('🚀 onTokenReceived $event'); });
it generates an invalid FCM device ID, it generates an APN device ID that works on APN.
Any Ideas that when sending push notifications to IOS it's always APN and for Androis its FCM or do we need some APN to FCM device ID converter?
Thanks in advance
Categories
Steps to Reproduce
I just followed Amplify Docs
Screenshots
Platforms
Flutter Version
3.24.1
Amplify Flutter Version
2.2.0
Deployment Method
Amplify Gen 2
Schema
No response
The text was updated successfully, but these errors were encountered: