WS Settings - Empty state instead of loaded the first time tags or categories are loaded

[vincdargento]

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.2.59-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/folder/13176818/test-cases/41237207
Email or phone of affected tester (no customers): gatantm+1010x@gmail.com
Issue reported by: Applause Internal Team
Device used: iPhone 17 Pro Max, iOS 26.1, MacOS 26.0.1
App Component: Workspace Settings

Action Performed:

1. Launch Expensify and login with an account with Tags and Categories
2. Go to Workspaces and open one you haven't opened yet on this login
3. Tap on Categories or Tags

Expected Result:

The Categories or Tags that are added are shown

Actual Result:

The empty state is shown for a second before the Categories or Tags are shown

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

buf.mp4

View all open jobs on GitHub

[melvin-bot]

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

[roryabraham]

Not able to reproduce on dev