LHN is focusing on incorrect chat when using chat switcher or when requesting money from global FAB

[isagoico]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Action Performed:

Chat switcher scenario:

1. Open chat switcher via CMD + K or in windows use the search function
2. Search for an user
3. Select any user

Request Money scenario:

1. Click on FAB
2. Click on request money
3. Set an amount
4. Search for any user
5. Finish the request money flow

Expected Result:

User should be redirected to the correct chat and it should be focused in LHN

Actual Result:

User is redirected to correct chat but the previous chat is focused in LHN.

Workaround:

None needed, visual issue.

Platform:

Where is this issue occurring?

Web ✔️
iOS
Android
Desktop App ✔️
Mobile Web

Version Number: 1.0.77-0

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

Notes/Photos/Videos: Any additional supporting documentation

Uploading Grabando #195.mp4…

Expensify/Expensify Issue URL:

View all open jobs on Upwork

---

From @iwiznia https://expensify.slack.com/archives/C01GTK53T8Q/p1626080273102100

on web (staging). Steps:

• Select a chat
• Use CMD+K to switch to a different chat
• Check that the LHN is still showing the old chat as active

[MelvinBot]

Triggered auto assignment to @Dal-Papa (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[alex-mechler]

Also happening on desktop https://expensify.slack.com/archives/C01GTK53T8Q/p1626109017129700

[parasharrajat]

This seems to me a regression but I have not checked it yet.

[Dal-Papa]

I could reproduce on desktop and browser based versions. I think it can be picked up by contributors so assigning External

[MelvinBot]

Triggered auto assignment to @michaelhaxhiu (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

[rdjuric]

@michaelhaxhiu I caused this one. Opening a PR to fix it now

Looks like componentDidMount isn't fired when we navigate to a ReportScreen from the Search/FAB. So we need to store our currentlyViewedReportID in the componentDidUpdate lifecycle (after checking for a report change).

[parasharrajat]

This issue can be closed now as PR is merged, after testing.

[isagoico]

Issue is still reproducible in staging. Once the PR is merged to staging and retested we can close it out.

[michaelhaxhiu]

Good works folks. I'll let you see this through and thanks for being proactive @rdjuric and @parasharrajat !

[Dal-Papa]

I confirmed that this issue is solved now and it had time for regression to be tested. Closing.