Categorize -Blank workspace selection page when existing workspace has disabled all categories

[lanitochka17]

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.7-4
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team

Action Performed:

Precondition:

• User has only one workspace

1. Go to staging.new.expensify.com
2. Go to workspace settings > Categories
3. Bulk select all the categories and disable them
4. Go to self DM
5. Track a manual expense in the self DM
6. Click Categorize it from the actionable whisper

Expected Result:

Since the existing workspace has no categories, clicking Categorize it should directly open category selection list for a new workspace

Actual Result:

Clicking Categorize it opens a blank workspace selection page
This issue only happens when the existing workspace(s) has disabled all the categories

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

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

Screenshots/Videos

Add any screenshot/video evidence

Bug6543727_1721124751428.bandicam_2024-07-16_18-08-27-809.mp4

View all open jobs on GitHub

[melvin-bot]

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

[arosiclair]

Looks like this is expected behavior from #43975 and this slack convo. Definitely not a blocker though I'm not sure if we want to display an empty state message here.

[allgandalf]

Yes this is a expected behaviour which was intended!, thanks @arosiclair

[arosiclair]

Looks like we'll punt adding any kind of empty state for this screen here. Closing this out