-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
[Pay on 6/18] When setting an unacceptable password the error message doesn't fit user's expectation #1517
Comments
Triggered auto assignment to @koswalto ( |
Triggered auto assignment to @flodnv ( |
Triggered auto assignment to @thienlnam ( |
Sorry, went to unassign myself but tricked Melvin in the process |
Could we get a copy for this please? @Expensify/marketing Something to indicate that the entered password does not meet the specified requirements |
Ah, I think you're looking to add the "Waiting for copy" label. I'll do that and it should auto-assign one of us from the Marketing Content team. Thanks! |
Oh weiiiiird it's not in the this repo. I'll take this one! Gimme a few. |
What qualifies a password as "not acceptable" on our end? We should basically be telling them two things (1) what happened that caused the error and (2) what they can do to resolve it. Hope this helps, thank you! |
@jamesdeanexpensify Thanks for taking this! It looks like our current requirements for a, acceptable password is that
|
Can it contain special characters, or only alphanumeric? |
ooh, i opened an issue for this a while back with copy for what we need to say for the reqs/ what we should be checking for: https://github.com/Expensify/Expensify/issues/149016 (basically, we should: show reqs from that start, then do front end validation so that we don't make the API call to set the password if the user's entry doesn't meet reqs, and then if there's a different error from the API, show the "friendly" API error text) (reqs being)
|
Oh awesome @sylveawong! Thanks for that - I copied the requirements into the issue and we'll just make this the external issue |
@anthony-hull would you like to work on this issue? If so the job in Upwork will pay $250 and their will be a $150 bonus for proposing the issue (you need to fix the issue in order to get the bonus). @koswalto assigned back to you, once we here back from @anthony-hull, can you create the Upwork job then hire @anthony-hull if he wants the job? |
I'm not working on contributor issues @mallenexpensify -- I just did my triage so I'm unassigning myself here 👍 |
Sorry about that @koswalto , I jumped the gun |
Hi team, yes I would like to work on this issue thank you for getting back to me! |
Triggered auto assignment to @puneetlath ( |
Is the job not already created? I've applied to this one. |
Ooops, good catch @anthony-hull , I forgot the Upwork job was already created :ohnothing: |
I'm happy to start. |
Hired @anthony-hull in Upwork, you're all set to start! |
Hi @anthony-hull do you have an update to provide? Anything you're waiting on from us? |
Hey sorry team. I have been ill over the past week. I have everything I need at the moment. I've started work on this and will provide an update later today. |
cc @Expensify/design for UX/UI feedback |
I wonder if a simpler approach would be to always keep the |
sure. What colour should it be when the user has satisfied the requirements? |
@anthony-hull I imagine that it can stay red until the user hits 'Set Password' and if it is valid then they should move on to the next screen |
Ohh I see what you mean - my bad I didn't realize that there was also another error field for confirming the password. In that case I think it makes sense if it goes back to the original color if the requirements were met. I'm going to fallback to @shawnborton for this one though. The changes are looking good though, could you open up a PR and tag me on it? We'll work on any changes from that |
Yeah sure I'll put a draft PR in |
Can you make the small hint text under the input use For the second input, I don't think it makes sense to immediately show a "Passwords must match" error - the user hasn't even had a chance to type the password at that point. Can we wait until they are done typing to validate the field, and then show the error if they don't match? |
Thanks for the feedback @shawnborton . I've made the changes you suggested. |
Navigate to here: |
I think it would be a good idea to re-use this component for the reset password page to improve the UX of the password rules there as well. |
Paid in Upwork with bonus for reporting the issue. Thanks @anthony-hull ! |
Platform - version:
Web
Action Performed (reproducible steps):
trigger password reset
make sure you're logged out
navigate to here: http://expensify.cash/#/setpassword/[code here]
make sure you have credentials.login key set to your email address in local storage
send a weak password
Expected Result:
An error that makes sense to the user's action and context
Requirements to be shown:
Actual Result:
message is:
However to a user's perspective they have only entered one password. This error doesn't make sense to me from that perspective.
Notes/Photos/Videos:
Logs - JS/Android/iOS (if applicable):
{"code":666,"jsonCode":402,"type":"Expensify\Libs\Error\ExpError","UUID":"03579dd0-476e-4865-b90b-371af0881280","message":"Passwords provided are not acceptable","title":"Bad password","data":[],"htmlMessage":"","requestID":"08592ec61d000042694e958000000001"}
The text was updated successfully, but these errors were encountered: