JS console error message displayed for chronos

[m-natarajan]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: 9.0.3-2 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 Expensify/Expensify Issue URL: Issue reported by: @rafecolton Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1719522042334589

Action Performed:

1. Go to staging.new.expensify.com
2. Initiate a chat with Chronos

   Expected Result:

   No console error displayed

   Actual Result:

   Console error displayed

   Workaround:

   Unknown

   Platforms:

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

   • [ ] Android: Native
   • [ ] Android: mWeb Chrome
   • [ ] iOS: Native
   • [ ] iOS: mWeb Safari
   • [X] MacOS: Chrome / Safari
   • [ ] MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01bbd4ecc222ba2d37
• Upwork Job ID: 1807900884343246877
• Last Price Increase: 2024-07-08

Issue Owner

Current Issue Owner: @allgandalf

[melvin-bot[bot]]

Triggered auto assignment to @VictoriaExpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[jacobkim9881]

I think this issue shouldn't be solved from FE.

[VictoriaExpensify]

I've looked at the Slack thread and it seems we agree this is an issue.

Since this is chat related, but not expense relates, I think this belongs to #VIP-VSB

[melvin-bot[bot]]

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

[melvin-bot[bot]]

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

[allgandalf]

@VictoriaExpensify , how do we initiate a chat with chronos?, having hard time searching for it

[jacobkim9881]

@allgandalf Starting a chat with chronos@expensify.com

[allgandalf]

Thanks @jacobkim9881 , were you able to reproduce this?

[jacobkim9881]

@allgandalf Yes, it was reproducible. I only got an error console starting with "Refuse to execute..." but not last error starting with "FullStory orgId..." as I remember.

[VictoriaExpensify]

@VictoriaExpensify , how do we initiate a chat with chronos?, having hard time searching for it

@allgandalf It looks like @jacobkim9881 helped you out with that - did that work for you?

[allgandalf]

I was able to chat but no console error, will try again, were you able to reproduce this bug?

[melvin-bot[bot]]

📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

[melvin-bot[bot]]

@VictoriaExpensify, @allgandalf Huh... This is 4 days overdue. Who can take care of this?

[VictoriaExpensify]

Ohhhh I don't think I should have made this an External issue - sorry, I'm still quite new to BZ. I'm going to make this an internal issue and see if we can get some traction.

[allgandalf]

not overdue melvin!

[melvin-bot[bot]]

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

[allgandalf]

@VictoriaExpensify what should be done moving forward for this issue?

[melvin-bot[bot]]

@VictoriaExpensify @allgandalf this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

[allgandalf]

friendly bump @VictoriaExpensify

[melvin-bot[bot]]

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

[allgandalf]

not overdue melvin, waiting for a reply from @VictoriaExpensify

[allgandalf]

This is an internal issue so going to unassign myself, but if this at all requires any front end changes, do assign me back, would love to review the proposals for the fix, thanks :)

[mvtglobally]

Issue not reproducible during KI retests. (First week)

[mvtglobally]

Issue not reproducible during KI retests. (Second week)

[VictoriaExpensify]

I think we can close this out. @rafecolton you reported this issue initially so please reopen if you can still reproduce and think it needs attention