-
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
[$500] Request money - Distance - Next button enabled when map is pending - offline #27269
Comments
Triggered auto assignment to @sophiepintoraetz ( |
Bug0 Triage Checklist (Main S/O)
|
Job added to Upwork: https://www.upwork.com/jobs/~01d98cf61c3038fc39 |
Current assignee @sophiepintoraetz is eligible for the External assigner, not assigning anyone new. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @peterdbarkerUK ( |
We're going to update |
It is expected considering we fetch the route in backend if the frontend is not rendering the map (offline behaviour) |
@b4s36t4 Mahesh - you're referring to this issue, yes? |
Yes. |
To fix this web can inser a check state when map Is loaded and the next button disabled until map Is finished. |
📣 @rokko! 📣
|
Contributor details |
✅ Contributor details stored successfully. Thank you for contributing to Expensify! |
Current assignee @sophiepintoraetz is eligible for the External assigner, not assigning anyone new. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @sobitneupane ( |
Yup, I think we should hold for this issue #27045 - what do you think @sobitneupane? |
@sophiepintoraetz I think we should disable the button when user if offline. I am not sure but I believe it requires response from the server to get the amount. Can you confirm if this problem can still be replicated? I'm not able to reproduce it on my side. |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
Need to replicate the issue - so hold fire, Melvin! |
Still need to find time to replicate the bug and test - will look at this on Monday. |
Still need to reproduce. |
@sobitneupane @sophiepintoraetz 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? 💸 |
@sobitneupane, @sophiepintoraetz Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
ProposalPlease re-state the problem that we are trying to solve in this issue.The next button is enabled on offline mode when there are two valid waypoints. What is the root cause of that problem?The issue comes from the The code also assumes that you won't be able to get valid points while offline, which is not true, we can still access the cached suggestions from Google Autocomplete. App/src/components/DistanceRequest.js Line 293 in 52f0e3c
The issue is then replicable on all devices, using the following steps
Notice the button is now enabled. What changes do you think we should make in order to solve the problem?We need to enforce the check by using
map-issue.mp4What alternative solutions did you explore? (Optional)N/A |
Checking with @jliexpensify here |
I tried to reproduce this one exactly, but my amount says I am currently on v.75 and the report is .68, and the behaviour seems to follow what's in #27045 - i.e. the |
Agreed - thank you @jliexpensify! Out of curiosity, what happens when you do click next? Thanks for that find, I'm going to close out this issue as the bug is not intended behaviour. |
From memory, a distance request gets created but it's incomplete (i.e. there's no map and it says TBD) |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Make sure to have few waypoints already chosen in distance pages.
Expected Result:
On Pending maps, Next button should be disabled. On enabling the button, distance is calculated as 0, and user can make requests too.
Actual Result:
Next button enabled when map is pending
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: v1.3.68-12
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
Notes/Photos/Videos: Any additional supporting documentation
Screen.Recording.2023-09-08.at.11.01.22.PM.mov
Screen_Recording_20230912_192005_New.Expensify.mp4
Expensify/Expensify Issue URL:
Issue reported by: @ashimsharma10
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1694193245534799
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: