Tag remain unlocked until navigating to other page

[nlemma]

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.1.48-0
Reproducible in staging?: Yes
Reproducible in production?: Unable to check - New feature testing
If this was caught during regression testing, add the test name, ID and link from TestRail: #58052
Email or phone of affected tester (no customers): testpayment935@gmail.com
Issue reported by: Applause Internal Team
Device used: Windows 10 /Chrome, Samsung Galaxy s10/ Chrome, Samsung Galaxy s10/ Android 12
App Component: Workspace Settings

Action Performed:

Precondition: Have a policy requires tag and requires category set to true.

1. Navigate to staging.new.expensify.com
2. Create WS and Navigate to Category
3. Disable every category except one
4. The remaining category is enabled and locked instantly
5. Navigate to Tag
6. Create more than one tag
7. Disable every Tag except one

Expected Result:

The one Tag should be locked immediately without navigating to other page or refresh (Category behavior)

Actual Result:

The one tag remain unlocked and can be disabled until navigating to other page or refresh

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

Bug6838614_1747858695131.bandicam_2025-05-21_23-05-20-191.mp4

View all open jobs on GitHub

[melvin-bot]

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

[nlemma]

@JmillsExpensify FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

[marcaaron]

cc @mollfpr seems related to #58052

IMO seems pretty benign / non-blockery. That PR is also quite large.