mWeb -Chat- The LHN page is visible for a moment when opening the URL of conversation

[kbecciv]

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

---

Issue found when executing PR #14669

Action Performed:

1. Go to URL https://staging.new.expensify.com/
2. Log into NewDot with an existing account that has more than 2 chats
3. Copy the relative path from an existing chat report
4. Navigate to another chat or page and then use the relative from step 2 to open the chat

Expected Result:

The correct chat is opened

Actual Result:

The LHN page is visible for a moment when opening the URL of conversation

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android / native
• Android / Chrome
• iOS / native
• iOS / Safari
• MacOS / Chrome / Safari
• MacOS / Desktop

Version Number: 1.2.67.3

Reproducible in staging?: Yes

Reproducible in production?: Yes

If this was caught during regression testing, add the test name, ID and link from TestRail:

Email or phone of affected tester (no customers):

Logs: https://stackoverflow.com/c/expensify/questions/4856

Notes/Photos/Videos: Any additional supporting documentation

Bug5928882_Record_2023-02-08-02-06-44.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

[MelvinBot]

Triggered auto assignment to @stephanieelliott (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[MelvinBot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[mountiny]

cc @marcochavezf I think we dont have to fix this I think this could be re-evaluated after the navigation refactor

[MelvinBot]

Looks like something related to react-navigation may have been mentioned in this issue discussion.

As a reminder, please make sure that all proposals are not workarounds and that any and all attempt to fix the issue holistically have been made before proceeding with a solution. Proposals to change our DeprecatedCustomActions.js files should not be accepted.

Feel free to drop a note in #expensify-open-source with any questions.

[marcochavezf]

Thanks @mountiny, sounds good. Just curious, do you know what is the latest of the navigation refactor?

[mountiny]

@marcochavezf we are working on the detailed design doc section at the moment, the proof of concept seems to be working great 🎉 lets hope that can be transported to App as well

[MelvinBot]

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

[MelvinBot]

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

[stephanieelliott]

Cool, sounds like this is being addressed in the nav refractor!