Tags - Import button loads infinitely after importing tags

[mitarachim]

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.1-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: #69263
Email or phone of affected tester (no customers): sjdiosjnojdsojsd@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Workspace Settings

Action Performed:

Precondition:
-Tags are enabled.

1. Go to staging.expensify.com
2. Go to workspace settings > Tags.
3. Click Import.
4. Select Multi-level tags.
5. Upgrade the workspace.
6. Upload a dependant tag file.
7. Disable "These are independent tags".
8. Click Import.

Expected Result:

Confirmation modal will open after importing tags.

Actual Result:

Import button loads infinitely after importing tags.

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

Bug6933776_1756853070055!depend.csv

Bug6933776_1756853070053.tags.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @ikevin127

[melvin-bot]

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