[Due for payment 2026-07-13] Android - Expense - More button overlaps with next step message and hardly tappable

[applause-bot]

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.4.17-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: #93437
Email or phone of affected tester (no customers): sdjnoisdjdosijsonssjo@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Samsung Galaxy S25 FE / Android 16
App Component: Money Requests

Action Performed:

1. Launch Expensify app.
2. Go to workspace chat.
3. Create an empty report.
4. Open the report.

Expected Result:

More button will not overlap with next step message.

Actual Result:

More button overlaps with next step message and it is hardly tappable.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

View all open jobs on GitHub

Applause Internal Information
Exported by: Mita Rachim
Bug ID: 7188079

Issue Owner

Current Issue Owner: @hungvu193

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/40faacdbf478615318c69bf9319bd5cb3fd0d2c1d1ecc3255ca03c9d776705a1

[melvin-bot]

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

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

[MelvinBot]

Proposal

Note: PR #93437 was auto-assigned as the deploy blocker, but its diff only adds new style helpers and is not the cause. The real regression is a layout wrapper added elsewhere in the 9.4.17 deploy (details below).

Problem

On an empty expense report (Android native, narrow layout), the More secondary-actions button overlaps the next‑step banner and is hardly tappable. Reproducible in 9.4.17-0 staging, not in production — so the regression entered with the 9.4.17 deploy.

Root Cause

The "More" dropdown relies on flex1 to take the remaining width of the header action row. A newly‑introduced wrapper View between the action row and the button has no style, so it collapses to content width and the button's flex1 no longer applies against the row. On an empty report there's no primary action, so the More button is the only child that should stretch — which is exactly the case that breaks.

• The action row is flexRow with the More button expected to stretch via flex1: MoneyReportHeaderActions/index.tsx:75-90.
• The real dropdown applies styles.flex1 when narrow + no primary action: MoneyReportHeaderKYCDropdown.tsx:105.
• But the dropdown is now wrapped by ReportSubmitToPopoverAnchor → a bare, unstyled measurable View: ReportSubmitToPopoverAnchor.tsx:250-265, inserted at MoneyReportHeaderSecondaryActions.tsx:431-436.
• Tell: the placeholder path applies flex1 to its own direct View (no anchor wrapper) and lays out correctly — so the overlap only appears once the real dropdown mounts: MoneyReportHeaderSecondaryActions.tsx:439-455.

Why this is the 9.4.17 regression (git evidence)

The unstyled anchor wrapper was added in commit 9dc22758625 ("change the approach to use the Popover instead"). The first release tag containing it is 9.4.17-0-staging — it is not in any 9.4.16 build, which matches "staging yes, production no." It reached main via the merge of #92378 on 2026-06-19 (the change originated from #87998).

git tag --contains 9dc22758625 | grep 9.4.1x  ->  9.4.17-0-staging (earliest)

Recommended Fix

Make the measurable anchor wrapper layout‑transparent so the inner button's flex1/w100 still apply against the action row. Thread an optional wrapperStyle from MoneyReportHeaderSecondaryActionsInner through ReportSubmitToPopoverAnchor to the <View ref={anchorRef}> at ReportSubmitToPopoverAnchor.tsx:257-263, applying the same condition the placeholder/dropdown already use ((shouldUseNarrowLayout || isMediumScreenWidth) && !primaryAction && !isInLandscapeMode → styles.flex1).

This mirrors existing working code and keeps the wrapper neutral in the wide / primary-action layouts. (A blunter alternative — always giving the wrapper flexGrow: 1 — risks affecting the wide layout, so the conditional passthrough is preferred.)

Confidence: High

Root-cause mechanism and the introducing commit are confirmed by code + git tag evidence. The only thing not yet visually confirmed is the exact pixel overlap — a quick Android emulator repro (open an empty expense report in a workspace chat) would validate the fix. This is a pure client-side layout regression, so logs are not relevant.

---

Next Steps for Contributor+ team:
To accept: @MelvinBot implement [this](https://github.com/Expensify/App/issues/94254) to create a draft PR.
To refine: @MelvinBot <your feedback>
To reject: Explain why you are rejecting Melvin's proposal.