Security - Device is removed after dismissing the error and clearing cache

[mitarachim]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: 9.3.67-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #87948
Email or phone of affected tester (no customers): n/a
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: iPhone 13 iOS 26.3.1, Mac 15.4.1 Safari/Chrome
App Component: User Settings

Action Performed:

Precondition: logged in to multiple devices with the same account

1. Go to https://staging.new.expensify.com
2. Go to Account > Security > Device Management
3. Turn on "Simulate failing network requests"
4. Go to Account > Security > Device management
5. Press Revoke on secondary device
6. Dismiss the error
7. Turn off "Simulate failing network requests"
8. Go to Troubleshoot
9. Click Clear cache and restart
10. Go to Account > Security > Device Management

Expected Result:

The device isn't removed after clearing cache

Actual Result:

The device is removed after dismissing the error and clearing the cache. The user who signs in on another device is signed out immediately

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari

Screenshots/Videos

Bug7145365_1778013331067.ScreenRecording_05-05-2026_15-30-34_1.mp4

View all open jobs on GitHub

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #87948

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.