Skip to content

[Due for payment 2025-10-03] [$250] Expense - RHP back button opens previous report instead of closing RHP #71137

Closed

Description

@lanitochka17

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.17-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: #69221
Email or phone of affected tester (no customers): sosdpsosnjojs@gmail.com
Issue reported by: Applause - Internal Team

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 the first expense
  6. Click arrow next button
  7. Click RHP back button

Expected Result:

RHP will close

Actual Result:

RHP back button reopens the first expense

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop
Platforms Tested: On which of our officially supported platforms was this issue tested:
  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence
Bug6953952_1758666054610.Screen_Recording_2025-09-24_at_06.18.50.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021970924697593816224
  • Upwork Job ID: 1970924697593816224
  • Last Price Increase: 2025-09-24
Issue OwnerCurrent Issue Owner: @abdulrahuman5196

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Sep 23, 2025
  2. melvin-bot commented on Sep 23, 2025

    @melvin-bot

    Triggered auto assignment to @CortneyOfstad (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 Sep 23, 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 Sep 23, 2025

    @melvin-bot

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

  5. melvin-bot commented on Sep 23, 2025

    @melvin-bot

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

  6. roryabraham commented on Sep 24, 2025

    @roryabraham
    Contributor

    This was introduced in #69221. Discussing here whether we should revert or demote

  7. added
    ExternalAdded to denote the issue can be worked on by a contributor
    Help WantedApply this label when an issue is open to proposals by contributors
    on Sep 24, 2025
  8. 29 remaining items

  9. self-assigned this
    on Sep 24, 2025
  10. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Sep 24, 2025
  11. m-natarajan commented on Sep 24, 2025

    @m-natarajan

    Not repro Windows 11 Chrome App version v9.2.17-6

    Repro_71137_Webb.mp4
  12. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Sep 26, 2025
  13. changed the title [-][$250] Expense - RHP back button opens previous report instead of closing RHP[/-] [+][Due for payment 2025-10-03] [$250] Expense - RHP back button opens previous report instead of closing RHP[/+] on Sep 26, 2025
  14. melvin-bot commented on Sep 26, 2025

    @melvin-bot

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

  15. melvin-bot commented on Sep 26, 2025

    @melvin-bot

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

    For reference, here are some details about the assignees on this issue:

  16. melvin-bot commented on Sep 26, 2025

    @melvin-bot

    @abdulrahuman5196 / @ishpaul777 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]

  17. ishpaul777 commented on Sep 26, 2025

    @ishpaul777
    Contributor

    no payment necessary here, this can be closed @roryabraham

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.EngineeringExternalAdded to denote the issue can be worked on by a contributorWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions