More button is not responsive when opening next report and quickly clicking More menu

[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.3.62-5
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #88522
Email or phone of affected tester (no customers): sdsodijnosdjoij@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.2 / Chrome
App Component: Money Requests

Action Performed:

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Create two reports.
4. Go to Reports > All reports.
5. Open any report.
6. If the report does not show left & right arrow button, open both reports, go to Inbox then return to Reports > All reports, then open any report.
7. Click left or right button, then quickly click More button.

Expected Result:

More menu will open.

Actual Result:

More button is not responsive when opening next report and quickly clicking More menu.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7139250_1777296480605.1.mp4

View all open jobs on GitHub

[melvin-bot]

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

[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: #88522 - "perf: defer mount of MoneyReportHeaderSecondaryActions" by @TMisiukiewicz (High confidence)
Related Issues: #88524, #77173

Recommendation: REVERT

PR #88522 introduced a deferred-mount wrapper (NavigationDeferredMount) around the "More" button's real implementation. When the user clicks the left/right report navigation arrow, a new transition begins, causing the deferred-mount component to swap back to its placeholder (a no-op Button), making the "More" button unresponsive until the transition fully settles and startTransition fires.

Assigned: @TMisiukiewicz (PR author), @roryabraham (approving reviewer), @rlinoz (approving reviewer)
Labels: Both DeployBlockerCash (App deploy) and DeployBlocker (Web deploy) are currently present. This is a Frontend bug — DeployBlockerCash should be kept and DeployBlocker should be removed.

Detailed Analysis

Evidence

• The issue is staging-only (version 9.3.62-5), not reproducible in production.
• The melvin-bot automatically identified PR perf: defer mount of MoneyReportHeaderSecondaryActions #88522 as the cause (it was recently merged on 2026-04-24).
• The bug occurs specifically when clicking left/right navigation arrows between reports, then quickly clicking the "More" button — exactly the scenario that would trigger NavigationDeferredMount to revert to its placeholder.
• PR perf: defer mount of MoneyReportHeaderSecondaryActions #88522 wraps MoneyReportHeaderSecondaryActionsInner in NavigationDeferredMount with waitForUpcomingTransition: true, which means every navigation transition resets the mounted state back to the placeholder.

Verification

• Affected files: src/components/MoneyReportHeaderActions/MoneyReportHeaderSecondaryActions.tsx and src/components/NavigationDeferredMount.tsx.
• PR perf: defer mount of MoneyReportHeaderSecondaryActions #88522 directly modifies MoneyReportHeaderSecondaryActions.tsx (the "More" button component) and introduces NavigationDeferredMount.tsx.
• The placeholder Button has onPress={() => {}} — a no-op — so any click during the deferred window does nothing.

Root Cause

NavigationDeferredMount renders a cheap placeholder Button (with an empty onPress) until the navigation transition completes, then mounts the real MoneyReportHeaderSecondaryActionsInner. When the user navigates between reports using the arrow buttons, waitForUpcomingTransition: true causes the component to wait for the transition to start and then finish before swapping in the real component. If the user clicks "More" during this window (which can last up to MAX_TRANSITION_START_WAIT_MS = 1000 ms as a fallback, plus the actual transition duration), the click hits the no-op placeholder instead of the real dropdown, producing the unresponsive behavior described in the issue.