Skip to content

Expense - App crashes after moving expense, RHP does not close on web #66156

Closed

Description

@jponikarchuk

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.1.81-2
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: #64259
Email or phone of affected tester (no customers): sdmjoisdjsoinos1@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

  • Log in with a new account.
  1. Go to staging.expensify.com
  2. Go to workspace chat.
  3. Submit an expense to the workspace chat.
  4. Create an empty report via + > Create report.
  5. Open the expense report from Step 3.
  6. Tap Report field.
  7. Select another report (the empty report from Step 4).
  8. (Web only) Close the RHP and refresh the page.

Expected Result:

In Step 7, after selecting another report from the report list, RHP will close.
In Step 8, after refreshing the page, the moved expense will not return to the original report.

Actual Result:

In Step 7, after selecting another report from the report list, RHP does not close.
In Step 8, after refreshing the page, the moved expense returns to the original report.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

1.mp4
2.mp4

Logs.txt

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @joekaufmanexpensify

Activity

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

    @melvin-bot

    Triggered auto assignment to @joekaufmanexpensify (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 Jul 15, 2025

    @melvin-bot

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

  4. melvin-bot commented on Jul 15, 2025

    @melvin-bot

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

  5. github-actions commented on Jul 15, 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. rushatgabhane commented on Jul 15, 2025

    @rushatgabhane
    Member

    @BlameGPT please confirm the root cause

  7. 11 remaining items

  8. linhvovan29546 commented on Jul 16, 2025

    @linhvovan29546
    Contributor

    I noticed that we reverted the PR that was causing the crash. ^

  9. joekaufmanexpensify commented on Jul 16, 2025

    @joekaufmanexpensify
    Contributor

    Nice. I see the revert PR was merged, but doesn't look like it's on staging yet, so will leave this open a bit longer.

  10. luacmartins commented on Jul 16, 2025

    @luacmartins
    Contributor

    This is fixed in staging. Closing.

  11. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Jul 18, 2025
  12. changed the title [-]Expense - App crashes after moving expense, RHP does not close on web[/-] [+][Due for payment 2025-07-25] Expense - App crashes after moving expense, RHP does not close on web[/+] on Jul 18, 2025
  13. melvin-bot commented on Jul 18, 2025

    @melvin-bot

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

  14. melvin-bot commented on Jul 18, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.82-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 2025-07-25. 🎊

  15. melvin-bot commented on Jul 18, 2025

    @melvin-bot

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

  16. changed the title [-][Due for payment 2025-07-25] Expense - App crashes after moving expense, RHP does not close on web[/-] [+]Expense - App crashes after moving expense, RHP does not close on web[/+] on Jul 18, 2025
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.EngineeringWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions