-
Notifications
You must be signed in to change notification settings - Fork 392
fix(ManageSpaceActivity): call clearApplicationUserData() after logout #2971
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
brandonpage
merged 5 commits into
forcedotcom:dev
from
wmathurin:fix-manage-space-clear-data
Jul 21, 2026
Merged
Changes from 4 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
fb487d7
docs(push): expand push notification documentation (W-23493430)
wmathurin e0a32cc
Revert "docs(push): expand push notification documentation (W-23493430)"
wmathurin eb3fa74
fix(ManageSpaceActivity): call clearApplicationUserData() after logout
wmathurin 844b0fb
fix(ManageSpaceActivity): use ActivityManager.clearApplicationUserDat…
wmathurin ee6a850
fix(ManageSpaceActivity): log out all users before clearing app data
wmathurin File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What happens if there are multiple users logged in?
account = nullwill only result in the current user being logged out.And what do we not clear already on logout?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch — you're right on both counts.
Multiple users:
logout(account=null)resolves toclientMgr.account→ the current user only. Other accounts never got SDK teardown beforeclearApplicationUserData()wiped their data at the OS level.Fix: Now calls
UserAccountManager.getAuthenticatedUsers()and loops, callingsignoutUser(user, activity, false, USER_LOGOUT)per account so each one goes through proper SDK cleanup (SmartStore, DPoP key deletion, token revocation). Falls back tologout(account=null)only when the user list is null/empty (fresh install / already logged out).What logout() clears that clearApplicationUserData() would already wipe: The OS call is a superset of SDK logout — it wipes all SharedPrefs, databases, files, caches, then restarts the process. Calling
signoutUserfirst still matters for server-side cleanup (push un-registration, refresh token revocation) and to give the SDK a clean teardown path before the process is killed.4 unit tests added: single user, 3 users, null list, empty list.