Skip to content

[HOLD for payment 2024-04-15] [$500] Distance - Unable to save second distance edit offline #38814

Closed

Description

@kbecciv

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.56-0
Reproducible in staging?: y
Reproducible in production?: n
Issue reported by: Applause - Internal Team

Action Performed:

  1. Go to staging.new.expensify.com.
  2. Go to workspace chat.
  3. Create a distance request with three waypoints.
  4. Go to request details page.
  5. Go offline.
  6. Click Distance.
  7. Drag and drop the waypoints and save it.
  8. Repeat Step 6 and 7.

Expected Result:

User will be able to save the second distance edit.

Actual Result:

User is unable to save the second distance edit.

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

Bug6423379_1711125466153.20240323_001712.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01b020e3127d156e8f
  • Upwork Job ID: 1772031538674204672
  • Last Price Increase: 2024-03-24
  • Automatic offers:
    • GandalfGwaihir | Contributor | 0

Activity

  1. github-actions commented on Mar 22, 2024

    @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.
  2. melvin-bot commented on Mar 22, 2024

    @melvin-bot

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

  3. kbecciv commented on Mar 22, 2024

    @kbecciv
    Author

    We think that this bug might be related to #wave-collect - Release 1

  4. nkdengineer commented on Mar 22, 2024

    @nkdengineer
    Contributor

    Proposal

    Please re-state the problem that we are trying to solve in this issue.

    User is unable to save the second distance edit.

    What is the root cause of that problem?

    We prevent the user save the distance if the transaction is loading.

    if (duplicateWaypointsError || atLeastTwoDifferentWaypointsError || hasRouteError || isLoadingRoute || isLoading) {
    setShouldShowAtLeastTwoDifferentWaypointsError(true);
    return;

    So in offline, after the first time we edit the distance, we can't edit this anymore.

    What changes do you think we should make in order to solve the problem?

    As the old edit distance flow, we should allow user saving the distance if we're offline event the transaction is loading

    if (duplicateWaypointsError || atLeastTwoDifferentWaypointsError || hasRouteError || isLoadingRoute || (isLoading && !isOffline)) {
        setShouldShowAtLeastTwoDifferentWaypointsError(true);
        return;
    }
    

    if (duplicateWaypointsError || atLeastTwoDifferentWaypointsError || hasRouteError || isLoadingRoute || isLoading) {
    setShouldShowAtLeastTwoDifferentWaypointsError(true);
    return;

    What alternative solutions did you explore? (Optional)

    NA

  5. ZhenjaHorbach commented on Mar 22, 2024

    @ZhenjaHorbach
    Contributor

    Looks like a regression from this PR
    #35302

  6. shubham1206agra commented on Mar 23, 2024

    @shubham1206agra
    Contributor

    Tagging @DylanDylann @cubuspl42 for visibility.

  7. srikarparsi commented on Mar 24, 2024

    @srikarparsi
    Contributor

    This looks external since editing the order of the points does work while offline when creating the request. Opening it up to see if there's any proposals before Monday.

  8. 48 remaining items

  9. mallenexpensify commented on Apr 12, 2024

    @mallenexpensify
    Contributor

    @GandalfGwaihir can you please accept the job and reply here once you have?
    https://www.upwork.com/jobs/~01b020e3127d156e8f

    Compensation is 50% of the job price, $250, because authoring a PR and testing wasn't involved.

  10. allgandalf commented on Apr 14, 2024

    @allgandalf
    Contributor

    @mallenexpensify accepted the offer thanks :)

  11. melvin-bot commented on Apr 15, 2024

    @melvin-bot

    Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO.

  12. removed
    Help WantedApply this label when an issue is open to proposals by contributors
    on Apr 16, 2024
  13. melvin-bot commented on Apr 16, 2024

    @melvin-bot

    📣 @GandalfGwaihir 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app!

    Offer link
    Upwork job
    Please accept the offer and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑‍💻
    Keep in mind: Code of Conduct | Contributing 📖

  14. mallenexpensify commented on Apr 16, 2024

    @mallenexpensify
    Contributor

    Contributor: @GandalfGwaihir paid $250 via Upwork

    Thanks!

  15. allgandalf commented on Apr 16, 2024

    @allgandalf
    Contributor

    I will decline the autogenerated offer by Melvin on Upwork, I was paid already, thanks for the paying @mallenexpensify :)

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

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionDailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions