[Due for payment 2026-03-30] [$250] iOS - Tag - Tag creation page is not dismissed after saving a new tag

[jponikarchuk]

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.3.27-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/test-runs/TR-7049/folder/13176676/41237285/1218710802
Email or phone of affected tester (no customers): htad26+ewrui@gmail.com
Issue reported by: Applause Internal Team
Bug source: Regression TC Execution
Device used: iPhone 13/iOS 26.3
App Component: Workspace Settings

Action Performed:

1. Sign in to the app
2. Create a new workspace
3. Enable tags
4. Navigate to tags > Add tag > Enter a name
5. Save

Expected Result:

The modal is dismissed and app returns to tag list page

Actual Result:

The modal isn't dismissed after saving tag

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @mallenexpensify

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022027482773716848522
• Upwork Job ID: 2027482773716848522
• Last Price Increase: 2026-02-27

[melvin-bot]

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

[OSBotify]

Investigation Summary

Classification: Frontend bug
Causing PR: #82587 - "Migration navigation from InteractionManager to TransitionTracker" by @blazejkustra (High confidence)
Related Issues: #71913 (Tracking issue for InteractionManager deprecation)

Recommendation: REVERT

PR #82587 should be reverted as it introduces a regression in the tag creation flow on iOS, preventing the modal from dismissing after saving a tag.

Labels: Keeping DeployBlockerCash (App deploy is blocked). No label changes needed - this is correctly labeled as a frontend bug.

Detailed Analysis

Evidence

PR #82587 modified src/pages/workspace/tags/WorkspaceCreateTagPage.tsx to migrate from the old keyboard dismissal pattern to the new TransitionTracker system. The specific change was:

Before:

createPolicyTag(policyData, values.tagName.trim(), setupTagsTaskReport, setupCategoriesAndTagsTaskReport, policyHasCustomCategories);
Keyboard.dismiss();
Navigation.goBack(isQuickSettingsFlow ? ROUTES.SETTINGS_TAGS_ROOT.getRoute(policyID, backTo) : undefined);

After:

createPolicyTag(policyData, values.tagName.trim(), setupTagsTaskReport, setupCategoriesAndTagsTaskReport, policyHasCustomCategories);
KeyboardUtils.dismiss({
    afterTransition: () => Navigation.goBack(isQuickSettingsFlow ? ROUTES.SETTINGS_TAGS_ROOT.getRoute(policyID, backTo) : undefined),
});

The navigation is now wrapped in an afterTransition callback that depends on the TransitionTracker system to execute.

Verification

• The bug is reproducible only in staging (v9.3.27-0), not in production
• PR Migration navigation from InteractionManager to TransitionTracker #82587 was merged on 2026-02-26 and is included in the staging deploy checklist (item Update timestamps automatically #80 in chronological order)
• The PR modified src/pages/workspace/tags/WorkspaceCreateTagPage.tsx, which is the exact page affected by this bug
• Issue affects iOS App (the platform where keyboard behavior differs)

Root Cause

The KeyboardUtils.dismiss() function in src/utils/keyboard/index.ts has a logic issue that affects iOS:

1. When dismiss() is called, it checks if the keyboard is visible
2. If the keyboard is NOT visible, it returns immediately without executing the afterTransition callback (lines 27-30)
3. On iOS, there may be timing issues where the keyboard state is not correctly tracked, or the keyboard hide event does not fire properly, leaving the transition hanging
4. This prevents the Navigation.goBack() call from executing, causing the modal to remain open

The TransitionTracker system itself may have issues on iOS with tracking keyboard transitions, or the keyboard may already be dismissed by the time the code runs, causing the callback to never execute.