[HOLD for payment 2023-04-13] [HOLD for payment 2023-04-12] Chat - Infinity loading displayed for link Valid ID https://staging.new.expensify.com/r/1234 instead "You don't have access to this chat message" in the conversation history.

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

---

Action Performed:

1. Log in to NewDot
2. On the URL change the conversation ID to any combination of 1-4 numbers. E.g https://staging.new.expensify.com/r/1234

Expected Result:

Verify You see a You don't have access to this chat message in the conversation history

Actual Result:

Infinity loading displayed for link Valid ID https://staging.new.expensify.com/r/1234 instead "You don't have access to this chat message" in the conversation history.

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

Reproducible in staging?: Yes

Reproducible in production?: No

If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/3322825

Email or phone of affected tester (no customers):

Logs: https://stackoverflow.com/c/expensify/questions/4856

Notes/Photos/Videos: Any additional supporting documentation

Bug6004979_infinity.1.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01d498a31ce02d2fa7
• Upwork Job ID: 1643282360869244928
• Last Price Increase: 2023-04-04

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

[MelvinBot]

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

[kbecciv]

Issue is not reproduced in Production, attaching video.

RPReplay_Final1680571453.MP4

[situchan]

This issue came from staging backend.
api?command=OpenReport returns jsonCode: 403 which expects 200.
This doesn't happen on production backend.

To reproduce in dev locally, enable Use Staging Server.

[marcaaron]

👀 into it now

[marcaaron]

Seems related to https://github.com/Expensify/Web-Expensify/pull/36929

cc @jasperhuangg @techievivek

[marcaaron]

Opening a fix PR. I think the solution is to handle the failureData case when calling OpenReport.

[MelvinBot]

Job added to Upwork: https://www.upwork.com/jobs/~01d498a31ce02d2fa7