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-21] [$250] The “There’s a report awaiting action” UI is pushing other content out, leaving blank space displayed. #89528
Version Number: 9.3.66-1 Reproducible in staging?: Y Reproducible in production?: N (Debug option N/A) If this was caught during regression testing, add the test name, ID and link from BrowserStack: Email or phone of affected tester (no customers): Logs:https://stackoverflow.com/c/expensify/questions/4856 Expensify/Expensify Issue URL: Issue reported by:@quinthar@blimpich@brianlee-expensify Slack conversation (hyperlinked to channel name): #Expensify Bugs#quality
Action Performed:
Precondition:
Have at least a report with GBR or RBR in LHN
Go to staging.new.expensify.com
Press CMD+D
Enable Debug mode
Navigate to LHN
Expected Result:
LHN menu displayed without any visual issues
Actual Result:
"There's a report awaiting action" UI is pushing LHN and blank space displayed
Workaround:
Unknown
Platforms:
Select the officially supported platforms where the issue was reproduced:
The DebugTabView banner is rendered as a sibling before the tab bar container inside NavigationTabBar. On narrow/desktop layouts, the parent TabNavigatorBar uses a negative marginTop of -(bottomTabHeight + safeAreaPaddingBottom) via getTabBarNarrowStyle to overlay the tab bar on content with zero layout impact. This margin only accounts for the fixed 72px tab bar height — it does not account for the extra height added by DebugTabView. The uncompensated height pushes the LHN content and creates the visible blank space.
On wide layout, a similar issue occurs: DebugTabView is a sibling of leftNavigationTabBarContainer (which has height: '100%') inside an overflowHidden parent, causing layout displacement.
What changes do you think we should make in order to solve the problem?
Move the DebugTabView to use absolute positioning so it overlays on top of the tab bar instead of participating in the normal layout flow. In NavigationTabBar/index.tsx, render the DebugTabView inside a wrapper with position: 'absolute' anchored above the tab bar (e.g., bottom: 100%, left: 0, right: 0). This way it does not add any height to the tab bar container and will not affect the negative margin calculation or push any content.
What alternative solutions did you explore? (Optional)
An alternative would be to dynamically measure the DebugTabView height and add it to the negative marginTop in getTabBarNarrowStyle. However, this is fragile — it couples the margin calculation to a dynamic element's height and would need different handling for wide vs narrow layouts. Absolute positioning is simpler and avoids affecting the layout math entirely.
Investigation details
Key code locations:
DebugTabView.tsx:168-185 — the banner component with p3 padding, flexRow layout, no absolute positioning
Data flow: Debug mode enabled → NavigationTabBar renders DebugTabView above tab bar → banner takes ~40-50px of layout space → narrow layout's fixed negative margin (-72px) doesn't compensate → content pushed / blank space appears.
Next Steps for Contributor+ team: Reply with @MelvinBot implement this to create a draft PR, @MelvinBot <your feedback> to refine this analysis, or explain why you are rejecting Melvin's proposal.
Please re-state the problem that we are trying to solve in this issue.
When debug mode is enabled and there is a report with GBR or RBR in the LHN, the "There's a report awaiting action" debug banner appears above the navigation tab bar but pushes LHN content upward, leaving blank space at the bottom of the list.
What is the root cause of that problem?
NavigationTabBar renders DebugTabView and the actual tab items as siblings in a React fragment. On narrow layout, TabNavigatorBar wraps the entire NavigationTabBar with a negative marginTop (via getTabBarNarrowStyle) that is sized to exactly bottomTabHeight + safeAreaPaddingBottom. This offset is hardcoded to the height of the tab items alone — it does not account for the additional height of the DebugTabView banner. When the banner is present, the overall fragment is taller than bottomTabHeight, but the negative margin only pulls up by the tab bar height, so the extra banner height remains as unreserved vertical space that displaces the LHN list content above it.
On wide layout the situation is similar: the <View style={styles.overflowHidden}> container in TabNavigatorBar grows to include both DebugTabView and leftNavigationTabBarContainer, but leftNavigationTabBarContainer has height: '100%' relative to its parent. Adding the banner as a sibling changes the flow of the containing column, pushing the tab container below its expected position and causing a layout gap.
What changes do you think we should make in order to solve the problem?
The fix should ensure the debug banner does not contribute to the document flow in a way that displaces surrounding content. The cleanest approach is to render DebugTabView with position: 'absolute' and anchored to the top of its containing View (with a negative top offset equal to the banner's height, or using bottom: '100%'). This way the banner floats above the tab bar without adding any height to the tab bar's layout footprint, so the negative marginTop trick in TabNavigatorBar continues to work as intended for both the narrow and wide layouts.
Concretely, in DebugTabView.tsx, the root <View> should receive position: 'absolute', bottom: '100%' (or equivalently top with a negative offset computed from the banner's measured height using onLayout), and width: '100%' so it spans the full tab bar width and rises above it without occupying any space in the normal layout flow. The parent views in NavigationTabBar/index.tsx that currently wrap DebugTabView alongside the tab items may need overflow: 'visible' (narrow layout already has this via getTabBarNarrowStyle) to prevent clipping the absolutely-positioned banner.
What alternative solutions did you explore? (Optional)
An alternative would be to make getTabBarNarrowStyle dynamically measure and account for the banner height by passing it as a parameter, adjusting the negative marginTop to -(bottomTabHeight + debugBannerHeight + safeAreaPaddingBottom). This would work on narrow layout but requires wiring onLayout measurements through multiple layers. The absolute-positioning approach is simpler, self-contained within DebugTabView, and naturally handles both narrow and wide layouts without touching the margin calculations.
changed the title [-]The “There’s a report awaiting action” UI is pushing other content out, leaving blank space displayed.[/-][+][$250] The “There’s a report awaiting action” UI is pushing other content out, leaving blank space displayed.[/+]on May 4, 2026
Because the wide tab bar wrapper currently uses the rendered children to determine its layout footprint, the banner’s text/button row makes the whole tab bar area wider than the 64px rail, pushing the LHN to the right and leaving the blank space shown in the screenshot:
The narrow wrapper intentionally offsets only bottomTabHeight + safeAreaPaddingBottom, so the extra DebugTabView height is not part of that layout calculation:
What changes do you think we should make in order to solve the problem?
Render DebugTabView out of normal layout flow so it can still be visible in debug mode without changing the tab bar’s measured width or height.
Required changes:
Add an optional style prop to DebugTabView and apply it to the root view.
For wide layout, render the banner as position: absolute at top: 0, left: 0.
For narrow layout, render the banner as position: absolute with bottom: '100%', left: 0, and right: 0, so it sits above the bottom tab bar.
Make the tab bar wrapper position: relative so the absolute banner is anchored to the tab bar wrapper.
Use overflowVisible for the wide tab bar wrapper so the absolute debug banner can paint outside the 64px rail without increasing the rail’s layout width.
Tests that should be added:
Update the NavigationTabBar UI tests to verify DebugTabView is rendered with absolute positioning when debug mode is enabled.
Add coverage for the wide-layout render path so the debug banner can render without changing the tab bar container’s normal layout footprint.
The existing proposals correctly identify that the banner must not participate in normal layout flow. The missing detail is that wide and narrow layouts need different anchors: bottom: '100%' is right for the bottom tab bar, but the wide vertical rail needs a top/left absolute anchor plus visible overflow on the wide wrapper. That is why this proposal keeps the same root-cause fix but makes the layout handling explicit for both tab bar orientations.
What alternative solutions did you explore? (Optional)
⚠️@nabi-ebrahimi Thanks for your proposal. Please update it to follow the proposal template, as proposals are only reviewed if they follow that format (note the mandatory sections).
changed the title [-][$250] The “There’s a report awaiting action” UI is pushing other content out, leaving blank space displayed.[/-][+][Due for payment 2026-07-21] [$250] The “There’s a report awaiting action” UI is pushing other content out, leaving blank space displayed.[/+]on Jul 21, 2026
@MelvinBot payment-review
MODE: <closed-no-pr | payment-due>
JOB_PRICE: 250 # override if the title bounty differs
Run the C+ payment framework for this issue and post a structured, evidence-cited
recommendation. Rules:
Suggest only — never auto-pay. A human confirms.
Every point / adjustment MUST cite a specific comment permalink. No permalink → no point.
Round every %→$ result up to the nearest $25: amount = ceil((pct × JOB_PRICE) / 25) × 25.
If MODE = closed-no-pr:
Run the eligibility gate; if it fails, or the token-saving skip-gate trips
(<~8 non-bot comments AND no C+ engagement markers, or closed <48h, or spam/invalid),
return "$0 — skipped" with a one-line reason and STOP.
Bucket the close reason (A/B/C), score the 5 factors 0–10 with permalinks.
Payout = 25% of JOB_PRICE if score ≥ 8, else $0.
If MODE = payment-due:
Start at 100% of JOB_PRICE.
Decreases: for any regression, read the offending PR + issue and decide if it's
truly attributable to this author/reviewer. If yes, −50% per verified regression.
If fault is unclear, DO NOT deduct — flag for human review.
Increases: evaluate the C+ increase framework (multiple PRs, additional fixes,
scope expansion, core-flow changes, deploy blockers audited, performance,
test coverage, files touched), each backed by a permalink.
Output: recommended $ amount, per-line reasoning with permalinks, confidence
(High/Med/Low), and any manual-review flags.
No increases. The only additional PRs on this job (#91856, #93078) were regression cleanup on this work's own output, not new scope, extra fixes, performance, or added test coverage — so the C+ increase framework awards nothing here.
Confidence: Medium
The recommendation ($125) is high-confidence because it matches the reviewer's own assessment and there is a documented deploy-blocker regression tied to the DebugTabView work. Confidence is held at Medium only on the strict framework attribution, because of the item flagged below.
Activity
MelvinBot commentedon May 4, 2026
Proposal
What is the root cause of that problem?
The
DebugTabViewbanner is rendered as a sibling before the tab bar container insideNavigationTabBar. On narrow/desktop layouts, the parentTabNavigatorBaruses a negativemarginTopof-(bottomTabHeight + safeAreaPaddingBottom)viagetTabBarNarrowStyleto overlay the tab bar on content with zero layout impact. This margin only accounts for the fixed 72px tab bar height — it does not account for the extra height added byDebugTabView. The uncompensated height pushes the LHN content and creates the visible blank space.On wide layout, a similar issue occurs:
DebugTabViewis a sibling ofleftNavigationTabBarContainer(which hasheight: '100%') inside anoverflowHiddenparent, causing layout displacement.What changes do you think we should make in order to solve the problem?
Move the
DebugTabViewto use absolute positioning so it overlays on top of the tab bar instead of participating in the normal layout flow. InNavigationTabBar/index.tsx, render theDebugTabViewinside a wrapper withposition: 'absolute'anchored above the tab bar (e.g.,bottom: 100%,left: 0,right: 0). This way it does not add any height to the tab bar container and will not affect the negative margin calculation or push any content.What alternative solutions did you explore? (Optional)
An alternative would be to dynamically measure the
DebugTabViewheight and add it to the negativemarginTopingetTabBarNarrowStyle. However, this is fragile — it couples the margin calculation to a dynamic element's height and would need different handling for wide vs narrow layouts. Absolute positioning is simpler and avoids affecting the layout math entirely.Investigation details
Key code locations:
DebugTabView.tsx:168-185— the banner component withp3padding,flexRowlayout, no absolute positioningNavigationTabBar/index.tsx:222-227— narrow layout: DebugTabView rendered before the tab barNavigationTabBar/index.tsx:136-143— wide layout: DebugTabView rendered before the left nav tab bargetTabBarNarrowStyle— negative margin only accounts forbottomTabHeight(72px)TabNavigatorBar.tsx:115-119— wide layout parent withoverflowHiddenData flow: Debug mode enabled →
NavigationTabBarrendersDebugTabViewabove tab bar → banner takes ~40-50px of layout space → narrow layout's fixed negative margin (-72px) doesn't compensate → content pushed / blank space appears.Next Steps for Contributor+ team: Reply with
@MelvinBot implement thisto create a draft PR,@MelvinBot <your feedback>to refine this analysis, or explain why you are rejecting Melvin's proposal.melvin-bot commentedon May 4, 2026
Triggered auto assignment to Contributor-plus team member for initial proposal review - @abzokhattab (
External)MobileMage commentedon May 4, 2026
Proposal
Please re-state the problem that we are trying to solve in this issue.
When debug mode is enabled and there is a report with GBR or RBR in the LHN, the "There's a report awaiting action" debug banner appears above the navigation tab bar but pushes LHN content upward, leaving blank space at the bottom of the list.
What is the root cause of that problem?
NavigationTabBarrendersDebugTabViewand the actual tab items as siblings in a React fragment. On narrow layout,TabNavigatorBarwraps the entireNavigationTabBarwith a negativemarginTop(viagetTabBarNarrowStyle) that is sized to exactlybottomTabHeight + safeAreaPaddingBottom. This offset is hardcoded to the height of the tab items alone — it does not account for the additional height of theDebugTabViewbanner. When the banner is present, the overall fragment is taller thanbottomTabHeight, but the negative margin only pulls up by the tab bar height, so the extra banner height remains as unreserved vertical space that displaces the LHN list content above it.On wide layout the situation is similar: the
<View style={styles.overflowHidden}>container inTabNavigatorBargrows to include bothDebugTabViewandleftNavigationTabBarContainer, butleftNavigationTabBarContainerhasheight: '100%'relative to its parent. Adding the banner as a sibling changes the flow of the containing column, pushing the tab container below its expected position and causing a layout gap.App/src/libs/Navigation/AppNavigator/Navigators/TabNavigatorBar.tsx
Lines 100 to 112 in bdce78b
What changes do you think we should make in order to solve the problem?
The fix should ensure the debug banner does not contribute to the document flow in a way that displaces surrounding content. The cleanest approach is to render
DebugTabViewwithposition: 'absolute'and anchored to the top of its containingView(with a negativetopoffset equal to the banner's height, or usingbottom: '100%'). This way the banner floats above the tab bar without adding any height to the tab bar's layout footprint, so the negativemarginToptrick inTabNavigatorBarcontinues to work as intended for both the narrow and wide layouts.Concretely, in
DebugTabView.tsx, the root<View>should receiveposition: 'absolute',bottom: '100%'(or equivalentlytopwith a negative offset computed from the banner's measured height usingonLayout), andwidth: '100%'so it spans the full tab bar width and rises above it without occupying any space in the normal layout flow. The parent views inNavigationTabBar/index.tsxthat currently wrapDebugTabViewalongside the tab items may needoverflow: 'visible'(narrow layout already has this viagetTabBarNarrowStyle) to prevent clipping the absolutely-positioned banner.App/src/components/Navigation/DebugTabView.tsx
Lines 168 to 186 in bdce78b
What alternative solutions did you explore? (Optional)
An alternative would be to make
getTabBarNarrowStyledynamically measure and account for the banner height by passing it as a parameter, adjusting the negativemarginTopto-(bottomTabHeight + debugBannerHeight + safeAreaPaddingBottom). This would work on narrow layout but requires wiringonLayoutmeasurements through multiple layers. The absolute-positioning approach is simpler, self-contained withinDebugTabView, and naturally handles both narrow and wide layouts without touching the margin calculations.[-]The “There’s a report awaiting action” UI is pushing other content out, leaving blank space displayed.[/-][+][$250] The “There’s a report awaiting action” UI is pushing other content out, leaving blank space displayed.[/+]melvin-bot commentedon May 4, 2026
Job added to Upwork: https://www.upwork.com/jobs/~022051335767738333893
nabi-ebrahimi commentedon May 4, 2026
Proposal
What is the root cause of that problem?
DebugTabViewis rendered as a normal-flow sibling of the actual navigation tab bar in both layouts.On wide layout,
NavigationTabBarrendersDebugTabViewbeforeleftNavigationTabBarContainer:App/src/components/Navigation/NavigationTabBar/index.tsx
Lines 135 to 147 in 29928fd
The vertical tab bar itself has a fixed
widthbut the debug banner does not:App/src/styles/index.ts
Lines 719 to 725 in 29928fd
Because the wide tab bar wrapper currently uses the rendered children to determine its layout footprint, the banner’s text/button row makes the whole tab bar area wider than the 64px rail, pushing the LHN to the right and leaving the blank space shown in the screenshot:
App/src/libs/Navigation/AppNavigator/Navigators/TabNavigatorBar.tsx
Lines 115 to 118 in 29928fd
On narrow layout, the same component is rendered before the bottom tab bar:
App/src/components/Navigation/NavigationTabBar/index.tsx
Lines 220 to 230 in 29928fd
The narrow wrapper intentionally offsets only
bottomTabHeight + safeAreaPaddingBottom, so the extraDebugTabViewheight is not part of that layout calculation:App/src/styles/utils/index.ts
Lines 2301 to 2306 in 29928fd
What changes do you think we should make in order to solve the problem?
Render
DebugTabViewout of normal layout flow so it can still be visible in debug mode without changing the tab bar’s measured width or height.Required changes:
styleprop toDebugTabViewand apply it to the root view.position: absoluteattop: 0,left: 0.position: absolutewithbottom: '100%',left: 0, andright: 0, so it sits above the bottom tab bar.position: relativeso the absolute banner is anchored to the tab bar wrapper.overflowVisiblefor the wide tab bar wrapper so the absolute debug banner can paint outside the 64px rail without increasing the rail’s layout width.Tests that should be added:
NavigationTabBarUI tests to verifyDebugTabViewis rendered with absolute positioning when debug mode is enabled.The existing proposals correctly identify that the banner must not participate in normal layout flow. The missing detail is that wide and narrow layouts need different anchors:
bottom: '100%'is right for the bottom tab bar, but the wide vertical rail needs a top/left absolute anchor plus visible overflow on the wide wrapper. That is why this proposal keeps the same root-cause fix but makes the layout handling explicit for both tab bar orientations.What alternative solutions did you explore? (Optional)
Fixed Demo:
Screencast.From.2026-05-05.00-13-27.mp4
github-actions commentedon May 4, 2026
42 remaining items
melvin-bot commentedon Jul 21, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)[-][$250] The “There’s a report awaiting action” UI is pushing other content out, leaving blank space displayed.[/-][+][Due for payment 2026-07-21] [$250] The “There’s a report awaiting action” UI is pushing other content out, leaving blank space displayed.[/+]melvin-bot commentedon Jul 21, 2026
Payment Summary
Upwork Job
BugZero Checklist (@mallenexpensify)
mallenexpensify commentedon Jul 23, 2026
@MelvinBot payment-review
MODE: <closed-no-pr | payment-due>
JOB_PRICE: 250 # override if the title bounty differs
Run the C+ payment framework for this issue and post a structured, evidence-cited
recommendation. Rules:
If MODE = closed-no-pr:
(<~8 non-bot comments AND no C+ engagement markers, or closed <48h, or spam/invalid),
return "$0 — skipped" with a one-line reason and STOP.
If MODE = payment-due:
truly attributable to this author/reviewer. If yes, −50% per verified regression.
If fault is unclear, DO NOT deduct — flag for human review.
scope expansion, core-flow changes, deploy blockers audited, performance,
test coverage, files touched), each backed by a permalink.
Output: recommended $ amount, per-line reasoning with permalinks, confidence
(High/Med/Low), and any manual-review flags.
MelvinBot commentedon Jul 23, 2026
💰 Payment Review — C+ (payment-due)
Recommended:
$125(50% of $250) — matches the C+'s own self-assessment. Suggestion only; a human confirms.Being paid:
abzokhattab(reviewer) — owed $250 via NewDot per the Payment Summary.Calculation
Reasoning (per line, with permalinks)
Base $250 — Reviewer role confirmed in the Payment Summary.
abzokhattabreviewed/approved the main fix PR #89893.−50% — one verified regression (deploy blockers). The tab-bar/
DebugTabViewwork introduced deploy blockers that had to be cleaned up in follow-ups tracked on this issue (borys3kk: "resolving some follow-ups", follow-ups merged). The fix PR #93078 — "Fix fullScreenBlockingView bleeding over navigationTabBar (deploy blockers after debugTabView update)" resolved regression issues [Due for payment 2026-06-29] LHN - Left navigation bar is replaced by back button after returning to home page #92327 and [Due for payment 2026-06-22] Home - Left navigation bar disappears after completing onboarding #92409 (left navigation bar disappears / replaced by back button).abzokhattabwas the reviewer across this chain and explicitly acknowledged the regression and proposed the discount: "I think we had a regression here, so the payment should be 125$". Counted as one regression event (single root cause — thefullScreenBlockingView/zIndex behavior — with a single fix PR), so −50%, not −100%.No increases. The only additional PRs on this job (#91856, #93078) were regression cleanup on this work's own output, not new scope, extra fixes, performance, or added test coverage — so the C+ increase framework awards nothing here.
Confidence: Medium
The recommendation ($125) is high-confidence because it matches the reviewer's own assessment and there is a documented deploy-blocker regression tied to the
DebugTabViewwork. Confidence is held at Medium only on the strict framework attribution, because of the item flagged below.🚩 Manual-review flags
Awaiting Payment. Ifabzokhattabis already being penalized/handled for these regressions on those jobs, applying −50% here as well would double-count. Please confirm the discount is applied once.cc @mallenexpensify
mallenexpensify commentedon Jul 23, 2026
Payment Summary
Contributor+: @abzokhattab due $125 via NewDot
Think we're good to close
quinthar commentedon Aug 19, 2026
Approved $125 to @abzokhattab