mWeb - Expense - System message 'Exported to CSV' displays 2 times when export by Select from Reports tab

[jponikarchuk]

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: v9.2.16-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: https://test-management.browserstack.com/projects/2219752/test-runs/TR-856/folder/13176922/41237500/907086858
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause Internal Team
Device used: iPhone 16 pro/ Safari
App Component: Money Requests

Action Performed:

1. Open https://staging.new.expensify.com
2. Create a workspace
3. Navigate to workspace chat create and submit a manual expense
4. Tap on Reports tab
5. Hold the manual expense for open "Select" option
6. Tap on Select option
7. Tap on Export
8. Tap on Basic export or All Data- expense level
9. Tap on Download of the confirm download
10. Tap on the manual expense and scroll down to the end

Expected Result:

System message 'Exported to CSV' should display correct on the expense detail page

Actual Result:

System message 'Exported to CSV' is displayed two times on the expense detail page

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

1.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @RachCHopkins (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[melvin-bot]

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

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