You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit edfe844
Browse filesBrowse the repository at this point in the historyBrowse files
Composite login creates the user directly, so data set on the anonymous user
before login was left behind. It now sends the anonymous user's onesignal_id
with the external ID, and Create User attaches the external ID to that user,
matching what login(externalId) does through SetAlias. A 409 means the external
ID already belongs to another user, so it retries without the onesignal_id.
Co-authored-by: Cursor <cursoragent@cursor.com>
Copy file name to clipboardExpand all lines: OneSignalSDK/onesignal/core/src/main/java/com/onesignal/user/internal/operations/impl/executors/LoginUserOperationExecutor.kt
+15Lines changed: 15 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -99,6 +99,11 @@ internal class LoginUserOperationExecutor(
99
99
// rewrite the call to identify by the new (not-yet-registered) `external_id`, producing
100
100
// a 404 or idempotent success against the wrong user. createUser's identities-map path
101
101
// handles the merge correctly through backend upsert semantics.
Copy file name to clipboardExpand all lines: OneSignalSDK/onesignal/core/src/test/java/com/onesignal/user/internal/operations/LoginUserOperationExecutorTests.kt
0 commit comments