-
Notifications
You must be signed in to change notification settings - Fork 249
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
How to register VOIP token #5782
Comments
Hello @kouz75 thanks for taking the time to open up the issue. Have you already enabled APNs VoIP in your AWS Console under Also I'm not familiar with callkeep so could you please confirm if this is the correct pubdev package and if you need a token different from our onTokenRecieved Stream. |
Hi, Yes, both APNs and APNs VOIP are configured and working correctly (tested with the Apple Push Notification Console). CallKeep (actually the PushKit Framework) requests a new token from Apple, which is used to send VOIP Push notifications. You can find more information here. On Amplify, we should be able to set this new token in addition to the standard token. (or amplify can manage everything on his side) On the Pinpoint side, a user should have two endpoints: thanks |
Hello @kouz75, sorry for the delayed reply. Amplify only supports a subset of Pinpoint features and unfortunately APN VoIP is not one of those. I will keep this issue open as a feature request. In the meantime we do have an aws_signature_v4 package that can be used communicate with AWS services outside of Amplify. With that package you might be able to send your token to the Pinpoint APN VoIP Channel. |
Hi,
Pinpoint support APNS and APNs VoIP to manage video call.
-> the app (the user) have 2 devices token one for each channel.
Amplify manage the APNS token without any issue.
In our app, we use callkeep which request the APNs VoIP token.
Is there a way to register this token in pinpoint ?
does pinpoint is able to choose the correcte token depending of the push type ?
thanks
The text was updated successfully, but these errors were encountered: