-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[$250] Contact method - Main email doesn't get validated after inserting magic code #48527
Comments
Triggered auto assignment to @lschurr ( |
@lschurr FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors |
ProposalPlease re-state the problem that we are trying to solve in this issue.Contact method - Main email doesn't get validated after inserting magic code What is the root cause of that problem?Right here we return exit from the function if we have a pending contact meaning adding new contact App/src/pages/settings/Profile/Contacts/ValidateCodeForm/BaseValidateCodeForm.tsx Lines 190 to 195 in 562d7b4
What changes do you think we should make in order to solve the problem?We can just remove the return statement What alternative solutions did you explore? (Optional)N/A |
Job added to Upwork: https://www.upwork.com/jobs/~021831356985561814829 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @c3024 ( |
Hi @c3024! Could you review the proposal here when you get a chance? |
ProposalPlease re-state the problem that we are trying to solve in this issue.Main gmail account still considered to be unvalidated after getting magic code and validated using it What is the root cause of that problem?I don't think this is a bug, in Step 6, we're validating the ACTION to add secondary contact, not the (main) contact itself. It's like KYC/proving you're the one who made the action before actually verifying the contact method. I think the problem lies in the validate code prompt text that confused users, even the QA and contributors. We need to update it. What changes do you think we should make in order to solve the problem?Take Google for example, it just simply shows To do that, we can modify the message in
|
Their will require backend change to work |
MAking this weekly as its not that critical |
This is not overdue |
What changes do we need to make here? If you're adding a secondary login with an unvalidated primary, and we prompt to "prove it's you" by entering a magic code, we should validate the primary? |
focusing on higher priorities still |
low |
same |
@c3024, could you please retest if this is still happening? I think we might have made some changes to this flow |
Still happening.
primaryMagicCode.mp4 |
@c3024 thanks for verifying |
GBR is not displayed anymore as per this PR #49004 Screen_Recording_20241111_172256_Chrome.mp4 |
I am still seeing the GBR now on staging. 🤔 Screen.Recording.2024-11-12.at.7.45.52.PM.movThe GBR is not there on signup but some data from backend seems to make the GBR appear after validating the primary account through the "Add secondary contact method" flow. |
low |
still in progress, been focusing on app deploy this week |
low |
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: 9.0.28-0
Reproducible in staging?: Y
Reproducible in production?: Y
Email or phone of affected tester (no customers): testpayment935@gmail.com
Issue reported by: Applause Internal Team
Action Performed:
Expected Result:
After validating the main email account the GBR should disappear from the main email and the main email should now be considered as validated
Actual Result:
Main gmail account still considered to be unvalidated after getting magic code and validated using it
Workaround:
Unknown
Platforms:
Screenshots/Videos
Bug6592205_1725395703195.Screen_Recording_20240903_233032_Chrome.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @mountinyThe text was updated successfully, but these errors were encountered: