Skip to content

[Due for payment 2026-01-07] [Due for payment 2026-01-06] Android - Split - App crashes after splitting expense and deleting one split. #78526

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.2.87-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/test-runs/TR-2567/folder/13176791/41237172/1097941174
Email or phone of affected tester (no customers): ibellicotest+2250@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Critical User Impact
Device used: Motorola MotoG60 / Android 12 (Hybrid app)
App Component: Money Requests

Action Performed:

Prerequisite: Account has at least one workspace.

  1. Open the Expensify app.
  2. Open any workspace chat.
  3. Create a manual expense.
  4. Open the just created expense.
  5. Tap on "More" > "Split"
  6. Save the split amounts.
  7. Once redirected to report again, long tap and select any of the splits.
  8. Tap on dropdown menu and delete the split.
  9. Note that after the split is deleted, app crashes.

Expected Result:

User should be able to continue using the app properly after deleting a split.

Actual Result:

App crashes after splitting an expense and deleting one split.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7038605_1767014894760!log.txt

Bug7038605_1767014658583.Split_Crash.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @sonialiap

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 Dec 29, 2025
  2. melvin-bot commented on Dec 29, 2025

    @melvin-bot

    Triggered auto assignment to @sonialiap (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

  3. github-actions commented on Dec 29, 2025

    @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.
  4. melvin-bot commented on Dec 29, 2025

    @melvin-bot

    Triggered auto assignment to @deetergp (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  5. melvin-bot commented on Dec 29, 2025

    @melvin-bot

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

  6. 23 remaining items

  7. sonialiap commented on Jan 6, 2026

    @sonialiap
    Contributor

    Payment summary:
    @situchan $250 offer sent in upwork. Please complete the checklist

  8. situchan commented on Jan 6, 2026

    @situchan
    Contributor

    @sonialiap I was not involved in original PR so no regression penalty.

  9. m-natarajan commented on Jan 6, 2026

    @m-natarajan

    Not reproduce, Xiaomi Redmi Note 10 / Android 12, App 9.2.94-0

    Screenrecorder-2026-01-06-21-10-21-184.mp4
  10. melvin-bot commented on Jan 7, 2026

    @melvin-bot

    Payment Summary

    Upwork Job

    • ROLE: @situchan paid $(AMOUNT) via Upwork (LINK)

    BugZero Checklist (@sonialiap)

    • (if NewFeature) I have created a PR for any necessary HelpDot updates, or I confirmed no updates are necessary.
    • I have verified the correct assignees and roles are listed above and updated the necessary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants//hired)
    • I have verified the PR was not reverted
    • I have applied any discounts due to bugs/regressions introduced by this PR
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  11. melvin-bot commented on Jan 9, 2026

    @melvin-bot

    @sonialiap Whoops! This issue is 2 days overdue. Let's get this updated quick!

  12. sonialiap commented on Jan 12, 2026

    @sonialiap
    Contributor

    @situchan sorry, I misunderstood the issue! Updated the payment summary to $250 and issued payment in upwork for that amount

  13. sonialiap commented on Jan 12, 2026

    @sonialiap
    Contributor

    @situchan could you complete the checklist?

  14. situchan commented on Jan 12, 2026

    @situchan
    Contributor

    BugZero Checklist:

    • [Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

      Link to comment: Fix - Make it more apparent in the expense chat carousel view when expenses are added to a report #74838 (comment)

    • [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.

      Link to discussion: N/A

    • [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

    • [BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.

      Link to issue:

    Regression Test Proposal

    Seems exists already https://test-management.browserstack.com/projects/2219752/test-runs/TR-2567/folder/13176791/41237172/1097941174

  15. sonialiap commented on Jan 13, 2026

    @sonialiap
    Contributor

    Thanks!

  16. added
    ReviewingHas a PR in review
    and removed on Feb 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.EngineeringReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions