Skip to content

[Due for payment 2026-05-13] [Due for payment 2026-05-12] Android - Spend - Created expense is blank #89523

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.66-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: #88296
Email or phone of affected tester (no customers): jsosdjosjndosjodnjno@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. Create a new account.
  3. Go to Home tab.
  4. Open FAB > Create expense > Manual.
  5. Create a manual expense to self DM.

Expected Result:

The created expense in Expenses list will not be blank.

Actual Result:

The created expense in Expenses list is blank.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7144272_1777908055070.Screen_Recording_20260504_222603_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.
    on May 4, 2026
  2. melvin-bot commented on May 4, 2026

    @melvin-bot

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

  3. melvin-bot commented on May 4, 2026

    @melvin-bot

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

  4. JS00001 commented on May 4, 2026

    @JS00001
    Contributor

    @Krishna2323 can you take a look please?

  5. OSBotify commented on May 4, 2026

    @OSBotify
    Contributor

    Investigation Summary

    Classification: Frontend bug
    Causing PR: #88296 - "Update report details view to use compact desktop table styles" by @Krishna2323 (High confidence)
    Related Issues: None

    Recommendation: REVERT

    PR #88296 was the last App PR to modify MoneyRequestReportTransactionList.tsx and MoneyRequestReportTransactionItem.tsx before this bug was introduced. A PR comment from @mitarachim on the PR explicitly states "Deploy Blocker #89523 was identified to be related to this PR."

    Assigned: @Krishna2323 (PR author), @JS00001, @luacmartins, @situchan (approving reviewers)
    Labels: DeployBlockerCash kept (frontend/App fix required). DeployBlocker removed (no backend involvement).

    Detailed Analysis

    Evidence

    Verification

    • Affected file: src/components/MoneyRequestReportView/MoneyRequestReportTransactionList.tsx
    • PR Update report details view to use compact desktop table styles #88296 modifies: MoneyRequestReportTransactionList.tsx, MoneyRequestReportTransactionItem.tsx, MoneyRequestReportGroupHeader.tsx, MoneyRequestReportTableHeader.tsx, TransactionItemRow/index.tsx, styles/variables.ts
    • The modified MoneyRequestReportTransactionList.tsx is the direct parent that renders each transaction row in the Expenses list.
    • The bug only manifests on Android Native (narrow layout), and the PR's changes span both narrow and wide layout code paths.

    Root Cause

    The PR refactors how transaction items are rendered by extracting a renderTransactionItem helper function (not a proper memoized component or useCallback-wrapped function). This means every re-render creates a new function reference. Additionally, the PR modifies how animatedHighlightStyle is applied to newly created transactions — the borderRadius was swapped (shouldUseNarrowLayout ? variables.componentBorderRadius : 0 instead of the prior shouldUseNarrowLayout ? 0 : variables.componentBorderRadius), and the OfflineWithFeedback style was changed to conditionally apply searchTableBottomRadius only for desktop layout. These combined changes appear to break rendering on Android (narrow layout) for newly created expenses, causing the expense row to appear blank after creation.

  6. removed
    DeployBlockerIndicates it should block deploying the API
    on May 4, 2026
  7. 3 remaining items

  8. m-natarajan commented on May 5, 2026

    @m-natarajan

    Issue no longer reproducible on build 9.3.66-5. Retested on Motorola Moto G60 - Android 12

    screen-20260504-214009.mp4
  9. added and removed
    ReviewingHas a PR in review
    on May 5, 2026
  10. changed the title [-]Android - Spend - Created expense is blank[/-] [+][Due for payment 2026-05-12] Android - Spend - Created expense is blank[/+] on May 5, 2026
  11. melvin-bot commented on May 5, 2026

    @melvin-bot

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

  12. melvin-bot commented on May 5, 2026

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.66-7 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-12. 🎊

    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 May 5, 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-12] Android - Spend - Created expense is blank[/-] [+][Due for payment 2026-05-13] [Due for payment 2026-05-12] Android - Spend - Created expense is blank[/+] on May 6, 2026
  15. melvin-bot commented on May 6, 2026

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.67-13 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-13. 🎊

    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 6, 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