fix: 9108 Keystone QR code can't send asset transaction#9185
fix: 9108 Keystone QR code can't send asset transaction#9185dawnseeker8 merged 5 commits intomainfrom
Conversation
…oller to prevent the version mismatch issue.
|
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/@keystonehq/metamask-airgapped-keyring@0.3.0, npm/@keystonehq/ur-decoder@0.6.1 |
|
|
|
@dawnseeker8 Could you pull from main? Bitrise test is also failing |
|
@dawnseeker8 will this also work for swaps on hw account? Can you confirm? |
i have done the pull again in this PR. and all e2e tests has passed now. |
|
|
|
Tested on iPhone 13 using iOS 17.4.1 and Samung S21 using Android 14. RPReplay_Final1712826537.MP4 |
|
@chrisleewilcox confirming that the swap transaction works on hw account. RPReplay_Final1712827138.MP4 |
|
More than one release label on PR. Keeping the lowest one (release-7.20.0) on PR and removing other release labels (release-7.21.0). |




Description
This PR fix the #9108 issue,
The keystone relative library used in MM mobile is too old and didnt match the version used in keyring-controller 8.0.1. this PR will upgrade those old keystonehq libraries (try to use as new version as possible) to resolve those keystone QR relative issue.
Related issues
Fixes: #9108
Manual testing steps
Scenario: Send using HW account
GIVEN I have Sepolia Test Network selected
AND I have hardware wallet account selected
WHEN I send assets
THEN assets are successfully sent (FAIL: error shown on Confirm screen)
AND send transaction is properly shown on all transactions screen
Screenshots/Recordings
Before
Screen.Recording.2024-04-01.at.1.40.50.PM.mov
After
248_1712734345.mp4
Pre-merge author checklist
Pre-merge reviewer checklist