DIA-5932 fix legacy data migration causing re-messaging#875
Merged
andresilveirah merged 2 commits intodevelopfrom Sep 11, 2025
Merged
DIA-5932 fix legacy data migration causing re-messaging#875andresilveirah merged 2 commits intodevelopfrom
andresilveirah merged 2 commits intodevelopfrom
Conversation
When migrating from legacy versions, some properties don't have gcm configured and thus this value is null. If not optional, the transfer from legacy data would fail causing the SDK to start from a new State.
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
1 participant
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.
Some properties don't have GCM configured and code responsible for transferring legacy data assumed this property was not optional.
Parsing the json string for legacy GDPR data would fail, causing the SDK to start from a new state and re-message the user.