[Due for payment 2026-08-25] Spend - Expenses count does not update after adding expense to report

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

Action Performed:

1. Go to staging.new.expensify.com
2. Create an empty report in workspace chat.
3. Create an expense in self DM.
4. Go to Spend > Reports.
5. Select the report via checkbox.
6. Open the report.
7. Click Add expense > Add existing expense.
8. Select self DM expense > Add to report.
9. Close the report.

Expected Result:

Expenses count will update after adding expense to report.

Actual Result:

Expenses count does not update after adding expense to report.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7233941_1786743963405.7.mp4

View all open jobs on GitHub

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

Issue Owner

Current Issue Owner: @QichenZhu

[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/dd24092922672a790ab884454039d1402b96de3da5847215916c55e85c59e0a5

[melvin-bot]

@mountiny recently merged #98558, but they are OOO right now, so I'll auto-assign someone else.

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

[melvin-bot]

Triggered auto assignment to @youssef-lr (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

@mountiny @QichenZhu you have been assigned to this deploy blocker because you reviewed the offending PR: #98558

[melvin-bot]

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