DIA-2065 / DIA-2120 fix state management for authenticated consent and handle pv-data response #430
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR addresses 2 items:
State management when
authId
changesThe SDK now correctly implements the following logic, related to state management when
authId
changes:authId
changes fromnil
->"something"
: state is persisted (consent is then linked to the current uuid)authId
changes from"something"
->nil
: state is persisted (storedauthId
remains"something"
)authId
changes from"something"
->"something else"
: state is reset (andauthId
becomes"something else"
)Handling
/pv-data
responseThe
/pv-data
endpoint not only logs a "pageview" but also returns a new consent uuid for a given campaign.Previously the SDK would not wait for the response of
/pv-data
. And this causes issues with reporting as well as a missing consent uuid in the stored consent data (until the user takes a consent action).