Product Window - Product marketing window flickers after logging in and clearing the cache

[applause-bot]

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.

---

Version Number: v9.4.50-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: #96141
Email or phone of affected tester (no customers): n/a
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 15.4.1 Safari/Chrome, iPhone 13 iOS 26.5
App Component: User Settings

Action Performed:

1. Go to https://staging.new.expensify.com
2. Create a new account
3. Create a new workspace
4. Dismiss the product marketing window
5. Log out
6. Sign in again with the same account
7. Go to Account > Troubleshoot
8. Click Clear cache and restart

Expected Result:

Product marketing window should not flicker

Actual Result:

Product marketing window flickers after logging in and clearing the cache

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7226088_1785893101411.Recording__2672.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Mita Rachim
Bug ID: 7226088

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/587f2907ae3f17b3823ea694c06a011010cda81da2954b559a7c2c1835c60cd6

[melvin-bot]

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

[melvin-bot]

@JS00001 @huult you have been assigned to this deploy blocker because you reviewed the offending PR: #96141

[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.