-
Notifications
You must be signed in to change notification settings - Fork 5.4k
fix(23804): unable to add QR code account #23903
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
|
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. |
|
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/socks@2.8.3 |
|
👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎ This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored. Ignoring: Next stepsTake a deeper look at the dependencyTake a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev. Remove the packageIf you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency. Mark a package as acceptable riskTo ignore an alert, reply with a comment starting with |
gantunesr
left a comment
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.
Dimiss approval
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #23903 +/- ##
========================================
Coverage 67.46% 67.46%
========================================
Files 1244 1244
Lines 48777 48777
Branches 12724 12724
========================================
Hits 32907 32907
Misses 15870 15870 ☔ View full report in Codecov by Sentry. |
Builds ready [6d909ed]
Page Load Metrics (469 ± 360 ms)
Bundle size diffs [🚀 Bundle size reduced!]
|
…ller version ini package.json.
|
@metamaskbot update-policies |
|
Policies updated |
Builds ready [eab6341]
Page Load Metrics (581 ± 414 ms)
Bundle size diffs [🚀 Bundle size reduced!]
|
benjisclowder
left a comment
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.
QA passed.
benjisclowder
left a comment
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.
QA passed
|
@metamaskbot update-policies |
|
Policies updated |
Builds ready [7f90d82]
Page Load Metrics (664 ± 492 ms)
Bundle size diffs [🚀 Bundle size reduced!]
|
benjisclowder
left a comment
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.
QA passed.
Builds ready [bffd110]
Page Load Metrics (794 ± 513 ms)
Bundle size diffs [🚀 Bundle size reduced!]
|
|
@SocketSecurity ignore-all The new author warnings are safe. We have approved those authors in the past, and ther are github employees and/or long time contributors to the npm ecosystem. The network access is necessary for make-fetch-happen to work, and that has been part of our dependency tree for a long time. |
Description
The connection via QR code on Hardware wallet is not proceeding past scanning the QR code. Functionality is working in the release version v11.13.1.
After debuggin the code and discover that the issue is caused by Keyring Controller upgraded to 13.0.0. and
#addQRKeyringfunction have bug to pass a empty accounts array as parameters to keyring, cause the Keystone MetamaskKeyring default properties all are undefined during deserialise() process.This fix patch the
@metamask/keyring-controllerto remove the empty array passed to KeyStone MetamaskKeyring so that all default properies in keyring will remain the same.Related issues
Fixes: #23804
Manual testing steps
Screenshots/Recordings
Before
Screen.Recording.2024-03-26.at.21.01.01.mov
After
Screen.Recording.2024-04-09.at.09.15.28.mov
Pre-merge author checklist
Pre-merge reviewer checklist