[HOLD for payment 2025-01-07] [HOLD for payment 2025-01-02] mWeb - Workspace - Using back button on WS chat, leads to inbox instead of WS profile.

[IuliiaHerets]

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.0.78-1
Reproducible in staging?: Yes
Reproducible in production?: No
Email or phone of affected tester (no customers): ibellicotest+115@gmail.com
Issue reported by: Applause Internal Team
Device used: Motorola MotoG60 - Android 12 - Chrome
App Component: Workspace Settings

Action Performed:

1. Open the staging.new.expensify.com website.
2. Tap on "Settings" and select "Workspaces"
3. Open any workspace.
4. Tap on the workspace chat button on the bottom.
5. Once redirected to workspace chat, tap on the back button on the top left corner.

Expected Result:

After tapping on the back button, user should return to workspace settings.

Actual Result:

After opening workspace chat via workspace settings and tapping on the back button, the user lands on inbox instead of returning to workspace settings.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6701646_1735017672514.BackWS.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @bfitzexpensify (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]

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

[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]

Pretty sure this is also going to be fixed in #54511 🤔

[Beamanator]

PR Merged & CP'd, waiting on test!

[kavimuru]

Not reproduced

SamsungA22_4g_Android13_Chrome.mp4