[Due for payment 2026-01-28] [Due for payment 2026-01-20] Tag - App crashes when import multi-level tags

[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.2.96-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #76016
Email or phone of affected tester (no customers): ndk.2303+179@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Critical User Impact
Device used: Windows 11 Home/Chrome
App Component: Workspace Settings

Action Performed:

1. Open https://staging.new.expensify.com/
2. Create new collect workspace
3. Go to workspace setting
4. Enable tags
5. Go to Tags
6. Click 'Import' button
7. Select 'Multi-level tags' & upgrade
8. Upload 'multi-level tags' file
9. Click 'Next'
10. Click 'Import'

Expected Result:

user successfully import the tags

Actual Result:

app crashes

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari

Screenshots/Videos

Bug7043844_1767891277317.bandicam_2026-01-08_23-49-56-563.mp4

Bug7043844_1767891359823!Independent_-_Multi_Level_tags (1).csv

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @CortneyOfstad

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #76016

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[melvin-bot]

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

[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.

[situchan]

Commented in offending line