Home - Spend over time chart only appears after opening it on Spend tab

[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.62-5
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #85234
Email or phone of affected tester (no customers): sdsodijnosdjoij@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.2 / Chrome
App Component: Other

Action Performed:

1. Go to staging.new.expensify.com
2. Create a new account and complete onboarding.
3. Create a workspace.
4. Go to workspace chat.
5. Create two expenses with date from Feb and Mar.
6. Go to Home.
   → Spend over time chart is not shown.
7. Go to Spend > Spend over time.
8. Go to Home.
   → Spend over time chart is only shown after opening it on Spend tab.

Expected Result:

In Step 6, Spend over time chart will appear on Home tab without opening it on Spend tab.

Actual Result:

In Step 6, Spend over time chart does not appear on Home tab.
In Step 8, Spend over time chart is only shown after opening it on Spend tab.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7139261_1777296956334.5.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @sumo-slonik

[melvin-bot]

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

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