[$250] Expense - Unable to add a third waypoint when editing distance expense
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: 9.0.61-0 Reproducible in staging?: Y Reproducible in production?: Y If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y Issue reported by: Applause Internal Team
Action Performed:
- Open the Expensify app.
- Open any workspace chat.
- Tap on the "+" button and select "Submit Expense"
- Tap on "Distance"
- Add "123 Melrose St" as start waypoint and "124 E 14th Street" as end waypoint.
- Open the just created expense report.
- Tap on "Distance"
- Tap on "Add Stop" and add a valid third waypoint, for example: "124 W 60th street"
- Verify the new waypoint is added and the expense information is updated.
Expected Result:
The user should be able to add a third waypoint to a distance expense while editing it and all the expense information should be updated correctly.
Actual Result:
"No route found through waypoints" message is displayed everytime the user tries to add a valid third waypoint while editing a distance expense.
Workaround:
Unknown
Platforms:
- [x] Android: Standalone
- [x] Android: HybridApp
- [x] Android: mWeb Chrome
- [ ] iOS: Standalone
- [ ] iOS: HybridApp
- [ ] iOS: mWeb Safari
- [x] MacOS: Chrome / Safari
- [ ] MacOS: Desktop
Screenshots/Videos
https://github.com/user-attachments/assets/0f0dd9bc-92b1-4370-b3f1-c59af9bfb1a3
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~021857394643329620491
- Upwork Job ID: 1857394643329620491
- Last Price Increase: 2024-12-06
Issue Owner
Current Issue Owner: @alitoshmatov
Triggered auto assignment to @zanyrenney (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.
Shoot, yeah we should be able to have this.
Job added to Upwork: https://www.upwork.com/jobs/~021857394643329620491
Triggered auto assignment to Contributor-plus team member for initial proposal review - @alitoshmatov (External)
Seems like BE error, Api - "GetRoute" returns this error
@zanyrenney, @alitoshmatov Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
@zanyrenney, @alitoshmatov Eep! 4 days overdue now. Issues have feelings too...
π£ It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? πΈ
@zanyrenney, @alitoshmatov 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it!
Making internal since this is a BE error, making weekly also
@zanyrenney @alitoshmatov 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!
π£ It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? πΈ
π£ It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? πΈ
No internal engineer assigned yet
@zanyrenney @alitoshmatov this issue is now 4 weeks old, please consider:
- Finding a contributor to fix the bug
- Closing the issue if BZ has been unable to add the issue to a VIP or Wave project
- If you have any questions, don't hesitate to start a discussion in #expensify-open-source
Thanks!
π£ It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? πΈ
π£ It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? πΈ
π£ It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? πΈ
Issue not reproducible during KI retests. (First week)
This issue has not been updated in over 15 days. @zanyrenney, @alitoshmatov eroding to Monthly issue.
P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!
π£ It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? πΈ
π£ It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? πΈ
π£ It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? πΈ
Issue not reproducible during KI retests. (Second week)
π£ It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? πΈ
π£ It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? πΈ
π£ It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? πΈ
Not reproducible, closing!