Skip to content
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

cherrypick: User should be re-directed to old designs when signing using QR wallet #13168

Merged
merged 1 commit into from
Jan 24, 2025

Conversation

jpuri
Copy link
Contributor

@jpuri jpuri commented Jan 24, 2025

Description

Fix signature sining using QR wallet, user should be re-directed to old flows.

Related issues

Fixes: https://github.com/MetaMask/MetaMask-planning/issues/4013

Manual testing steps

  1. Sign signature request using keystone wallet
  2. You should see old signature page

Screenshots/Recordings

TODO

Pre-merge author checklist

Pre-merge reviewer checklist

  • I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
  • I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

…wallet (#13145)

## **Description**

Fix signature sining using QR wallet, user should be re-directed to old
flows.

## **Related issues**

Fixes: MetaMask/MetaMask-planning#4013

## **Manual testing steps**

1. Sign signature request using keystone wallet
2. You should see old signature page

## **Screenshots/Recordings**
TODO

## **Pre-merge author checklist**

- [X] I’ve followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [X] I've completed the PR template to the best of my ability
- [X] I’ve included tests if applicable
- [X] I’ve documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [X] I’ve applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

## **Pre-merge reviewer checklist**

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.
@jpuri jpuri added the team-confirmations Push issues to confirmations team label Jan 24, 2025
@jpuri jpuri requested a review from a team as a code owner January 24, 2025 13:36
Copy link
Contributor

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.

@jpuri jpuri added the Run Smoke E2E Triggers smoke e2e on Bitrise label Jan 24, 2025
Copy link
Contributor

github-actions bot commented Jan 24, 2025

https://bitrise.io/ Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: aa9fbe0
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/125a3061-239d-43b7-a384-f644b3a3d6b0

Note

  • You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

Tip

  • Check the documentation if you have any doubts on how to understand the failure on bitrise

@jpuri jpuri merged commit ad79a6b into release/7.39.0 Jan 24, 2025
39 of 40 checks passed
@jpuri jpuri deleted the qr_wallet_signing_fix branch January 24, 2025 14:07
@github-actions github-actions bot locked and limited conversation to collaborators Jan 24, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Run Smoke E2E Triggers smoke e2e on Bitrise team-confirmations Push issues to confirmations team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants