Skip to content

[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

Closed

Description

@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.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.
  1. Launch Expensify app.
  2. Go to Spend > Expenses.
  3. Tap Create expense.
  4. Create an expense.

Expected Result:

Expense row will show expense summary.

Actual Result:

Expense row is blank after creating expense on Spend tab.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7139709_1777340434032.Screen_Recording_20260428_093921_Expensify.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @Krishna2323

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    on Apr 28, 2026
  2. melvin-bot commented on Apr 28, 2026

    @melvin-bot

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

  3. melvin-bot commented on Apr 28, 2026

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  4. github-actions commented on Apr 28, 2026

    @github-actions
    Contributor

    👋 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.
  5. OSBotify commented on Apr 28, 2026

    @OSBotify
    Contributor

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

    Verification

    • Affected files: src/components/Search/SearchStaticList.tsx, src/components/Search/SearchList/ListItem/TransactionListItem.tsx, src/components/TransactionItemRow/index.tsx
    • Confirmation the PR modifies these files: PR Update table and row styles for mobile search pages #87742 directly modifies all three of these files with substantial layout changes to the narrow/mobile rendering path.

    Root Cause

    The PR restructured the mobile narrow-layout rendering of expense rows throughout the Search/Expenses page. There are two interacting issues:

    1. 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).

    2. 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).

  6. 11 remaining items

  7. melvin-bot commented on Apr 28, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

  8. IuliiaHerets commented on Apr 29, 2026

    @IuliiaHerets

    Not repro on Samsung Galaxy A40/Android 11/App/Build v9.3.64-9

    636c172a9e1a48ee500ac17cba74f222.mp4
  9. added and removed
    ReviewingHas a PR in review
    on Apr 30, 2026
  10. 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
  11. melvin-bot commented on Apr 30, 2026

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  12. melvin-bot commented on Apr 30, 2026

    @melvin-bot

    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:

    • @Krishna2323 requires payment through NewDot Manual Requests
    • @situchan requires payment through NewDot Manual Requests
  13. melvin-bot commented on Apr 30, 2026

    @melvin-bot

    @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]

  14. 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
  15. melvin-bot commented on May 4, 2026

    @melvin-bot

    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:

    • @Krishna2323 requires payment through NewDot Manual Requests
    • @situchan requires payment through NewDot Manual Requests
  16. melvin-bot commented on May 4, 2026

    @melvin-bot

    @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]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Engineering

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions