Skip to content

[HOLD for payment 2024-07-24] [$250] Track distance - Incorrect distance is displayed on confirmation page when submitting to WS #42959

@kavimuru

Description

@kavimuru

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: 1.4.78-3
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 staging.new.expensify.com
  2. Go to self DM.
  3. Track a distance expense.
  4. Go to transaction thread of the distance expense.
  5. Take note of the distance.
  6. Return to the main chat.
  7. Click Share it with my accountant (or categorize it) from actionable whisper.
  8. Proceed to confirmation page.

Expected Result:

The distance in the confirmation page will be the same as the distance in the transaction thread because waypoints remain the same.

Actual Result:

The distance in the confirmation page is different. It shows a very short distance (0.01 km in my case).

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

Bug6498389_1717234236224.bandicam_2024-06-01_17-20-03-316.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01cae0e715bb61699d
  • Upwork Job ID: 1798854040827421683
  • Last Price Increase: 2024-06-13
  • Automatic offers:
    • situchan | Reviewer | 102737223
    • dominictb | Contributor | 102737226
Issue OwnerCurrent Issue Owner: @lschurr

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2ExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions