[Due for payment 2026-09-03] Spend - "No expenses yet" displayed on report with expenses after returning to it via arrow.

[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: 9.4.62-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #98611
Email or phone of affected tester (no customers): ibellicotest+2766@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Motorola MotoG60 / Android 12 (Hybrid app) - Windows 11 / Chrome
App Component: Search

Action Performed:

Prerequisite: Account has a workspace.
Prerequisite 2: Have two reports created on workspace. One with at least three expenses and the other one with at least one.

1. Open the staging.new.expensify.com website.
2. Navigate to "Spend" > "Reports"
3. Open report with more than one expense.
4. Navigate to the other report via arrow carousel on top of report.
5. Return to previous report via arrow carousel.
6. Note that a "No expenses yet" message appears and expenses on report are no longer visible.

Expected Result:

Expenses on report should remain visible after returning to report via arrow navigation.

Actual Result:

"No expenses yet" message appears on report with expenses after returning to it via arrow carousel.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7243763_1787788038274.No_Yet.mp4

View all open jobs on GitHub

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

Issue Owner

Current Issue Owner: @thelullabyy

[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/13b9100349661801cc61ac6616bac32804fb334a64fc0048ccc22468c7cf69bc

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

@thelullabyy you have been assigned to this deploy blocker because you authored the offending PR: #98611

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