-
Notifications
You must be signed in to change notification settings - Fork 987
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
support PUK and seed recovery during onboarding #12955
Conversation
78% of end-end tests have passed
Failed tests (15)Click to expand
Passed tests (53)Click to expand |
@bitgamma thanks for this fix! Steps:
Actual result: Expected result: video_2021-12-27_12-59-37.mp4 |
@qoqobolo that was actually on purpouse. Thing is that the recovery with workflow procedure overwrites all flow information so we don't know what the user was doing. Making the onboarding finishing would be possible, but it would make the already intricate logic even more intricate (short of doing some big refactoring). Since this seems to be a very edge case, bringing the user to the start so they can do whatever they wanted to do seemed the best thing option. What do you think? |
@bitgamma yeah, I suspected that this was done on purpose, there's no doubt now :) Thanks for the explanation! |
13% of end-end tests have passed
Failed tests (13)Click to expand
Passed tests (2)Click to expand
|
Signed-off-by: Michele Balistreri <[email protected]>
Fixes #12938.
Note for QA: please test for regressions in other scenarios where puk/reset recovery is used