#announce workspace appears to the user without any notification and as read.

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

---

Action Performed:

1. Go to settings then workspaces and create a new workspace
2. Click members > then click invite > choose User B to invite
3. Click Next > then Invite
4. Login as user B and find the #announce workspace he was just invited to inside the LHN.

Expected Result:

#announce room should appear for user B as unread and he got Notified that something new has been added to his LHN, and he is now a member of a new workspace. Just like what happens if he is added as a new chat or added as a group member.
Another scenario: is not to add #announce workspace to user B LHN unless it had some messages inside it. I suggest this scenario because once the #announce has some messages inside it, it appears unread as expected.

Actual Result:

#announce workspace appears for user B as read and he doesn't get anything to notify him that something added to his LHN and that he has been invited to a workspace.

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

Platforms:

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

• Android / native
• Android / Chrome
• iOS / native
• iOS / Safari
• MacOS / Chrome / Safari
• MacOS / Desktop

Version Number: 1.3.43-1
Reproducible in staging?: y
Reproducible in production?: y
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
Notes/Photos/Videos: Any additional supporting documentation
Screencast from 18-07-23 01_00_37.webm

Recording.1292.mp4

Expensify/Expensify Issue URL:
Issue reported by: @Ahmed-Abdella
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1689634166791039

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @michaelhaxhiu (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[melvin-bot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[hannojg]

This could be a regression from my PR:

• [Fix #21022] Improve performance by reducing re-renders SidebarLinks #21406

looking into it!

[hannojg]

Taking my comment back, this issue is more of a feature request than a bug / regression

[michaelhaxhiu]

Hmm maybe we should close this since it's a feature request. This started as a bug and we need to propose a feature it seems.