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-05-11] [Due for payment 2026-05-07] Android - Spend - Expense row is blank after creating expense on Spend tab #89046
Version Number: 9.3.63-1 Reproducible in staging?: Yes Reproducible in production?: No If this was caught during regression testing, add the test name, ID and link from BrowserStack:#87742 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: Samsung Galaxy S25 FE / Android 16 App Component: Search
Action Performed:
Precondition:
Account has no expenses.
Have a workspace.
Launch Expensify app.
Go to Spend > Expenses.
Tap Create expense.
Create an expense.
Expected Result:
Expense row will show expense summary.
Actual Result:
Expense row is blank after creating expense on Spend tab.
👋 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.
Classification: Frontend bug Causing PR: #87742 - "Update table and row styles for mobile search pages" by @Krishna2323 (High confidence) Related Issues: #87460
Recommendation: REVERT
PR #87742 significantly overhauled the mobile layout of expense rows in the Search/Expenses view and is the clear cause of blank rows after expense creation on Android. The bug is staging-only, aligns with the PR's merge date (April 27, 2026), and the melvin-bot independently identified this same PR.
Assigned: @Krishna2323 (PR author), @JS00001, @luacmartins, @shawnborton, @situchan (approving reviewers) Labels: DeployBlockerCash kept (frontend App PR caused the bug). DeployBlocker removed (this is not a backend issue).
Detailed Analysis
Evidence
The bug occurs on the Spend > Expenses tab in Android narrow layout immediately after creating an expense — the newly created expense row renders blank (no merchant, amount, date, or receipt shown).
PR Update table and row styles for mobile search pages #87742 ("Update table and row styles for mobile search pages") was merged on 2026-04-27 and is present in the StagingDeployCash checklist (entry 175 in chronological order). The bug is staging-only and not reproducible in production, confirming the regression was introduced by this staging PR.
melvin-bot automatically assigned this PR to the deploy blocker, independently corroborating the diagnosis.
The PR restructured the mobile narrow-layout rendering of expense rows throughout the Search/Expenses page. There are two interacting issues:
SearchStaticList.tsx (the optimistic fast-render list shown immediately after creating an expense): The TransactionItemRow is called with style={[styles.p3, styles.pv2, styles.p0, styles.pt3]}. The styles.p0 entry overrides styles.p3 and zeroes out all padding, then styles.pt3 restores only top padding. This collapses the content area of the narrow-layout row, making content invisible or zero-height for newly created transactions (which lack some data fields and depend on proper padding to be visible).
TransactionListItem.tsx: The PR changed the TransactionItemRow style to [styles.p3, styles.pv2, shouldUseNarrowLayout ? [styles.p0, styles.pt3] : ...] — the same p0 override problem applies in the full list rendering path on narrow screens.
These style changes effectively strip horizontal and vertical padding from the transaction row's inner content container on mobile, causing the expense summary content to render with no visible area in certain states (e.g., freshly created expense with minimal populated fields).
changed the title [-]Android - Spend - Expense row is blank after creating expense on Spend tab[/-][+][Due for payment 2026-05-07] Android - Spend - Expense row is blank after creating expense on Spend tab[/+]on Apr 30, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.64-31 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@Krishna2323 / @situchan 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]
changed the title [-][Due for payment 2026-05-07] Android - Spend - Expense row is blank after creating expense on Spend tab[/-][+][Due for payment 2026-05-11] [Due for payment 2026-05-07] Android - Spend - Expense row is blank after creating expense on Spend tab[/+]on May 4, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.65-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@Krishna2323 / @situchan 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]
Activity
melvin-bot commentedon Apr 28, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #87742
melvin-bot commentedon Apr 28, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Apr 28, 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:
OSBotify commentedon Apr 28, 2026
Investigation Summary
Classification: Frontend bug
Causing PR: #87742 - "Update table and row styles for mobile search pages" by @Krishna2323 (High confidence)
Related Issues: #87460
Recommendation: REVERT
PR #87742 significantly overhauled the mobile layout of expense rows in the Search/Expenses view and is the clear cause of blank rows after expense creation on Android. The bug is staging-only, aligns with the PR's merge date (April 27, 2026), and the melvin-bot independently identified this same PR.
Assigned: @Krishna2323 (PR author), @JS00001, @luacmartins, @shawnborton, @situchan (approving reviewers)
Labels:
DeployBlockerCashkept (frontend App PR caused the bug).DeployBlockerremoved (this is not a backend issue).Detailed Analysis
Evidence
Verification
src/components/Search/SearchStaticList.tsx,src/components/Search/SearchList/ListItem/TransactionListItem.tsx,src/components/TransactionItemRow/index.tsxRoot Cause
The PR restructured the mobile narrow-layout rendering of expense rows throughout the Search/Expenses page. There are two interacting issues:
SearchStaticList.tsx(the optimistic fast-render list shown immediately after creating an expense): TheTransactionItemRowis called withstyle={[styles.p3, styles.pv2, styles.p0, styles.pt3]}. Thestyles.p0entry overridesstyles.p3and zeroes out all padding, thenstyles.pt3restores only top padding. This collapses the content area of the narrow-layout row, making content invisible or zero-height for newly created transactions (which lack some data fields and depend on proper padding to be visible).TransactionListItem.tsx: The PR changed theTransactionItemRowstyle to[styles.p3, styles.pv2, shouldUseNarrowLayout ? [styles.p0, styles.pt3] : ...]— the samep0override problem applies in the full list rendering path on narrow screens.These style changes effectively strip horizontal and vertical padding from the transaction row's inner content container on mobile, causing the expense summary content to render with no visible area in certain states (e.g., freshly created expense with minimal populated fields).
11 remaining items
melvin-bot commentedon Apr 28, 2026
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
IuliiaHerets commentedon Apr 29, 2026
Not repro on Samsung Galaxy A40/Android 11/App/Build v9.3.64-9
636c172a9e1a48ee500ac17cba74f222.mp4
[-]Android - Spend - Expense row is blank after creating expense on Spend tab[/-][+][Due for payment 2026-05-07] Android - Spend - Expense row is blank after creating expense on Spend tab[/+]melvin-bot commentedon Apr 30, 2026
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Apr 30, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.64-31 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-05-07. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Apr 30, 2026
@Krishna2323 / @situchan 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]
[-][Due for payment 2026-05-07] Android - Spend - Expense row is blank after creating expense on Spend tab[/-][+][Due for payment 2026-05-11] [Due for payment 2026-05-07] Android - Spend - Expense row is blank after creating expense on Spend tab[/+]melvin-bot commentedon May 4, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.65-6 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-05-11. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon May 4, 2026
@Krishna2323 / @situchan 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]