-
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
[$1000] Request Money – The address input lacks a red outline or error message when an incomplete IOU is created offline #32405
Comments
Triggered auto assignment to @conorpendergrast ( |
Job added to Upwork: https://www.upwork.com/jobs/~01bc96448abc5e7e68 |
Bug0 Triage Checklist (Main S/O)
|
Triggered auto assignment to Contributor-plus team member for initial proposal review - @ntdiary ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.Request Money – The address input lacks a red outline or error message when an incomplete IOU is created offline What is the root cause of that problem?We have 2 problems here:
To show the error messages, we have to call validate function, but this function is just called when users press App/src/pages/iou/WaypointEditor.js Lines 216 to 217 in d2056af
When users go offline, we allow them to write any addresses, so BE will validate them then return the correct latitude and longitude. If the addresses are invalid, BE will return the error ->
In App/src/components/DistanceRequest/index.js Lines 198 to 199 in d2056af
we did not pass What changes do you think we should make in order to solve the problem?We need to define the new property in waypoint like In
then set isChecking to false for all waypoints in successData of
In
App/src/components/DistanceRequest/index.js Line 198 in d2056af
ResultScreen.Recording.2023-12-21.at.11.40.36.mp4What alternative solutions did you explore? (Optional) |
Reproduced on iOS (SafarI). @ntdiary two proposals for your review above! |
I'd suggest avoid submitting these with the "help wanted" label then |
@chiItepin, ah, is there any misunderstanding here? 😂 As my bandwidth is not sufficient, @shubham1206agra will take over as C+ to review all the proposals, to avoid delays in the review process. 😄 |
@conorpendergrast Do we also need to show a red brick indicator in the Distance field on the request details page? |
Being handled in #29783 |
@tienifr Can you point to the code where |
TBH, I am not sure this is worth fixing after #29783 is done, as we will show red dot already on 2 pages |
@chiItepin Your RCA is not right. We do not disable the request flow if the user is offline |
I think we should have some indicator of which address has a problem. So that we can fix the address. |
@shubham1206agra I see, but how is the user able to look for an address if the user is offline and there are no autocomplete items (recently added addresses)? |
By manually entering the address and proceed with that |
Hmm, I thought the app needed to sanitize the address, without being online and without autocomplete items, the user could literally enter anything thus, the map is not recognizing the address if this is the case which is what the reporter described though, map not being picked up due to invalid address, no? |
@shubham1206agra We update pendingFields here when users change the waypoints I also updated it in my proposal. Thanks
|
We clear Line 760 in 3827a9c
|
@conorpendergrast I am OOO right now. I will review this on 30th |
Sounds good, thanks! |
It's not the 30th yet! That's tomorrow |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
Also double-checking which wave this should be part of |
@conorpendergrast I was able to repro your steps behavior but not the original behavior. I think if the backend is giving an error code of failure while making a request, then it should not be allowed at all. Can you confirm the ideal offline behavior with vague waypoints internally? As BE may have removed support of the same. |
@shubham1206agra can do, thanks for moving this along! |
Ok, well, good news! Yes, it is expected that you can create a request like this. Quoting @neil-marcellini :
So, we'll close this out in favour of #22719. That covers this scenario well! Thank you for your time everyone! |
@conorpendergrast Can I get partial compensation in this case? As I have tried to move this along for a long time by doing quite back and forth with a proposal. |
@shubham1206agra I can put that forward! What do you feel is a fair partial compensation? |
250 is fine for me. |
Ok, let me reopen to discuss that internally! |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
Still discussing internally |
@shubham1206agra we've agreed with the 25% based on the work here. I've sent you the offer now |
@conorpendergrast Accepted |
And paid! Thanks @shubham1206agra |
Payouts due:
Upwork job is here. |
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.7.0
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:
Expected Result:
The address input has a red outline and below it is an error message like “Unable to find the location for this address. Please edit the address and try again
Actual Result:
The address input lacks a red outline or error message when an incomplete IOU is created offline
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6298369_1701504006546.Address_input_has_no_red_outline.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: