DIA-6098 fix authId multiple instances#877
Merged
andresilveirah merged 7 commits intodevelopfrom Sep 18, 2025
Merged
Conversation
* kotlin version 2.1.21 * initialise authId from State if none is passed to its constructor
Nevazhnovu
approved these changes
Sep 17, 2025
Collaborator
|
@andresilveirah pay attention to the single failing test |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Authenticated consent seems to be working only on instances of the SDK that have had
loadMessagescalled withauthId.If another instance of the SDK is then initialized, that instance of the SDK won't have the value stored for
authIdand consent actions (from the PM for example), won't be stored for thatauthId.This PR and SourcePointUSA/mobile-core#78 fixes this issue.