Search - Tapping "From" link in expense navigates back to search result instead of WS chat

[jponikarchuk]

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.66-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/folder/13176922/test-cases/41237514
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause Internal Team
Device used: iPhone 15 iOS 26.1
App Component: Search

Action Performed:

1. Sign in to ND
2. Create a workspace, create a single expense in the workspace chat, selecting a category
3. In the workspace chat tap search icon, select "Select in User X's expenses"
4. Continue the search query, type "category:", select the category from step 2
5. Tap Enter or search suggestion to see the result
6. On the Reports page tap the expense row, then tap "From User X's expenses" link

Expected Result:

User is navigated to the workspace chat

Actual Result:

Tapping "From" link in expense navigates back to the search result instead of workspace chat, after searching for the category

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

1.mp4

View all open jobs on GitHub

[melvin-bot]

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

[truph01]

Proposal

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

Search - Tapping "From" link in expense navigates back to search result instead of WS chat

What is the root cause of that problem?

The logic at

App/src/components/ParentNavigationSubtitle.tsx

Lines 118 to 121 in f82a8db

	if (Navigation.getTopmostReportId() === parentReportID) {
	Navigation.dismissModal();
	return;
	}

is triggered in this case because the report screen remains in the navigation stack, but it isn't displayed underneath RHP, causing the app to incorrectly determine the return destination.

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

We should correct the condition at

App/src/components/ParentNavigationSubtitle.tsx

Line 118 in f82a8db

if (Navigation.getTopmostReportId() === parentReportID) {

if (Navigation.getTopmostReportId() === parentReportID && currentFullScreenRoute?.name === NAVIGATORS.REPORTS_SPLIT_NAVIGATOR) {

What alternative solutions did you explore? (Optional)