App: Dev: Web - Console error `Error parsing URLs: TypeError: Failed to construct 'URL': Invalid URL`
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:
- Go to any chat and enter the message
-77.com
- Edit the message and change the text to:
-[77.com](https://-77.com)
- Notice that the console error props up.
Expected Result:
Should not show any console error
Actual Result:
Shows console error - Url.js:46 Error parsing URLs: TypeError: Failed to construct ‘URL’: Invalid URL
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: Dev 1.3.62.0 Reproducible in staging?: no Reproducible in production?: no 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
Expensify/Expensify Issue URL: Issue reported by: ~@narzullome~ @Natnael-Guchima reported earlier Slack conversation:
- https://expensify.slack.com/archives/C049HHMV9SM/p1693374389112709
- https://expensify.slack.com/archives/C049HHMV9SM/p1699915690734349?thread_ts=1699551645.734819&cid=C049HHMV9SM
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~010fdcd111103dab09
- Upwork Job ID: 1701909826193559552
- Last Price Increase: 2023-09-13
Issue Owner
Current Issue Owner: @MariaHCDAbout this issue
- Original URL
- State: closed
- Created 10 months ago
- Comments: 44 (32 by maintainers)
I was assigned to the other issue, @Natnael-Guchima is correct, I’ve updated the OP to reflect
vs

Closing other issue since this one has more progress on it.
Great! I believe we can now move forward with the payment for reporting, @bfitzexpensify
This should be fixed once BE returns the full URL.
Okay, reproduced the console error when I created a public room in dev:
let’s fix it!
Will take a look and see if I can reproduce this on dev tomorrow