[HOLD for payment 2024-05-09] [$250] Group chat - Inconsistency in limitation when adding members via FAB and group details page

[kavimuru]

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: 1.4.63-0
Reproducible in staging?: y
Reproducible in production?: n
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: applause internal team
Slack conversation:

Action Performed:

1. Go to staging.new.expensify.com
2. Go to FAB > Start chat.
3. Click Add to group until the max amount of members is reached.
4. Note that only 8 participants can be selected.
5. Create the group chat with 8 participants.
6. Click on the chat header.
7. Go to Members > Invite member.
8. Invite a few more members.

Expected Result:

There should be consistency whether more than 9 members (including the creator) is allowed in the group chat when adding members via FAB and group details page.

Actual Result:

In Step 3, when creating group chat via FAB, not more than 8 members can be selected.
In Step 8. when adding members from group details page, there is no limitation at all.

Workaround:

unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native
• [x ] Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6453873_1713458029171.bandicam_2024-04-19_00-28-17-571.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01cde40901114ff34c
• Upwork Job ID: 1781091286528417792
• Last Price Increase: 2024-04-18
• Automatic offers:
• cubuspl42 | Reviewer | 0
• GandalfGwaihir | Contributor | 0

Issue Owner

Current Issue Owner: @zanyrenney

[melvin-bot]

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

[melvin-bot]

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

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

[kavimuru]

@jasperhuangg 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.

[jasperhuangg]

This appears to be a new feature that isn't on production yet (I think), so not worth blocking deploy on it. Plus it's a pretty minor bug. assigning @marcaaron since it looks like it was added in #39757