[$500] Mweb - IOU - When user creates distance request, unexpected error is displayed.

[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.11
Reproducible in staging?: y
Reproducible in production?: y
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: Applause - Internal Team
Slack conversation:

Action Performed:

1. Go to https://staging.new.expensify.com/
2. Tap Workspace chat
3. Tap plus icon --- request money --- Distance
4. Enter start "1907 Woodland Ave, Coffeyville, KS" and finish "1859 County RD 4300" waypoints
5. Tap next
6. Tap Request

Expected Result:

User must be able to create distance request.

Actual Result:

When user creates distance request, unexpected error is 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
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6309178_1702309051479.distance.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01ab7e708380b1f9ec
• Upwork Job ID: 1734241321301344256
• Last Price Increase: 2023-12-18

[melvin-bot]

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

[melvin-bot]

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

[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

[melvin-bot]

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

[c3024]

Cannot reproduce the bug.

[dksingla]

Seems to be a BE error. It's producible with the 'Start' and 'Finish' used in the bug report. Following is the response from the server.

{
  "code": 666,
  "jsonCode": 666,
  "type": "Expensify\\Libs\\Error\\ExpError",
  "UUID": "80ADBEDB-6248-4C16-B2EA-85E03A744715",
  "message": "An unexpected error occurred, please try again. If the error persists, please reach out to [email protected].",
  "title": "",
  "data": {
    "onyxData": [
      {
        "onyxMethod": "merge",
        "key": "transactions_5587980153775394500",
        "value": {
          "errors": {
            "1702638081170151": "An unexpected error occurred, please try again. If the error persists, please reach out to [email protected]."
          }
        }
      }
    ]
  },
  "htmlMessage": "",
  "onyxData": [
    {
      "onyxMethod": "merge",
      "key": "transactions_5587980153775394500",
      "value": {
        "errors": {
          "1702638081170151": "An unexpected error occurred, please try again. If the error persists, please reach out to [email protected]."
        }
      }
    }
  ],
  "requestID": "835e3010fe2e2e39-BOM"
}

[melvin-bot]

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

[MitchExpensify]

Does this need to be handled internally @c3024 ?

[c3024]

Yes, this needs to be internal.

[melvin-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]

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

[MitchExpensify]

@neil-marcellini, as the distance maestro, what do you think this error message should read as?

[melvin-bot]

@MitchExpensify @c3024 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!

[melvin-bot]

@MitchExpensify, @c3024 Eep! 4 days overdue now. Issues have feelings too...

[MitchExpensify]

Is this wave 5 @DylanDylann ?

[melvin-bot]

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

[mvtglobally]

Issue not reproducible during KI retests. (First week)

[melvin-bot]

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

[MitchExpensify]

@dylanexpensify* - Is this wave 5?

Friendly bump :)

[c3024]

@cead22 this needs to be dealt internally.

[melvin-bot]

@MitchExpensify @c3024 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]

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

[melvin-bot]

Triggered auto assignment to @aldo-expensify (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[MitchExpensify]

this needs to be dealt internally.

Reassigned the label to assign an internal engineer based on this comment from @c3024

[mvtglobally]

Issue not reproducible during KI retests. (Second week)

[aldo-expensify]

The issue has been identified in the backend and will be fixed by this PR: https://github.com/Expensify/Web-Expensify/pull/40462

[iwiznia]

Removed the $ from https://github.com/Expensify/Web-Expensify/pull/40462 because you need to update secure too

[aldo-expensify]

Web-S PR: https://github.com/Expensify/Web-Secure/pull/2627

[aldo-expensify]

Fix is in staging https://github.com/Expensify/Web-Expensify/pull/40462

[aldo-expensify]

Screen.Recording.2024-01-15.at.12.37.28.PM.mov

Confirmed that this has been fixed in staging