[Due for payment 2026-08-19] Spend - Pagination number changes after opening expense from expense 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.52-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: #97005
Email or phone of affected tester (no customers): sdiojnosdjsiojdosj@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.5 / Chrome
App Component: Money Requests

Action Performed:

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Create a report and add an expense to it.
4. Create a second report and add two expenses to it.
5. Go to Spend > Expenses.
6. Open one of the expenses from Step 4.
   → Pagination shows x of 3.
7. Click on the header subtitle to open expense report.
8. Click on any expense.
9. Click RHP back button twice.

Expected Result:

Pagination will show x of 3 because there are 3 expenses.

Actual Result:

Pagination shows x of 2 when there are 3 expenses.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7230456_1786393523322.3.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Svetlana Lazutkina
Bug ID: 7230453

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/ad8f1038541f093b6e44468b9e6446d6f353e6c09c1ace8b8852fbd4a0164967

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

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

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