[$250] Web - Clicking the back button does not navigate them back to that specific thread

[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.8-1
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail: https://github.com/Expensify/Expensify/issues/389888
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause Internal Team
Device used: Windows 10 - Chrome
App Component: Other

Action Performed:

1. Join a thread by commenting in it
2. Leave the thread and get taken back to the DM or channel
3. Hit the back button (or three-finger swipe, cmd + [)

Expected Result:

you are taken back to the thread you were just viewing

Actual Result:

that thread does not appear in the history, and you are taken back to whatever chat you were viewing before

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

Bug6924728_1755946366267.Recording_57.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021966171009703767951
• Upwork Job ID: 1966171009703767951
• Last Price Increase: 2025-09-25

Issue Owner

Current Issue Owner: @bfitzexpensify

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

[dmkt9]

Proposal

Please re-state the problem that we are trying to solve in this issue.

that thread does not appear in the history, and you are taken back to whatever chat you were viewing before

What is the root cause of that problem?

Here we use Navigation.goBack to go back to the last accessed report:

App/src/libs/actions/Report.ts

Line 3547 in 9c2929e

Navigation.goBack(lastAccessedReportRoute);

What changes do you think we should make in order to solve the problem?

We should add a shouldUseNavigate param to navigateToMostRecentReport (if needed) and use Navigation.navigate instead of Navigation.goBack when shouldUseNavigate === true:

App/src/libs/actions/Report.ts

Line 3547 in 9c2929e

Navigation.goBack(lastAccessedReportRoute);

InteractionManager.runAfterInteractions(() => {
    Navigation.navigate(lastAccessedReportRoute);
});

Note: For the navigateToConciergeChat function inside navigateToMostRecentReport, we can also rely on the shouldUseNavigate parameter to determine whether to pass the {forceReplace: true} option.

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

NA

What alternative solutions did you explore? (Optional)

NA

Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~021966171009703767951

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @ahmedGaber93 (External)