[Due for payment 2026-01-15] Chat - Unable to add user to group when clicked outside Add to group button in Recents section

[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.95-3
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #77734, https://test-management.browserstack.com/projects/2219752/test-runs/TR-2697/folder/13176684/41236574/1110521929?issue_type=jira
Email or phone of affected tester (no customers): sdjonsidjoijdosdjos@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.1 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

• Create two chats with different user (must have two users under Recents section in FAB > Start chat).

1. Go to staging.new.expensify.com
2. Open FAB > Start chat > Chat.
3. Click Add to group on User B under Recents section.
4. Click outside Add to group on User C row under Recents section.

Expected Result:

The second user will be selected.

Actual Result:

DM with the second user opens instead.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @NicMendonca

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #77734

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[melvin-bot]

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

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.