Add user switching support in restore flow #770
+124
−0
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.
Summary
restore()could result in the SDK operating under a newly created user instead of returning to the original user. This change adds user switching logic to the restore flow so that when the backend returns a differentuid, the SDK updates its local state accordingly.identify()flow: persist the new user ID, update internal config, notify remote config manager, and clear the permissions cache.Changes
QProductCenterManager.kt: AddedhandleUserSwitchingOnRestore()method, called in therestore()success callback before caching the launch result. If the returneduiddiffers from the current local user, the SDK switches to the returned user.QProductCenterManagerTest.kt: Added 4 unit tests covering:Test plan