[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

[MelvinBot]

Triggered auto assignment to Contributor Plus for review of internal employee PR - @s77rt (Internal)

[MelvinBot]

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

[MelvinBot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[MelvinBot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 1.2.94-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• [CP Staging] Fix infinity loading display for inaccessible report #16918

If no regressions arise, payment will be issued on 2023-04-12. 🎊

After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.

• External issue reporter
• Contributor that fixed the issue
• Contributor+ that helped on the issue and/or PR

As a reminder, here are the bonuses/penalties that should be applied for any External issue:

• Merged PR within 3 business days of assignment - 50% bonus
• Merged PR more than 9 business days after assignment - 50% penalty

[MelvinBot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 1.2.95-0 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• [CP Staging] Fix infinity loading display for inaccessible report #16918

If no regressions arise, payment will be issued on 2023-04-13. 🎊

After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.

• External issue reporter
• Contributor that fixed the issue
• Contributor+ that helped on the issue and/or PR

As a reminder, here are the bonuses/penalties that should be applied for any External issue:

• Merged PR within 3 business days of assignment - 50% bonus
• Merged PR more than 9 business days after assignment - 50% penalty

[thienlnam]

This looks resolved, anything else needed to be done here? @marcaaron

[marcaaron]

Payment for @mollfpr

[francoisl]

Thanks for the fix, going to remove the Deploy Blocker label so that it doesn't block the deploy moving forward.

[marcaaron]

I think this is ready for payment but no BZ is assigned gonna add the bug label to get some help (I think it should work..?)

[MelvinBot]

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

[kadiealexander]

@mollfpr just sent you a contract in Upwork :)

[mollfpr]

@kadiealexander Accepted, thank you!

[kadiealexander]

Thanks for the speed @mollfpr! All paid. Leaving this open in case there are any other actions @marcaaron.