[HOLD for payment 2024-11-14] [$250] Search - Search icon is not responsive after tapping on room mention in Chat and exit chat

[IuliiaHerets]

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.0.45-2
Reproducible in staging?: Y
Reproducible in production?: Y
Email or phone of affected tester (no customers): applausetester+pso@applause.expensifail.com
Issue reported by: Applause Internal Team

Action Performed:

1. Launch New Expensify app.
2. Go to workspace chat.
3. Send a message containing #admins room mention.
4. Go to Search > Chat.
5. Tap on the #admins mention.
6. Swipe to the right to close the chat.
7. Tap on the Search icon.

Expected Result:

User should be able to navigate to Search after swiping to right to close the room chat when it is opened from Search.

Actual Result:

Search icon is not responsive after tapping on room mention in Chat and closing the chat.

Workaround:

Unknown

Platforms:

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6626382_1728242537349.ScreenRecording_10-07-2024_03-17-45_1.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021847130088347504306
• Upwork Job ID: 1847130088347504306
• Last Price Increase: 2024-10-25
• Automatic offers:
• rayane-djouah | Reviewer | 104596829
• Nodebrute | Contributor | 104596830

Issue Owner

Current Issue Owner: @alexpensify

[melvin-bot]

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

[IuliiaHerets]

We think that this bug might be related to #wave-control

[IuliiaHerets]

@alexpensify FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

[Nodebrute]

Proposal

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

Search icon is not responsive after tapping on room mention in Chat and exit chat

What is the root cause of that problem?

The first issue is that when we navigate back by swiping, we are returned to the Home screen instead of the Search screen. The second issue is that clicking on #admin or any room name on wide screens should open the report in the RHP, rather than navigating to it directly. It's because we navigate to ROUTES.REPORT_WITH_ID instead of ROUTES.SEARCH_REPORT

App/src/components/HTMLEngineProvider/HTMLRenderers/MentionReportRenderer/index.tsx

Line 76 in 6d8e739

const navigationRoute = reportID ? ROUTES.REPORT_WITH_ID.getRoute(reportID) : undefined;

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

When a room mention is clicked from the search pane to address both issues, we should open the report in the RHP instead of navigating directly to it. We can do something like this

  let navigationRoute = reportID ? ROUTES.REPORT_WITH_ID.getRoute(reportID) : undefined;
    const topmostCentralPaneRoute = getTopmostCentralPaneRoute(navigationRef.getRootState() as State<RootStackParamList>)
    const backTo = Navigation.getActiveRoute();
    if(topmostCentralPaneRoute?.name === SCREENS.SEARCH.CENTRAL_PANE){
        navigationRoute = reportID ?  ROUTES.SEARCH_REPORT.getRoute({reportID,backTo}) :undefined
    }

In the above code we are checking with getTopmostCentralPaneRoute === searchpanel if yes then we will navigate to ROUTES.SEARCH

Note

This is just pseudo-code, and we can refine it further in the PR

Result ios

Screen.Recording.2024-10-07.at.2.10.18.AM.mov

Result (wide screen)

Screen.Recording.2024-10-07.at.2.10.37.AM.mov

What alternative solutions did you explore? (Optional)

Another alternative solution would be to use getUrlWithBackToParam

App/src/ROUTES.ts

Lines 266 to 269 in 6d8e739

	REPORT_WITH_ID: {
	route: 'r/:reportID?/:reportActionID?',
	getRoute: (reportID: string, reportActionID?: string, referrer?: string) => {
	const baseRoute = reportActionID ? (`r/${reportID}/${reportActionID}` as const) : (`r/${reportID}` as const);

and pass the active route here as backTo param

App/src/components/HTMLEngineProvider/HTMLRenderers/MentionReportRenderer/index.tsx

Line 76 in 6d8e739

const navigationRoute = reportID ? ROUTES.REPORT_WITH_ID.getRoute(reportID) : undefined;

Other minor details can be addressed in the PR.

[alexpensify]

Adding this one to my test list and will get to it later this week.

[melvin-bot]

@alexpensify Whoops! This issue is 2 days overdue. Let's get this updated quick!

[alexpensify]

Still on my testing list

[alexpensify]

No update