[Due for payment 2025-08-22] [$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.1.77-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: Chat

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

Bug6868741_1750791485166.Recording_34.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021947799747408464064
• Upwork Job ID: 1947799747408464064
• Last Price Increase: 2025-07-22
• Automatic offers:
• huult | Contributor | 108170630

Issue Owner

Current Issue Owner: @muttmuure

[melvin-bot]

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

[nabi-ebrahimi]

Proposal

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

Web - Clicking the back button does not navigate them back to that specific thread

What is the root cause of that problem?

We go back to the latest viewed report from here when the user leaves the thread. So the thread gets removed from history.

App/src/libs/actions/Report.ts

Lines 3465 to 3471 in 11ff1d3

	function navigateToMostRecentReport(currentReport: OnyxEntry<Report>) {
	const lastAccessedReportID = findLastAccessedReport(false, false, undefined, currentReport?.reportID)?.reportID;
	if (lastAccessedReportID) {
	const lastAccessedReportRoute = ROUTES.REPORT_WITH_ID.getRoute(lastAccessedReportID);
	Navigation.goBack(lastAccessedReportRoute);
	} else {

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

We should use from navigate method instead of goBack to keep the thread in the history.

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

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

None

What alternative solutions did you explore? (Optional)

[nabi-ebrahimi]

My Proposal Demo

keep-the-thread-histor.mp4

[muttmuure]

discussions ongoing

[melvin-bot]

@muttmuure Whoops! This issue is 2 days overdue. Let's get this updated quick!

[melvin-bot]

@muttmuure Huh... This is 4 days overdue. Who can take care of this?

[melvin-bot]

@muttmuure Still overdue 6 days?! Let's take care of this!

[melvin-bot]

@muttmuure 10 days overdue. Is anyone even seeing these? Hello?

[melvin-bot]

@muttmuure this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!