[Due for payment 2025-12-25] [$250] Dev : Report chat is not visible in LHN if we open concierge chat in another window

[m-natarajan]

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.38-0
Reproducible in staging?: Y
Reproducible in production?: Y
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
Expensify/Expensify Issue URL:
Issue reported by: @allgandalf
Slack conversation (hyperlinked to channel name): #Expensify Bugs

Action Performed:

1. Be in focus mode
2. Open a workspace chat
3. Submit Expense
4. Open that expense
5. Now open expensify in another tab and open concierge chat
6. Go back to previous tab

Expected Result:

The report chat should be visible in the LHN

Actual Result:

Concierge chat is visible in the LHN even when we have opened a report chat in first tab
(In staging the report chat is not displayed in LHN)

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

Platforms:

Select the officially supported platforms where the issue was reproduced:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari
• MacOS: Desktop

Platforms Tested:

On which of our officially supported platforms was this issue tested:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Screen.Recording.2025-10-25.at.12.39.03.AM.mov

Recording.1810.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021983278058299028658
• Upwork Job ID: 1983278058299028658
• Last Price Increase: 2025-10-28
• Automatic offers:
• FitseTLT | Contributor | 109313193

Issue Owner

Current Issue Owner: @

Issue Owner

Current Issue Owner: @rojiphil

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

[lorretheboy]

Proposal

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

Report chat is not visible in LHN if we open concierge chat in another window

What is the root cause of that problem?

We are prioritizing currentReportIDFromPath (derived from LAST_VISITED_PATH) over currentReportID (from the actual navigation state)

App/src/hooks/useSidebarOrderedReports.tsx

Line 81 in c8e5abd

const derivedCurrentReportID = currentReportIDForTests ?? currentReportIDValue?.currentReportIDFromPath ?? currentReportIDValue?.currentReportID;

• When you opened a report in Tab 1, currentReportID was set to that report's ID
• When you opened Concierge chat in Tab 2, the LAST_VISITED_PATH was updated to the Concierge chat URL
• When you switched back to Tab 1, currentReportIDFromPath (from LAST_VISITED_PATH) now pointed to Concierge
• Since currentReportIDFromPath had higher priority, the LHN showed Concierge instead of the report

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

We should reverse the priority so that currentReportID (from the actual navigation state) takes precedence

    const derivedCurrentReportID = currentReportIDForTests ?? currentReportIDValue?.currentReportID ?? currentReportIDValue?.currentReportIDFromPath;

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.

[FitseTLT]

Proposal

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

Dev : Report chat is not visible in LHN if we open concierge chat in another window

What is the root cause of that problem?

derivedCurrentReportID here is set to currentReportIDFromPath if it exists

App/src/hooks/useSidebarOrderedReports.tsx

Line 81 in c8e5abd

const derivedCurrentReportID = currentReportIDForTests ?? currentReportIDValue?.currentReportIDFromPath ?? currentReportIDValue?.currentReportID;

and currentReportIDFromPath is a value set from last accessed report

App/src/hooks/useCurrentReportID.tsx

Line 73 in 0983d75

currentReportIDFromPath: lastAccessReportFromPath || undefined,

so now when we open another report on another tab the last accessed report is set to another report which will remove the report in the old tab from LHN

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

This currentReportIDFromPath implementation was done in #56523 to fix a flashing bug on LHN. This bug was caused by the slow update of currentReportID as it is set via onStateChange event with a setTimeout delay (BTW we could avoid the setTimeout but it still doesn't fully solve the flickering). So when we click on an unread report that would not be in the list of the LHN if it weren't unread the LHN item for the report will hide briefly and come back. What we should do is replace using last accessed report with useNavigationState hook and get the report from the state which would solve both bugs.

const currentReportIDFromPath = useNavigationState((state) => Navigation.getTopmostReportId(state));

    const derivedCurrentReportID = currentReportIDForTests ?? currentReportIDFromPath ?? currentReportIDValue?.currentReportID; // currentReportIDValue?.currentReportID might not be relevant
    

Ofcourse we can reuse the whole logic of updateCurrentReportID to set the current report or even call updateCurrentReportID of the context on change of nav state via useNavigationState instead of onStateChange listener to apply wholistically on context.

What alternative solutions did you explore? (Optional)

[melvin-bot]

@muttmuure Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[melvin-bot]

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

[melvin-bot]

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