Skip to content

feat: Support UserIdentificationType#119

Merged
rmi22186 merged 2 commits intomainfrom
feat/handle-UserIdentificationType
Mar 25, 2026
Merged

feat: Support UserIdentificationType#119
rmi22186 merged 2 commits intomainfrom
feat/handle-UserIdentificationType

Conversation

@BrandonStalnaker
Copy link
Copy Markdown
Contributor

Summary

  • Adds userIdentificationType so AppsFlyer’s customer user ID can follow MPID, CustomerId, or legacy behavior, including launch/identity-callback sync and commerce af_customer_user_id via customerIDForAppsFlyer:.
  • setUserIdentity is updated so MPID mode ignores customer-ID identity for AppsFlyer’s customer user ID but still returns success, while legacy and CustomerId mode keep forwarding that identity to AppsFlyer.

Testing Plan

  • Was this tested locally? If not, explain why.
  • The mock now records writes to AppsFlyer’s customerUserID property (the real SDK path) so tests can assert when the kit sets it.
  • New tests cover setUserIdentity for legacy, CustomerId, and MPID modes plus email and unsupported identity types, alongside the existing manualStart / didBecomeActive checks.

Reference Issue (For mParticle employees only. Ignore if you are an outside contributor)

@BrandonStalnaker BrandonStalnaker self-assigned this Mar 25, 2026
@BrandonStalnaker BrandonStalnaker force-pushed the feat/handle-UserIdentificationType branch 5 times, most recently from 97569e7 to 2f763d7 Compare March 25, 2026 13:54
@BrandonStalnaker BrandonStalnaker force-pushed the feat/handle-UserIdentificationType branch from 2f763d7 to 225abeb Compare March 25, 2026 13:58
Co-authored-by: Robert Ing <rmi22186@gmail.com>
@rmi22186 rmi22186 merged commit e58e6e0 into main Mar 25, 2026
15 checks passed
@rmi22186 rmi22186 deleted the feat/handle-UserIdentificationType branch March 25, 2026 16:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants