LHN - Announce room does not appear on invited user's LHN

[kbecciv]

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.9.2
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. User A open staging.new.expensify.com
2. User A Create Workspace> Invite User B

Expected Result:

Workspace chat and announce room should be present in User's B LHN

Actual Result:

Announce room does not appear on User's B LHN

Workaround:

Unknown

Platforms:

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

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

Screenshots/Videos

Add any screenshot/video evidence

Bug6304595_1701963089634.Recording__1509.mp4

View all open jobs on GitHub

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

[melvin-bot]

Triggered auto assignment to @francoisl (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[francoisl]

I can reproduce on staging, going to keep investigating in dev.

[francoisl]

Weird I can't repro in dev, and also can't repro on staging anymore after trying again.

Screen.Recording.2023-12-07.at.10.39.44.AM.mov

[francoisl]

The announce room appears to be marked as read by default, maybe that's why it didn't show up in your LHN. This also happens on production so as far as I can tell, it's normal:

Screen.Recording.2023-12-07.at.10.52.29.AM.mov

Going to close this for now as it appears it's working fine after further investigation.