-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[HOLD for payment 2024-06-06] [$250] Android - Distance - Waypoint does not change position correctly by dragging #40105
Comments
Triggered auto assignment to @rlinoz ( |
👋 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:
|
We think that this bug might be related to #wave-collect - Release 1 |
Starting an android build to check what is happening |
Having a really hard time building it, the build is getting fixed here #40102 |
Latest app is crashing when opening distance request page Hmm, swtiching tabs fixed it? |
Can reproduce though, not sure what broke it yet |
This is not a backend issue and it is almost EOD for my, I am opening this for help. |
Job added to Upwork: https://www.upwork.com/jobs/~010257ce95cba77cc8 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @ishpaul777 ( |
Thinking more about this, I don't think it needs to be a blocker, the functionality still works (the start/stop are swapped and the map preview is updated) and it is working as intended in all other platforms. Gonna go ahead and remove the label. |
Triggered auto assignment to @jliexpensify ( |
@ishpaul777, PR ready for review. |
This issue has not been updated in over 15 days. @rlinoz, @jliexpensify, @Krishna2323, @ishpaul777 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! |
we are actively working on the PR #41378, sorry for no updates on issue 🙇 |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.77-11 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2024-06-06. 🎊 For reference, here are some details about the assignees on this issue:
|
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
Payment Summary
Just waiting on checklist |
Bumping @ishpaul777 for the checklist! |
Here's a new Upworks job because the previous one was closed automatically. Please accept invites @ishpaul777 and @Krishna2323 |
I'll fill out checklist today. |
Bump @ishpaul777 to accept offer + complete checklist |
[@ishpaul777] The PR that introduced the bug has been identified. Link to the PR: #28618 Regression Test Proposal
Expected Result:The waypoint sequence will now be C, A, B. Do we 👍 or 👎 ? |
Sorry i left early yesterday, Accepted offer! |
Awesome, cheers - all paid and job closed. |
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.62-2
Reproducible in staging?: y
Reproducible in production?: n
Issue reported by: Applause - Internal Team
Action Performed:
Expected Result:
The waypoint sequence will now be C, A, B.
Actual Result:
The waypoint sequence is B, C, A. The "Start" waypoint is in the middle instead of at the top after dragging the distance.
Workaround:
n/a
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6445791_1712835794464.Screen_Recording_20240411_194116_New_Expensify.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @jliexpensifyThe text was updated successfully, but these errors were encountered: