Accessing a chat that user doesn’t have access to will open a blank chat page without any explanation

[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. Create public room with an user that can use policy rooms (Note that we need to mark visibility as public)
2. Login to another account that cannot use policy rooms
3. Access the chat link in 1
4. Observe that we see a blank chat report page without any content

Expected Result:

It should show not found page

Actual Result:

It shows the bank page

Workaround:

unknown

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.2.88-0
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:

Screen.Recording.2023-03-23.at.13.33.20.mov

Recording.19.mp4

Expensify/Expensify Issue URL:
Issue reported by: @tienifr
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1679553438113879?thread_ts=1679072391.780749&cid=C049HHMV9SM

View all open jobs on GitHub

[MelvinBot]

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

[MelvinBot]

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

[hayata-suenaga]

@kavimuru I couldn't reproduce the issue. I'm getting the following message.

Does the other user have to belong to the same domain?

[miljakljajic]

bumping @kavimuru

[kavimuru]

@miljakljajic Please follow the following steps:

1. Create a public room in the account behind beta
2. Copy the URL link
3. Log in to Gmail account and paste the link

[hayata-suenaga]

will try to reproduce this today

[MelvinBot]

@miljakljajic Huh... This is 4 days overdue. Who can take care of this?

[miljakljajic]

@hayata-suenaga has been OOO. Let me know if you're able to reproduce this once you're back online, Hayata! :)