Skip to content

[$250] Expense - After merging expenses, deleted expense can be opened by navigation arrow #77610

Closed

Description

@nlemma

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.78-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #75886
Email or phone of affected tester (no customers): idjsjodijsojsdon@gmail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: Mac 26.1 / Chrome
App Component: Money Requests

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Create two expenses.
  4. Open the expense report.
  5. Open any expense.
  6. Click More > Merge.
  7. Select the other expense from Step 3 > Continue.
  8. Select any details > Next.
  9. Click Merge expenses.
  10. Click navigation arrow on the top right.

Expected Result:

Navigation arrows on the top right should disappear after merging expenses as there is only one remaining expense in the report.

Actual Result:

Navigation arrows on the top right does not disappear after merging expenses when there is only one remaining expense in the report.
As a result, the deleted (merged) expense can be opened by the arrow which leads to a infinite loading page.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7028438_1765596353413.18.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021999886785376487245
  • Upwork Job ID: 1999886785376487245
  • Last Price Increase: 2025-12-13
Issue OwnerCurrent Issue Owner: @

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Dec 13, 2025
  2. melvin-bot commented on Dec 13, 2025

    @melvin-bot

    Triggered auto assignment to @JmillsExpensify (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. melvin-bot commented on Dec 13, 2025

    @melvin-bot

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

  4. melvin-bot commented on Dec 13, 2025

    @melvin-bot

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

  5. github-actions commented on Dec 13, 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.
  6. added
    ExternalAdded to denote the issue can be worked on by a contributor
    and removed on Dec 13, 2025
  7. 15 remaining items

  8. melvin-bot commented on Dec 15, 2025

    @melvin-bot

    Current assignee @carlosmiceli is eligible for the choreEngineerContributorManagement assigner, not assigning anyone new.

  9. m-natarajan commented on Dec 15, 2025

    @m-natarajan

    Not Repro, Windows 10/ Chrome, v9.2.78-1

    Repro.-.issue.77610.-.Web.mp4
  10. daledah commented on Dec 15, 2025

    @daledah
    Contributor

    @JmillsExpensify @carlosmiceli I think me and @DylanDylann would be eligible for partial payments because this issue is marked as External and i got C+ reviewed #77610 (comment) according to contributor docs:

    50% payment if the contributor wasn't assigned and
    The proposal was 🎀👀🎀 by the C+

    quoting from #62166 (comment)

    cc @DylanDylann for more insight

  11. daledah commented on Dec 17, 2025

    @daledah
    Contributor

    @JmillsExpensify could you please check this issue whenyou get a chance?

  12. JmillsExpensify commented on Dec 17, 2025

    @JmillsExpensify
    Contributor

    Payment summary:

  13. JmillsExpensify commented on Dec 17, 2025

    @JmillsExpensify
    Contributor

    Offer sent

  14. JmillsExpensify commented on Jan 20, 2026

    @JmillsExpensify
    Contributor

    All paid out.

  15. garrettmknight commented on Jan 20, 2026

    @garrettmknight
    Contributor
  16. JmillsExpensify commented on Jan 20, 2026

    @JmillsExpensify
    Contributor

    $125 approved for @DylanDylann

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.EngineeringExternalAdded to denote the issue can be worked on by a contributorHelp WantedApply this label when an issue is open to proposals by contributorsReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions