Chat- Back button from expense detail leads to LHN rather than expense report conversation

[mitarachim]

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: v9.0.78-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Device used: Samsung s10/ chrome
App Component: Chat Report View

Action Performed:

1. Navigate to https://staging.new.expensify.com
2. Open any chat
3. Submit an expense
4. Navigate to expense detail page and click the top left back button

Expected Result:

The Back button navigate to expense conversation page

Actual Result:

Back button leads to LHN rather than expense report conversation

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6701565_1735002323431.Screen_Recording_20241224_035846_Chrome.mp4

View all open jobs on GitHub

[melvin-bot]

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

[daledah]

Edited by proposal-police: This proposal was edited at 2024-12-24 07:30:25 UTC.

Proposal

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

Back button leads to LHN rather than expense report conversation

What is the root cause of that problem?

Offending PR: #53969

We are setting to go back to ROUTES.HOME here and go back with shouldPopToTop as true

App/src/pages/home/ReportScreen.tsx

Line 299 in 8b7096f

Navigation.goBack(ROUTES.HOME, false, true);

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

We should update route to undefined

 Navigation.goBack(undefined, false, true);

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

What alternative solutions did you explore? (Optional)

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.

[DylanDylann]

It came from this change

@pac-guerreiro updated it to fix another bug. But now @pac-guerreiro is OOO. I will revert this change only to fix this bug

[daledah]

@RachCHopkins @cristipaval It is currently a deploy blocker that needs immediate attention. The previous PR addressed the issue in debug mode without impacting the production environment, so the fix should be straightforward.
If Dylan were to create the PR, we would need additional time for the C+ request and review process. However, since both @DylanDylann and I are online, I can quickly create a PR within 5 minutes and have @DylanDylann review it right away.

[DylanDylann]

@daledah Thanks for your concern, It seems to make sense. I haven't started on it.

@cristipaval What do you think about it? because @pac-guerreiro (the author of the offending PR) is OOO, @daledah can help to raise a PR because they also take time to investigate and find the RCA. Then we can compensate them a part

[cristipaval]

@daledah, thanks for jumping in! Please go ahead with your solution

[melvin-bot]

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

[Beamanator]

That ^ was me linking #54508 to this one b/c they look like the same root cause

[daledah]

I'll raise PR soon

[daledah]

@DylanDylann we have a open PR here

[Beamanator]

PR Merged & CP'd, waiting on test!

[Beamanator]

Fixed in staging so removed blocker label!

I believe we need to pay out @daledah for the fix before closing this out, right?