-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Improve signature request message #5711
Conversation
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
I have read the CLA Document and I hereby sign the CLA |
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.
Great PR. Do you think we should also add this to MessageSign
as well?
Message sign is encoded data, its is not needed there. |
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.
Nice 🙌
I've QAd the branch and when I click on Personal Sign I am seeing a crashing error saying mobile-personal-sign-regex.mp4 |
@seaona : I found that it was crashing in android, PR is updated with fix. |
The error is fixed now. Thank you @jpuri ⭐ I've realized that when we try to Verify the Signature, the verification fails and the address is not recovered. This happens only for that specific case that the original issue was reporting. For the rest of the cases the Verify Signature works fine. I didn't realize this is also happening with the Improve signature on Extension. It is a rare edge case but we might want to resolve it correctly too. In that case I can open a new issue for Extension. The error message is:
personal-sign-mobile-verify.mp4 |
The above issue it's been discussed internally if needs a fix or not. Not exclusive to this PR. |
Sanitising string on signature request pages
Ref: https://app.zenhub.com/workspaces/confirmations-6245e6e2348677001213b8d2/issues/gh/metamask/metamask-planning/306