[HOLD for payment 2023-05-29] Infinite loading when navigating to a chat without access

[isagoico]

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. Log in to NewDot
2. From another app, click on the URL with the conversation ID to any combination of 1-4 numbers. E.g https://staging.new.expensify.com/r/1234
3. Verify You see a You don't have access to this chat message in the conversation history
4. Repeat with non-valid conversation ID (e..g, staging.new.expensify.com/r/sometxt)

Expected Result:

User should be redirected to "Hmmm.. it's not here" page

Actual Result:

Infinite loading when navigating to a chat without access - "Hmmm.. it's not here" page is never displayed

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.15-5

Reproducible in staging?: Yes
Reproducible in production?: No

If this was caught during regression testing, add the test name, ID and link from TestRail: 2 test cases are failing because of this issue:

1. Navigate to Chat without access (Valid and non valid ID)
2. Web/mWeb - Navigate to IOU via link

Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856

Notes/Photos/Videos: Any additional supporting documentation

Bug6058936_Scr2_ND.mp4

Expensify/Expensify Issue URL: N/A

Issue reported by: Applause - Internal team
Slack conversation: N/A

View all open jobs on GitHub

[melvin-bot]

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

[OSBotify]

👋 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 @jasperhuangg (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[jasperhuangg]

Investigating