[$500] Web - Request money - Console error after refreshing page and requesting money

[lanitochka17]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Issue found when executing PR #27395

Action Performed:

1. Go to https://staging.new.expensify.com/
2. Log in
3. Refresh the page
4. Click on FAB > Request money

Expected Result:

There is no console error

Actual Result:

There is a console error after refreshing a page and selecting "Request money". Console error does not show up if user navigates to different areas of the app before requesting money

Workaround:

Unknown

Platforms:

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

• Android / native
• Android / Chrome
• iOS / native
• iOS / Safari
• Windows / Chrome
• MacOS / Desktop

Version Number: 1.3.71-5

Reproducible in staging?: Yes

Reproducible in production?: Yes

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: Any additional supporting documentation

Bug6205468_Recording__234.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/~010ab36420ceccc863
• Upwork Job ID: 1704804349777985536
• Last Price Increase: 2023-09-21

[melvin-bot]

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

[mallenexpensify]

@lanitochka17 I see the below on Chrome. Can you screenshot a pic of the error you're seeing so I can confirm they're the same? ( it's a lil hard for me t make out in the vid)

[lanitochka17]

I see the same console error in Windows/Chrome

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~010ab36420ceccc863

[melvin-bot]

Current assignee @mallenexpensify is eligible for the External assigner, not assigning anyone new.

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @fedirjh (External)

[mallenexpensify]

Guessing/hoping this can be external, I'm unsure though. @fedirjh , what do you think?

[Talha345]

This is a CSP error and needs to be fixed on the server side.

[fedirjh]

cc @mallenexpensify This should be internal, should be fixed on server.

[melvin-bot]

Current assignee @fedirjh is eligible for the Internal assigner, not assigning anyone new.

[mallenexpensify]

Thanks @fedirjh and @Talha345, made it Internal.

[fedirjh]

Awaiting internal assignment.

[mallenexpensify]

hmm... are we treating console errors with the same level of priority as other bugs?

[fedirjh]

are we treating console errors with the same level of priority as other bugs?

It depends on the specific console error. Some errors indicate broken functionality and require higher priority, while in this case, it's a CSP (Content Security Policy) error that doesn't seem to affect functionality. IMO, it's not as high a priority as other bugs.

[melvin-bot]

@mallenexpensify, @fedirjh Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[mallenexpensify]

Still waiting internal pickup, since it's not high priority, I'll wait a lil bit longer then drop in #engineering-chat to get more 👀 and feedback about next steps

[melvin-bot]

@mallenexpensify @fedirjh this issue is now 4 weeks old and preventing us from maintaining WAQ. This should now be your highest priority. Please post below what your plan is to get a PR in review ASAP. Thanks!

[melvin-bot]

@mallenexpensify, @fedirjh Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[mallenexpensify]

Posted internally
https://expensify.slack.com/archives/C03SSAQ7P/p1698785604286439

[mallenexpensify]

No takers in the post above, will post again next week if no one picks this up

[mallenexpensify]

Maybe post about next week, it's not a priority and it the holidays here...

[mallenexpensify]

Likely closing this soon since it's a console error and we're prioritizing working on roadmap issues