[$1000] Web - Unexpected error displayed after adding a comment

[kbecciv]

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

---

Version Number: 1.4.31.0 Reproducible in staging?: n/a Reproducible in production?: n/a 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: @jliexpensify Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1706069427229519

Action Performed:

1. Login in NewDot
2. Select the Workspace chat
3. Add a comment

Expected Result:

User is able to add comment without any error

Actual Result:

Unexpected error displayed after adding a comment

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/~0186123ce8bf2e2147
• Upwork Job ID: 1752713142580895744
• Last Price Increase: 2024-02-05

[melvin-bot[bot]]

Triggered auto assignment to @johncschuster (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[melvin-bot[bot]]

@johncschuster Eep! 4 days overdue now. Issues have feelings too...

[melvin-bot[bot]]

Job added to Upwork: https://www.upwork.com/jobs/~0186123ce8bf2e2147

[melvin-bot[bot]]

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

[DylanDylann]

I can't reproduce. No proposal yet

[johncschuster]

I'll buzz #expensify-open-source on Monday to drum up proposals.

[melvin-bot[bot]]

Upwork job price has been updated to $1000

[johncschuster]

Increased the bounty

[melvin-bot[bot]]

@johncschuster @DylanDylann this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

[johncschuster]

I'm not positive, but I bet this is a Backend issue. @DylanDylann, what are your thoughts?

[melvin-bot[bot]]

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

[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? 💸

[mvtglobally]

Issue not reproducible during KI retests. (First week)

[jeremy-croff]

Could it be related to the Category? I do not have that option. Maybe the Service doesn't like it?

Additionally, I'm clueless how to set up this reimbursement report as well as get the Department options.

[DylanDylann]

I can't reproduce this issue with test step on the OP. @jliexpensify Could you help to detail the previous step? how we create that report and what did we do before?

[jliexpensify]

I would say that we should close this - honestly, these Unexpected Error GH's are really frustrating as they happen once and generally only to a single user and are near-impossible to reproduce. I also can't reproduce anymore.

cc @johncschuster

[melvin-bot[bot]]

@johncschuster @DylanDylann this issue is now 3 weeks old. There is one more week left before this issue breaks WAQ and will need to go internal. What needs to happen to get a PR in review this week? Please create a thread in #expensify-open-source to discuss. Thanks!

[DylanDylann]

Let's close this one

[DylanDylann]

@johncschuster Not overdue. Wait to close

[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? 💸

[johncschuster]

Just caught up on this! Yeah, I agree we can close the issue. Thanks!