Closed julian-dotcom closed 2 weeks ago
Hello, @julian-dotcom and thanks for opening this issue. With v6 of Amplify, Push Notifications now has a separate channel from Analytics. This was a v6 exclusive change that uses two different endpoints for these two categories now.
Because of this, endpointId
can no longer be set manually and will be randomly generated by Amplify. This also looks similar to the request in #12623 that calls out the change.
@julian-dotcom, we'll consolidate this into the above referenced #12623 as a duplicate issue. The feature request to bring that functionality back in v6 is captured there, so feel free to add any additional upvotes, comments, context, etc. on that issue. Thank you!
Thanks for the quick response! :)
Before opening, please confirm:
JavaScript Framework
React Native
Amplify APIs
Analytics, Push Notifications
Amplify Version
v6
Amplify Categories
No response
Backend
None
Environment information
Describe the bug
What happened to the unique endpointId that you could set in AWS-Amplify v4 & v5?
In previous versions (before v6), it was possible to set the endpointId with a unique device ID and send push notifications with this identifier. Now, Typescript complains when I try to set the property and I get an error.
Is this not possible anymore? Not recommended?
Would be nice to have some clarity as to what happened because this is undocumented in the upgrade guide.
Expected behavior
Set the endpointId in the aws-config and send notifications using a unique device id.
Reproduction steps
Simply check the
export const AWS_CONFIG: ResourcesConfig = {}
for an endpointId property. I cannot find it.Code Snippet
Log output
aws-exports.js
No response
Manual configuration
No response
Additional configuration
No response
Mobile Device
No response
Mobile Operating System
No response
Mobile Browser
No response
Mobile Browser Version
No response
Additional information and screenshots
No response