[HOLD for payment 2025-01-07] [HOLD for payment 2025-01-02] Expense - From expense report page tapping app's back button navigated to Workspace chat page

[IuliiaHerets]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: 9.0.78-1
Reproducible in staging?: Yes
Reproducible in production?: No
Issue reported by: Applause Internal Team
Device used: Redmi note 10s Android 13
App Component: Money Requests

Action Performed:

1. Go to https://staging.new.expensify.com/home
2. Tap fab - new workspace
3. Create 2 expenses
4. Open the expense and navigate to the report page
5. Tap the app's back button

Expected Result:

From expense report page tapping app's back button user must be navigated to workspace chat page.

Actual Result:

From expense report page tapping app's back button user navigated to LHN instead workspace chat page.

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6701609_1735009424228.Screenrecorder-2024-12-24-08-26-44-483_compress_1.1.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @sakluger

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @sakluger (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.

[melvin-bot]

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

[github-actions]

👋 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.

[Beamanator]

Looooks like the same as #54496

[daledah]

It can be fix in this #54511

[Beamanator]

PR Merged & CP'd, waiting on test!

[kavimuru]

Bug is not reproduced

SamsungA224g_Chrome_Android13.mp4

[Beamanator]

Nice! Fixed, so closing this out

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.78-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• [CP staging] fix: go back to LHN page #54511

If no regressions arise, payment will be issued on 2025-01-02. 🎊

[melvin-bot]

@Beamanator @sakluger @Beamanator 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]

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.79-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• [CP staging] fix: go back to LHN page #54511

If no regressions arise, payment will be issued on 2025-01-07. 🎊

[melvin-bot]

@Beamanator @sakluger @Beamanator 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]