Workspace chat - The whisper notice doesn't appear in the workspace of the invited user.

[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.99-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail: #56288
Email or phone of affected tester (no customers): applausetester+bm467@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Web, mweb, android
App Component: Chat Report View

Action Performed:

1. Go to https://staging.new.expensify.com/
2. Create a user account. This will be owner of the workspace.
3. Create another account in a second browser (or incognito mode), this will be the guest of the owner's workspace.
4. In the first browser (owner), create a workspace (Settings > Workspace > New Workspace). Give it a name and confirm.
5. In the just created workspace page, click the "Invite" button
6. Invite the second account by typing their email and then select Admin for the role.
7. The workspace should automatically appear on the second account. You can see a welcome message in the workspace.
8. In the first account, select the invited user in the members page (Settings > Workspaces > Workspace > Members)
9. In the window that opened, change the role from Admin to User

Expected Result:

The whisper notice should appear in the workspace of the invited user

Actual Result:

The whisper notice doesn't appear in the workspace of the invited user.
That whisper appears in #admins room, but it is not visible for member, for Admin only.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6745588_1739790219529.bandicam_2025-02-17_13-49-40-317.mp4

View all open jobs on GitHub

[melvin-bot]

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

[heekinho]

Yes. It doesn't seem to work on staging but I think that's process related, maybe?
It needs this: https://github.com/Expensify/Auth/pull/14002 which is being holded by this app PR, right now.
So perhaps I missed adding that information? What's the process to deal with those cases, @flodnv @iwiznia

[melvin-bot]

📣 @heekinho! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:

1. Make sure you've read and understood the contributing guidelines.
2. Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
3. Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
4. Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
   
   Format:

Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>

[flodnv]

@iwiznia I think we need to treat this as not a blocker and test this whenever Auth gets deployed?

[iwiznia]

Yep