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
[Due for payment 2026-07-29] Expense-More button is not aligned with the header in expense details in 1:1 chat #96575
Version Number: 9.4.41-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/folder/13176922/test-cases/41237503 Email or phone of affected tester (no customers): N/A Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: MacBook Air 26.5.2 App Component: Money Requests
Action Performed:
Navigate to Account - Troubleshoot and clear cache
Navigate to 1:1 chat
Create a manual expense
Click on the expense preview and observe the expense header and More button
Expected Result:
The More button is aligned with the header in the expense details
Actual Result:
The More button are not aligned with the header in the expense details in 1:1 chat.
👋 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.
Regression traced to #90403 — "Standardize Expense Report and Expense header with predictable button placement and carousel counter" (thelullabyy, merged 2026-07-17). It's a line item in the 9.4.41-0 StagingDeployCash and is the only staging-only PR that restructures the expense header layout, which matches "reproducible in staging, not production."
What is the root cause of that problem?
That PR restructured MoneyRequestHeader.tsx in two ways that shift the More button off the header baseline:
It wrapped the buttons row in a styles.mtn1 container — a marginTop: -4 negative offset (spacing.ts:354) — that pulls the button up by 4px so it no longer lines up with the avatar/title.
It changed the inline-render guard to !shouldDisplayButtonsInSeparateLine && !statusBarProps, so when a status is shown the More button is no longer rendered inline in the header row; it's relocated into the new mtn1-shifted status/actions row below.
Net effect: on the affected layout the More button renders in a row that's offset 4px upward (and/or relocated), so it's visually misaligned with the header.
Residual uncertainty (medium confidence on the exact pixel path): which branch the specific repro hits depends on window/RHP width and whether the manual expense shows a status. On a wide desktop with no status the inline branch is unchanged, so the misalignment most likely comes from the RHP/narrow-pane separate-line branch (the mtn1 wrapper) or from the status-bar relocation. A quick visual check while toggling the RHP width will confirm which one.
What changes do you think we should make in order to solve the problem?
Remove or correct the styles.mtn1 (marginTop: -4) offset added to the buttons/status rows in MoneyRequestHeader.tsx (and re-check the relocated More button placement) so the button re-aligns to the header baseline. Because this is a deploy blocker, the fastest safe path is a revert of #90403 (or a targeted follow-up by the author) if a clean fix isn't quick.
This fix is entirely within the App repo.
No duplicate issues found in a quick scan.
Next Steps for Contributor+ team: To accept:@MelvinBot implement [this](https://github.com/Expensify/App/issues/96575) to create a draft PR. To refine:@MelvinBot <your feedback> To reject: Explain why you are rejecting Melvin's proposal.
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.41-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
changed the title [-]Expense-More button is not aligned with the header in expense details in 1:1 chat[/-][+][Due for payment 2026-07-29] Expense-More button is not aligned with the header in expense details in 1:1 chat[/+]on Jul 22, 2026
@Beamanator The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]
@Beamanator The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]
Activity
applause-bot commentedon Jul 21, 2026
While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/b7c68c90e6e34f01899d5f5c517d5c5abae861082287b996ccf537f79555856d
melvin-bot commentedon Jul 21, 2026
Triggered auto assignment to @Beamanator (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Jul 21, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Jul 21, 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:
MelvinBot commentedon Jul 21, 2026
Proposal
Regression traced to #90403 — "Standardize Expense Report and Expense header with predictable button placement and carousel counter" (
thelullabyy, merged 2026-07-17). It's a line item in the 9.4.41-0StagingDeployCashand is the only staging-only PR that restructures the expense header layout, which matches "reproducible in staging, not production."What is the root cause of that problem?
That PR restructured
MoneyRequestHeader.tsxin two ways that shift the More button off the header baseline:styles.mtn1container — amarginTop: -4negative offset (spacing.ts:354) — that pulls the button up by 4px so it no longer lines up with the avatar/title.!shouldDisplayButtonsInSeparateLine && !statusBarProps, so when a status is shown the More button is no longer rendered inline in the header row; it's relocated into the newmtn1-shifted status/actions row below.Net effect: on the affected layout the More button renders in a row that's offset 4px upward (and/or relocated), so it's visually misaligned with the header.
Evidence & investigation details
9bffa9c), staging tip = 9.4.41-0 (98beeed); Standardize Expense Report and Expense header with predictable button placement and carousel counter #90403's header changes exist only in the staging range.MoneyRequestHeader.tsxin Standardize Expense Report and Expense header with predictable button placement and carousel counter #90403:{!shouldDisplayButtonsInSeparateLine && (...)}→{!shouldDisplayButtonsInSeparateLine && !statusBarProps && (...)}(L183)MoneyRequestHeaderActionsin<View style={styles.mtn1}>(L197-L204)flexRowwithstyles.mtn1that now also renders the More button inline (L205-L219)MoneyRequestHeaderSecondaryActions.tsxchange (Refactor: isolate allReportActions from getTrackExpenseActionableWhisper function #95745) only passes an extra arg todeleteTrackExpense(no layout impact); theButtonWithDropdownMenuAPI rename (ButtonWithDropdownMenu — align public API to composed conventions #95494) and Icon refactor (Move inline icon out of icon primitives #95286) already shipped in production 9.4.40.mtn1wrapper) or from the status-bar relocation. A quick visual check while toggling the RHP width will confirm which one.What changes do you think we should make in order to solve the problem?
Remove or correct the
styles.mtn1(marginTop: -4) offset added to the buttons/status rows inMoneyRequestHeader.tsx(and re-check the relocated More button placement) so the button re-aligns to the header baseline. Because this is a deploy blocker, the fastest safe path is a revert of #90403 (or a targeted follow-up by the author) if a clean fix isn't quick.This fix is entirely within the App repo.
No duplicate issues found in a quick scan.
Next Steps for Contributor+ team:
To accept:
@MelvinBot implement [this](https://github.com/Expensify/App/issues/96575)to create a draft PR.To refine:
@MelvinBot <your feedback>To reject: Explain why you are rejecting Melvin's proposal.
Beamanator commentedon Jul 21, 2026
Looks like the PR we're accusing was reverted in #96636, will ask for retest
Beamanator commentedon Jul 21, 2026
Hmm not fixed yet in v9.4.41-0, maybe that revert hasn't been CP'd yet
Beamanator commentedon Jul 21, 2026
Fixed in v9.4.41-1!
yuwenmemon commentedon Jul 21, 2026
This issue was fixed by the revert in #96636. @Expensify/applauseleads please retest.
melvin-bot commentedon Jul 22, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.41-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-07-29. 🎊
[-]Expense-More button is not aligned with the header in expense details in 1:1 chat[/-][+][Due for payment 2026-07-29] Expense-More button is not aligned with the header in expense details in 1:1 chat[/+]melvin-bot commentedon Jul 22, 2026
@Beamanator The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]
melvin-bot commentedon Jul 22, 2026
@Beamanator The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]