Skip to content

Conversation

@runway-github
Copy link
Contributor

@runway-github runway-github bot commented May 14, 2025

Description

This PR aims to fix an issue when user puts an unexpected value into
to field in send flow.

It appears from that the
issue
is
thrown by toChecksumAddress because it doesn't expect any incomplete
address. However in send flow UX we let user to type in address
themselves.

To test this you can go SendTo page and put K for example - and see
the crash. (Screenshot below is fixed version)

Labels
Adding skip-sonar-cloud as the raised issue was intentional.

Screenshot 2025-05-14 at 06 44 09

Related issues

Fixes: #15094

Manual testing steps

  1. Go to send flow
  2. Input an unexpected address
  3. Confirm warning shown - you shouldn't be proceed next step

Screenshots/Recordings

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. b22bfcc

… `SendTo` page (#15308)

<!--
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 an issue when user puts an unexpected value into
`to` field in send flow.

It appears from that [the
issue](https://metamask.sentry.io/issues/6582066742/?project=2299799) is
thrown by `toChecksumAddress` because it doesn't expect any incomplete
address. However in send flow UX we let user to type in address
themselves.

To test this you can go `SendTo` page and put `K` for example - and see
the crash. (Screenshot below is fixed version)

**Labels**
Adding `skip-sonar-cloud` as the raised issue was intentional.

![Screenshot 2025-05-14 at 06 44
09](https://github.com/user-attachments/assets/fda651bc-4925-40d8-95ca-2cabd7cbed66)

## **Related issues**

Fixes: #15094

## **Manual testing steps**

1. Go to send flow
2. Input an unexpected address 
3. Confirm warning shown - you shouldn't be proceed next step

## **Screenshots/Recordings**

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

### **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 May 14, 2025 06:27
@metamaskbot metamaskbot added the team-runway-bot-deprecated DEPRECATED: please use "team-bots" instead label May 14, 2025
@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Please upload report for BASE (release/7.47.0@e126d89). Learn more about missing BASE report.

Additional details and impacted files
@@                Coverage Diff                @@
##             release/7.47.0   #15309   +/-   ##
=================================================
  Coverage                  ?   68.64%           
=================================================
  Files                     ?     2376           
  Lines                     ?    51324           
  Branches                  ?     7640           
=================================================
  Hits                      ?    35229           
  Misses                    ?    13857           
  Partials                  ?     2238           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@sonarqubecloud
Copy link

@OGPoyraz OGPoyraz merged commit a8254f5 into release/7.47.0 May 14, 2025
38 of 40 checks passed
@OGPoyraz OGPoyraz deleted the runway-cherry-pick-7.47.0-1747204013 branch May 14, 2025 08:32
@github-actions github-actions bot locked and limited conversation to collaborators May 14, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

team-runway-bot-deprecated DEPRECATED: please use "team-bots" instead

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants