Search - No "exported to CSV" system message and invalid data in downloaded CSV file

[IuliiaHerets]

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.0.22-7
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp https://expensify.testrail.io/index.php?/tests/view/4874296
Email or phone of affected tester (no customers): applausetester+kh050806@applause.expensifail.com
Issue reported by: Applause Internal Team

Action Performed:

1. Go to staging.new.expensify.com
2. Create a new workspace,
3. Go to workspace chat.
4. Submit two expenses.
5. Pay elsewhere the report.
6. Go to Search.
7. Go to Paid status.
8. Select the "Select all" checkbox for the paid expense report in Step 5.
9. Click on the dropdown > Download.
10. Go back to expense report in Step 5.
11. Refresh the page.
12. Open the CSV file.

Expected Result:

In Step 11, there will be "exported to CSV" system message in the expense report.
In Step 12, the CSV file will show the correct expense details.

Actual Result:

In Step 11, there is not "exported to CSV" system message in the expense report.
In Step 12, the CSV file shows invalid data.

Workaround:

Unknown

Platforms:

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6577258_1724173096081.20240821_005406.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @CortneyOfstad (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 @tgolen (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

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

[IuliiaHerets]

We think that this bug might be related to #wave-collect - Release 1

[luacmartins]

We reverted the offending PR. Closing.