You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[HOLD for payment 2023-10-13] [$500] Login - Enter key does not submit recovery code #28092
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
Identify the pull request that introduced this issue and revert it.
What changes do you think we should make in order to solve the problem?
Add that callback: onSubmitEditing={validateAndSubmitForm}
What alternative solutions did you explore? (Optional)
Additionally, pass pressOnEnter={props.isUsingRecoveryCode} to Button if we'd like to submit on enter even when input is not focused. There will not be duplicated call thanks to isLoading check here.
I'm able to reproduce. At first I thought there was no error because I clicked on the Sign In after entering the incorrect recovery code. As the instructions outline, you need to use the "Enter" button to reproduce the issue.
I'm not sure this qualifies as a deploy blocker. The user can still enter an incorrect code, just not in their preferred way by clicking or tapping "Enter". @tylerkaraszewski do you view this as a deploy blocker?
I don't think this is a DB because user still can use the app.
Please re-state the problem that we are trying to solve in this issue.
Login - Enter key does not submit recovery code
What is the root cause of that problem?
Currently we didn't pass the pressOnEnter props to our submit button here, so when we press enter, nothing happen because we're using TextInput for recovery code (others used MagicCodeInput).
📣 @abdulrahuman5196 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app!
Offer link Upwork job
Please accept the offer and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑💻
Keep in mind: Code of Conduct | Contributing 📖
changed the title [-][$500] Login - Enter key does not submit recovery code[/-][+][HOLD for payment 2023-10-13] [$500] Login - Enter key does not submit recovery code[/+]on Oct 6, 2023
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.78-4 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-13. 🎊
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.
External issue reporter
Contributor that fixed the issue
Contributor+ that helped on the issue and/or PR
For reference, here are some details about the assignees on this 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:
[@abdulrahuman5196] The PR that introduced the bug has been identified. Link to the PR:
[@abdulrahuman5196] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
[@abdulrahuman5196] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
[@abdulrahuman5196] Determine if we should create a regression test for this bug.
[@abdulrahuman5196] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
[] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
Activity
melvin-bot commentedon Sep 24, 2023
Triggered auto assignment to @tjferriss (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.melvin-bot commentedon Sep 24, 2023
Bug0 Triage Checklist (Main S/O)
Platformsin OP are ✅)OSBotify commentedon Sep 24, 2023
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
StagingDeployCashdeploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:melvin-bot commentedon Sep 24, 2023
Triggered auto assignment to @tylerkaraszewski (
Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.mkhutornyi commentedon Sep 24, 2023
Proposal
Please re-state the problem that we are trying to solve in this issue.
Pressing Enter key does nothing on login recovery code page
What is the root cause of that problem?
On press enter key, TextInput's
onSubmitEditingcallback is called but it's not implemented here:App/src/pages/signin/ValidateCodeForm/BaseValidateCodeForm.js
Lines 298 to 308 in 4ea4a55
What changes do you think we should make in order to solve the problem?
Add that callback:
onSubmitEditing={validateAndSubmitForm}What alternative solutions did you explore? (Optional)
Additionally, pass
pressOnEnter={props.isUsingRecoveryCode}to Button if we'd like to submit on enter even when input is not focused. There will not be duplicated call thanks toisLoadingcheck here.tjferriss commentedon Sep 25, 2023
I'm able to reproduce. At first I thought there was no error because I clicked on the Sign In after entering the incorrect recovery code. As the instructions outline, you need to use the "Enter" button to reproduce the issue.
I'm not sure this qualifies as a deploy blocker. The user can still enter an incorrect code, just not in their preferred way by clicking or tapping "Enter". @tylerkaraszewski do you view this as a deploy blocker?
hungvu193 commentedon Sep 25, 2023
Proposal
I don't think this is a DB because user still can use the app.
Please re-state the problem that we are trying to solve in this issue.
Login - Enter key does not submit recovery code
What is the root cause of that problem?
Currently we didn't pass the
pressOnEnterprops to our submit button here, so when we press enter, nothing happen because we're usingTextInputfor recovery code (others used MagicCodeInput).App/src/pages/signin/ValidateCodeForm/BaseValidateCodeForm.js
Lines 379 to 388 in 19f93db
What changes do you think we should make in order to solve the problem?
We should add
pressOnEnterto our SignIn button incase we're using recovery code:What alternative solutions did you explore? (Optional)
N/A
25 remaining items
melvin-bot commentedon Sep 29, 2023
📣 @abdulrahuman5196 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app!
Offer link
Upwork job
Please accept the offer and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑💻
Keep in mind: Code of Conduct | Contributing 📖
MonilBhavsar commentedon Sep 29, 2023
This was regression from original PR, so updating assignees
[-][$500] Login - Enter key does not submit recovery code[/-][+][HOLD for payment 2023-10-13] [$500] Login - Enter key does not submit recovery code[/+]melvin-bot commentedon Oct 6, 2023
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Oct 6, 2023
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.78-4 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-13. 🎊
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:
melvin-bot commentedon Oct 6, 2023
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:
tjferriss commentedon Oct 6, 2023
Payment Summary:
alitoshmatov commentedon Oct 7, 2023
@tjferriss This was a follow up PR and does not require payment - #22335 (comment)
abdulrahuman5196 commentedon Oct 7, 2023
@tjferriss No payment needed here as discussed - #22335 (comment)
We can close this issue directly.
MonilBhavsar commentedon Oct 9, 2023
Yes, thanks everyone! We can close this one 👍