Room - Who can post displays All members after setting it to Admins

[IuliiaHerets]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: 9.0.66-0
Reproducible in staging?: Y
Reproducible in production?:
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/5257611
Issue reported by: Applause Internal Team

Action Performed:

1. Log in to NewDot with an account that owns an existing Workspace
2. Click on FAB/ Start Chat/ #Room.
3. Enter room name and select a workspace.
4. Set "Who can post" setting to "admins only"
5. Create a room.
6. Click on the header of created room chat/ Settings.
7. Verify that Who can post setting is set to "Admins only".

Expected Result:

Who can post setting is set to Admins only in the room details after selecting this option during room creation process.

Actual Result:

Who can post setting is set to All members in the room details after selecting "Admins only" during room creation process.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6673892_1732342512444.Who_can_post.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.

[melvin-bot]

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

[melvin-bot]

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

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

[rojiphil]

This is a BE issue as AddWorkspaceRoom API request returns response for writeCapability as all even when it is requested with admins.

[rlinoz]

Apparently this is Web-E as mentioned in the code above, still trying to find out what it is.

[rlinoz]

Oh actually, apparently in prod we call OpenReport right after calling AddWorkspaceRoom which returns the correct writeCapability

[rlinoz]

Im gonna remove the blocker since I think we should fix the AddWorkspaceRoom response.

[rlinoz]

Deployed to prod