Skip to content

Conversation

@rodrigo-fournier-immutable
Copy link
Collaborator

Summary

This PR adds support for the 'subscribed' marketing consent status to ensure compatibility with Auth0's default marketing consent value.

Changes

  • Add Subscribed enum value to MarketingConsentStatus
  • Add parsing for 'subscribed' status in PassportUI login flow
  • Update ToApiString() method to handle 'subscribed' conversion

Why

Auth0 returns 'subscribed' as the default marketing consent status, but the Unity SDK only recognized 'opted_in' and 'unsubscribed'. This was causing authentication warnings and potential flow issues.

Testing

  • Updated enum to include Subscribed value
  • Updated parsing logic in PassportUI
  • Updated ToApiString conversion method
  • CI/CD tests pending

Related

- Add Subscribed enum value to MarketingConsentStatus
- Add parsing for 'subscribed' status in PassportUI login flow
- Update ToApiString() method to handle 'subscribed' conversion

Ensures compatibility with Auth0 default marketing consent value
…chain

Following the ts-immutable-sdk Passport v3 refactoring (commit 240cd2f15,
Dec 8 2025), which introduced stricter validation via toUserImx() during
user registration, we now explicitly handle the 409 Conflict error in
ImxRegisterScript.

When a user is already registered off-chain, the API returns a 409 error with
USER_REGISTRATION_ERROR type. This change detects this specific scenario and
displays a user-friendly message: 'Passport account already registered'.

This ensures the UI tests (test_4_imx_functions) continue to pass and provides
a better user experience when attempting to register an already registered
account.
Apply the same 409 error handling fix to the sample app version of
ImxRegisterScript.cs that was previously applied to the Samples~ package
version. The CI tests use the sample app directory, so both files need
the same fix.
@rodrigo-fournier-immutable rodrigo-fournier-immutable deleted the feat/passport-subscribed-marketing-consent branch December 17, 2025 04:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants