You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Tags - Nothing happens after clicking Import tags #82456
Version Number: 9.3.19-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:#77913 Email or phone of affected tester (no customers):sdhiubsdhishiushduis@gmail.com Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: Mac 26.2 / Chrome App Component: Workspace Settings
👋 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:
Identify the pull request that introduced this issue and revert it.
Classification: Frontend bug Causing PR: #77913 - "fix: refactor ConfirmModal usage to useConfirmModal in workspace tags pages" by @daledah (High confidence) Related Issues: None
Recommendation: REVERT
The bug is a straightforward async/await issue introduced during the refactor. Reverting PR #77913 is the safest option to unblock the deploy immediately. The PR author can then fix the bug and resubmit.
Labels: No label changes needed - this is a Frontend bug, so DeployBlockerCash should remain.
Detailed Analysis
Evidence
The bug report states that clicking "Import tags" on the multi-level tags option does nothing. I traced this to a missing async keyword in the ImportTagsOptionsPage.tsx file.
PR #77913 refactored the code to use useConfirmModal hook instead of the ConfirmModal component. During this refactor, the "Multi-level tags" button's onPress handler was changed but the async keyword was omitted.
Current code at line 278 (introduced by PR #77913):
onPress={()=>{if(!isControlPolicy(policy)){setShouldRunPostUpgradeFlow(true);Navigation.navigate(...);return;}startMultiLevelTagImportFlow();// <-- async function NOT being awaited}}
Comparison - Single level button at line 242 (correctly implemented in same PR):
The startMultiLevelTagImportFlow() function (line 155) is an async function that uses await showConfirmModal() to display a confirmation modal and wait for user action. However, the "Multi-level tags" button's onPress handler is NOT async and does not await the call to startMultiLevelTagImportFlow().
When the user clicks the button:
The onPress handler calls startMultiLevelTagImportFlow()
The function starts executing and calls await showConfirmModal()
BUT the onPress handler returns immediately without waiting
The Promise from showConfirmModal() is never resolved in the context of the handler
The navigation code after the modal confirmation never executes
The fix is simple: change line 278 from onPress={() => { to onPress={async () => { OR await the call: await startMultiLevelTagImportFlow();
Why This Works on Single Level
The "Single level" button at line 242 was correctly implemented with async in the same PR, which is why it works. Only the "Multi-level tags" button has this bug.
Activity
melvin-bot commentedon Feb 13, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #77913
melvin-bot commentedon Feb 13, 2026
💬 A slack conversation has been started in #expensify-open-source
melvin-bot commentedon Feb 13, 2026
Triggered auto assignment to @greg-schroeder (
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 commentedon Feb 13, 2026
👋 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:
OSBotify commentedon Feb 13, 2026
Investigation Summary
Classification: Frontend bug
Causing PR: #77913 - "fix: refactor ConfirmModal usage to useConfirmModal in workspace tags pages" by @daledah (High confidence)
Related Issues: None
Recommendation: REVERT
The bug is a straightforward async/await issue introduced during the refactor. Reverting PR #77913 is the safest option to unblock the deploy immediately. The PR author can then fix the bug and resubmit.
Labels: No label changes needed - this is a Frontend bug, so
DeployBlockerCashshould remain.Detailed Analysis
Evidence
The bug report states that clicking "Import tags" on the multi-level tags option does nothing. I traced this to a missing
asynckeyword in the ImportTagsOptionsPage.tsx file.PR #77913 refactored the code to use
useConfirmModalhook instead of theConfirmModalcomponent. During this refactor, the "Multi-level tags" button'sonPresshandler was changed but theasynckeyword was omitted.Verification
File affected:
/home/runner/_work/App/App/src/pages/workspace/tags/ImportTagsOptionsPage.tsxCurrent code at line 278 (introduced by PR #77913):
Comparison - Single level button at line 242 (correctly implemented in same PR):
Root Cause
The
startMultiLevelTagImportFlow()function (line 155) is an async function that usesawait showConfirmModal()to display a confirmation modal and wait for user action. However, the "Multi-level tags" button'sonPresshandler is NOT async and does not await the call tostartMultiLevelTagImportFlow().When the user clicks the button:
onPresshandler callsstartMultiLevelTagImportFlow()await showConfirmModal()onPresshandler returns immediately without waitingshowConfirmModal()is never resolved in the context of the handlerThe fix is simple: change line 278 from
onPress={() => {toonPress={async () => {OR await the call:await startMultiLevelTagImportFlow();Why This Works on Single Level
The "Single level" button at line 242 was correctly implemented with
asyncin the same PR, which is why it works. Only the "Multi-level tags" button has this bug.mountiny commentedon Feb 15, 2026
Testing a revert here #82523
m-natarajan commentedon Feb 16, 2026
Issue not reproduce using v9.3.19-1 PR:82523
Screen.Recording.2026-02-16.at.7.25.16.AM.mov
mountiny commentedon Feb 16, 2026
Reverte cherry picked