[Payment due Oct 7][$250] [Support CSV] Categories - File contains errors when downloading CSV with no category

[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: 9.0.32-3
Reproducible in staging?: Y
Reproducible in production?: N/A - new feature, doesn't exist in prod
Email or phone of affected tester (no customers): applausetester+kh010901@applause.expensifail.com
Issue reported by: Applause Internal Team

Action Performed:

1. Go to staging.new.expensify.com
2. Go to Workspace settings > Categories.
3. Delete all the categories.
4. Tap 3-dot menu.
5. Tap Download CSV.
6. Open the downloaded file.

Expected Result:

The file should not contain error when downloading CSV with no categories.

Actual Result:

The file contains errors when downloading CSV with no category.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6600256_1726080845912.Screen_Recording_20240912_024951_Sheets.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021833956684433969336
• Upwork Job ID: 1833956684433969336
• Last Price Increase: 2024-09-11
• Automatic offers:
• brunovjk | Reviewer | 103982747
• cretadn22 | Contributor | 103982748

Issue Owner

Current Issue Owner: @brunovjk

[melvin-bot]

Triggered auto assignment to @Christinadobrzyn (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 @blimpich (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.

[blimpich]

Looking into this.