-
-
Notifications
You must be signed in to change notification settings - Fork 219
fix: confusing error message when using wrong password #5627
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
Conversation
@metamaskbot publish-preview |
Preview builds have been published. See these instructions for more information about preview builds. Expand for full list of packages and versions.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Explanation
When calling
submitPassword
with the wrong password, a confusing error is shown instead ofIncorrect password
. This is due to the recently added metadata length check in#restoreSerializedKeyrings
, which doesn't match the correct behavior whenisUnlocked = true
.We can move the metadata length check to
#unlockKeyrings
, so that it will be skipped everytime the controller is lockedReferences
Changelog
Changelog updated in the PR
Checklist