[Due for payment 2026-09-03] Spend - Arrow carousel disappears after duplicating expense.

[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 a report with two manual expenses created on workspace chat.

1. Open the staging.new.expensify.com website.
2. Navigate to "Spend" > "Reports"
3. Open the report created on workspace chat.
4. Open one of the expenses created in it.
5. Note that arrow carousel is displayed on top.
6. Click on "More" > "Duplicate Expense"
7. Note that arrow carousel is not displayed on top once you are navigated to expense again.

Expected Result:

Arrow carousel should still be visible when returning to expense after duplicating it.

Actual Result:

Arrow carousel disappears when returning to expense after duplicating it.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7243805_1787794651457.Carousel_Disappears.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7243805

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

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