-
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 2023-10-23] [HOLD for payment 2023-10-23] [$500] Security - Error message displays briefly after reopening the 2FA step 2 page #28937
Comments
Job added to Upwork: https://www.upwork.com/jobs/~01c5525a081fe174f8 |
Triggered auto assignment to @alexpensify ( |
Bug0 Triage Checklist (Main S/O)
|
Triggered auto assignment to Contributor-plus team member for initial proposal review - @s77rt ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.Error message displays briefly after reopening the 2FA step 2 page What is the root cause of that problem?When we enter the wrong 2FA code, we will update the errors in the onyx account, and back to step 1 return to step 2, we still have errors in the onyx account until the function What changes do you think we should make in order to solve the problem?In here We should clear errors in account when we back to step 1
What alternative solutions did you explore? (Optional) |
ProposalPlease re-state the problem that we are trying to solve in this issueSecurity - Error message displays briefly after reopening the 2FA step 2 page What is the root cause of that problem?The root cause of the problem is that the error message is not being cleared when changing pages. The error message is stored in the account object and is not being reset when navigating away from the VerifyStep component. What changes do you think we should make in order to solve the problem?To solve the problem, we need to clear the error message when changing pages. This can be done by adding a cleanup function to the Here's the updated code:
By adding the cleanup function, Session.clearAccountMessages() will be called when the component is unmounted, effectively clearing the error message. This change should reset and remove the error message when changing pages in the Security section. ResultFix.mp4What alternative solutions did you explore? (Optional)None cc: @alexpensify @s77rt |
@DylanDylann Thanks for the proposal. Your RCA makes sense. The solution is mostly okay except that I think we should clear the error in the responsible page and not the component i.e. in |
@studentofcoding Thanks for the proposal. Your RCA is correct and the solution makes sense. 🎀 👀 🎀 C+ reviewed |
Triggered auto assignment to @grgia, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
Not overdue. @grgia #28937 (comment) |
I've reached out in chat |
📣 @s77rt 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app! |
📣 @studentofcoding 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
📣 @adeel0202 🎉 An offer has been automatically sent to your Upwork account for the Reporter role 🎉 Thanks for contributing to the Expensify app! |
It's ready to be review @s77rt |
🎯 ⚡️ Woah @s77rt / @studentofcoding, great job pushing this forwards! ⚡️ The pull request got merged within 3 working days of assignment, so this job is eligible for a 50% #urgency bonus 🎉
On to the next one 🚀 |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.84-10 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 2023-10-23. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
As a reminder, here are the bonuses/penalties that should be applied for any External 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:
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.84-10 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 2023-10-23. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
As a reminder, here are the bonuses/penalties that should be applied for any External 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:
|
|
Hi guys, as today is the date for the payment, please kindly proceed it, thanks! |
Here is the payment summary: @s77rt - Reviewer $750 Upwork Job: https://www.upwork.com/jobs/~01c5525a081fe174f8 *If applicable, the bonuses will be applied on the final payment Extra Notes regarding payment: There is an urgency bonus - #28937 (comment) |
Great work, everyone has now been paid via Upwork! |
@alexpensify The total here should be $750. I have refunded the $250. |
Thanks @s77rt -- it looks like I miscalculated the bonus amounts and I've updated the summary. |
Thanks for the payment @alexpensify, but yes it should be $750. How do I refund the remaining $250? (also Upwork already deducted $50 from the bonus, lol) |
@studentofcoding Open the contract page. Click the three dots button > Give a refund |
I appreciate your honesty here. I confirmed that all refunds have been sent via Upwork. Thank you! |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Action Performed:
Expected Result:
Error message is not displayed after reopening the 2FA step 2 page
Actual Result:
Error message is briefly displayed after reopening the 2FA step 2 page
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.78.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
Notes/Photos/Videos: Any additional supporting documentation
640eac02-0680-49b9-840e-b71eeb9e187d.MP4
4cf1cf6e-2a8a-4e29-9918-629a35898ec5.MP4
RPReplay_Final1696315393.MP4
Screen.Recording.2023-10-03.at.12.17.18.PM.mov
RPReplay_Final1696252437.MP4
Screen.Recording.2023-10-02.at.6.11.33.PM.mov
Recording.4876.mp4
Expensify/Expensify Issue URL:
Issue reported by: @adeel0202
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1696253182828299
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: