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

chore(runway): cherry-pick fix: Fix send flow deeplinks #13014

Merged
merged 1 commit into from
Jan 15, 2025

Conversation

runway-github[bot]
Copy link
Contributor

@runway-github runway-github bot commented Jan 15, 2025

Description

This PR aims to fix deeplinks using Send flow.

Related issues

Fixes: #12689

Manual testing steps

  1. Open safari/chrome in the testing device - navigate
    https://metamask.github.io/metamask-deeplinks/
  2. Click "Payment Request" then "Eth Payment"
  3. Fill the form - you dont need to put chain id
  4. Click "Generate url"
  5. Click generated url
  6. See that it opens send flow page

Screenshots/Recordings

Simulator.Screen.Recording.-.iPhone.13.Pro.-.2025-01-13.at.22.01.50.mp4

Before

After

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. 249e035

<!--
Please submit this PR as a draft initially.
Do not mark it as "Ready for review" until the template has been
completely filled out, and PR status checks have passed at least once.
-->

## **Description**

<!--
Write a short description of the changes included in this pull request,
also include relevant motivation and context. Have in mind the following
questions:
1. What is the reason for the change?
2. What is the improvement/solution?
-->

This PR aims to fix deeplinks using `Send` flow.

## **Related issues**

Fixes: #12689

## **Manual testing steps**

1. Open safari/chrome in the testing device - navigate
https://metamask.github.io/metamask-deeplinks/
2. Click "Payment Request" then "Eth Payment"
3. Fill the form - you dont need to put chain id
4. Click "Generate url"
5. Click generated url 
6. See that it opens send flow page

## **Screenshots/Recordings**

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->



https://github.com/user-attachments/assets/ec6324b0-188f-4079-90ee-3d30b7e6056d



### **Before**

<!-- [screenshots/recordings] -->

### **After**

<!-- [screenshots/recordings] -->

## **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.
@runway-github runway-github bot requested a review from a team as a code owner January 15, 2025 20:03
@sethkfman sethkfman added the Run Smoke E2E Triggers smoke e2e on Bitrise label Jan 15, 2025
Copy link
Contributor

github-actions bot commented Jan 15, 2025

https://bitrise.io/ Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 4d96e7c
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/2b3079c7-3569-42de-8f6c-9ac034dfb7e8

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

@sethkfman sethkfman added team-confirmations Push issues to confirmations team rc-cherry-picked labels Jan 15, 2025
@sethkfman sethkfman merged commit c4af1f5 into release/7.38.0 Jan 15, 2025
35 of 39 checks passed
@sethkfman sethkfman deleted the runway-cherry-pick-7.38.0-1736971400 branch January 15, 2025 21:04
@github-actions github-actions bot locked and limited conversation to collaborators Jan 15, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
rc-cherry-picked Run Smoke E2E Triggers smoke e2e on Bitrise team-confirmations Push issues to confirmations team team-runway-bot
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants