-
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 App#20404] 2 factor authentiaction code dissappear when switch to small screen #20611
Comments
Triggered auto assignment to @MitchExpensify ( |
Bug0 Triage Checklist (Main S/O)
|
ProposalPlease re-state the problem that we are trying to solve in this issue.Two factor auth code disappear when change the screen size What is the root cause of that problem?When users press
So we clear recoveryCodes without the logic to fetch it again
What changes do you think we should make in order to solve the problem?We should move this function
like what DisablePage component did with Session.toggleTwoFactorAuth(false); So when the component is mounted, we can fetch recoveryCodes again
|
Switching to weekly while on hold 👍 |
On hold |
Coming from a duplicate issue of this: #21803 ProposalPlease re-state the problemRecovery codes are cleared on resize. What is the root cause of that problem?When we resize the page, the whole screen gets remounted (a feature of the new architecture). App/src/pages/settings/Security/TwoFactorAuth/CodesPage.js Lines 53 to 57 in 4379e6d
And due to the above code, when the component unmounts, it clears the codes. What changes do you think we should make to solve this problem?Instead of clearing the codes on unmount, we can clear them when the navigation shifts focus from the screen. This way we can clear the codes when the user is not seeing them and also prevent this issue. useEffect(() => {
if (props.isFocused) {
return;
}
TwoFactorAuthActions.clearTwoFactorAuthData();
}, [props.isFocused]); What other approach did you explore?None |
Looks like something related to As a reminder, please make sure that all proposals are not workarounds and that any and all attempt to fix the issue holistically have been made before proceeding with a solution. Proposals to change our Feel free to drop a note in #expensify-open-source with any questions. |
Still on hold for #20404 but progress is being made there! |
Still on hold but PRs are being drafted in the related issue! 🚀 #20404 |
It does, that PR should resolve this issue 🤝 |
🤝 |
Still on hold for #20404 |
Same |
Same |
Whoop! This was resolved in #20404 |
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:
Expected Result:
Recovery codes still display
Actual Result:
Recovery codes disappear
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.26-1
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-06-07.at.15.42.20.mov
Recording.946.mp4
Expensify/Expensify Issue URL:
Issue reported by: @dukenv0307
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1686127296080609
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: