-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Pinpoint endpoint user ID keeps getting set to identityId #13174
Comments
Hey there, @nigelAt8Seats and thank you for opening this issue. To better understand what's happening here, do you have some frontend code you can share that details how/where you're calling |
Hiya,
We have a cognito user provider.
The problem has existed for months... Turning off Analytics has made it less frequent; but still possible. |
Disabling analytics
|
@nigelAt8Seats, appreciate the sample code. Just to confirm, is this all areas where |
Updating this issue to be a bug and we are actively investigating this further. It looks like the root problem is with the UpdateEndpoint util in core where we are using a fallback value that changes what is set when calling an API like We'll update this issue as we make progress. |
Amplify JS v6.3.1 has just been released. It should contain the following fixes: We believe these fixes should resolve your issue of the endpoint being overwritten by the device registration. Could you please help us by verifying if this is indeed the case by updating to the latest Amplify version? Thank you |
We moved to using firebase cloud messaging instead of pinpoint to avoid the issue entirely. |
@nigelAt8Seats, we appreciate the follow up comment and will close the issue as resolved at this point. Feel free to let us know if you're able to validate fixes and come back to Analytics/Pinpoint at any time! |
Before opening, please confirm:
JavaScript Framework
React Native
Amplify APIs
Analytics, Push Notifications
Amplify Version
v6
Amplify Categories
analytics, notifications
Backend
Amplify CLI
Environment information
Describe the bug
React Native app. We send pinpoint push notifications and analytics.
We
PushNotifications.identitfyUser
as soon as we have the cognito sub. We always use the cognito sub. Logging shows we never call it incorrectly... but the endpoints keeps getting their user id set to the identityId. This breaks notifications as we can't look up the endpoints using the user id any more.I've experimented with turning off all the analytics I can.
I can still create the problem intermittently by minimising the app while it's loading... before the user id has been set.
Expected behavior
The user id in the endpoints should stay set to the cognito user id.
Reproduction steps
I can still create the problem intermittently by minimising the app while it's loading... before the user id has been set.
Code Snippet
// Put your code below this line.
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
The text was updated successfully, but these errors were encountered: