Room - Error instructs to invite users to #announce when users cannot be invited to #announce

[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.31-5
Reproducible in staging?: Y
Reproducible in production?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp https://expensify.testrail.io/index.php?/tests/view/4938531
Email or phone of affected tester (no customers): applausetester+kh010901@applause.expensifail.com
Issue reported by: Applause Internal Team

Action Performed:

1. Go to staging.new.expensify.com
2. Go to workspace settings > Members.
3. Invite more than 8 members.
4. Go to #announce.
5. Click on the room header > Members.
6. On the search field, enter term that will not return result.

Expected Result:

The error message for invalid search term will not show the prompt to invite member using the invite button because users cannot be invited manually in #announce room.

Actual Result:

The error message is "Member not found. To invite a new member to the room, please use the invite button above." when there is no invite button as users cannot be invited manually in #announce room.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6597926_1725910348020.20240910_032728.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @yuwenmemon (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

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

[rayane-d]

@Expensify/design What do you think about this bug? Do we need to use a different copy for this case?

[rayane-d]

cc @paultsimura for visibility

[yuwenmemon]

This is coming from: #47201