Skip to content

Distance - Duplicate waypoints error is shown while creating distance expense offline #75773

Closed

Description

@lanitochka17

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.2.62-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: https://test-management.browserstack.com/projects/2219752/test-runs/TR-2119/folder/13176744/47211684/1030269711
Email or phone of affected tester (no customers): Slottwo1@gmail.com
Issue reported by: Applause - Internal Team

Action Performed:

  1. Launch app
  2. Open workpace chat
  3. Tap plus icon - track distance
  4. Turn off internet
  5. Enter a waypoint as start
  6. Enter different waypoint as stop

Expected Result:

Duplicate waypoints error must not be shown while creating distance expense offline

Actual Result:

Duplicate waypoints error is shown while creating distance expense offline

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop
Platforms Tested: On which of our officially supported platforms was this issue tested:
  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence
Bug7010241_1763738348098.Screenrecorder-2025-11-21-20-48-09-678.mp4

View all open jobs on GitHub

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Nov 21, 2025
  2. melvin-bot commented on Nov 21, 2025

    @melvin-bot

    Triggered auto assignment to @strepanier03 (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.

  3. melvin-bot commented on Nov 21, 2025

    @melvin-bot

    Triggered auto assignment to @jasperhuangg (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  4. melvin-bot commented on Nov 21, 2025

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  5. github-actions commented on Nov 21, 2025

    @github-actions
    Contributor

    👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  6. jasperhuangg commented on Nov 21, 2025

    @jasperhuangg
    Contributor

    This one seems suspicious: #75116, although I'm not sure that this needs to block deploy since it's such an edge case.

  7. jasperhuangg commented on Nov 21, 2025

    @jasperhuangg
    Contributor

    Just tried reverting #75116 locally and that seems to fix the issue. I don't think a revert is necessary here since it's so minor but @bernhardoj please address a fix in a followup thanks!

  8. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Nov 21, 2025
  9. bernhardoj commented on Nov 23, 2025

    @bernhardoj
    Contributor

    Raised a follow up PR!

  10. melvin-bot commented on Dec 17, 2025

    @melvin-bot

    This issue has not been updated in over 15 days. @strepanier03, @jasperhuangg 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!

  11. jasperhuangg commented on Dec 17, 2025

    @jasperhuangg
    Contributor

    @DylanDylann are we good to close this out too based on #76331 (comment)?

  12. DylanDylann commented on Dec 17, 2025

    @DylanDylann
    Contributor

    Yesss

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.EngineeringMonthlyKSv2ReviewingHas a PR in review

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions