Skip to content

fix: cherry-pick: Bug in transaction flow component for 1155 token (#29775) #29975

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

Merged
merged 1 commit into from
Jan 30, 2025

Conversation

pedronfigueiredo
Copy link
Contributor

@pedronfigueiredo pedronfigueiredo commented Jan 29, 2025

Cherry-picks: #29775

Description

There has been a recent change to stop relying on transaction decoding third
parties
. The parsed transaction data now varies depending on the ABIs, and for some ERC1155 tokens the ._to argument is expressed as simply .to.

Open in GitHub Codespaces

Related issues

Fixes:

Manual testing steps

  1. Go to this page... 2.

Screenshots/Recordings

Before

Screenshot 2025-01-17 at 10 03 10

After

Screenshot 2025-01-17 at 10 05 45

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.

Description

Open in GitHub Codespaces

Related issues

Fixes:

Manual testing steps

  1. Go to this page...

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.

<!--
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?
-->

There has been a [recent change to stop relying on transaction decoding
third
parties](#29341). The
parsed transaction data now varies depending on the ABIs, and for some
ERC1155 tokens the `._to` argument is expressed as simply `.to`.

[![Open in GitHub
Codespaces](https://github.com/codespaces/badge.svg)](https://codespaces.new/MetaMask/metamask-extension/pull/29775?quickstart=1)

## **Related issues**

Fixes:

## **Manual testing steps**

1. Go to this page...
2.
3.

## **Screenshots/Recordings**

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

### **Before**

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

<img width="320" alt="Screenshot 2025-01-17 at 10 03 10"
src="https://github.com/user-attachments/assets/ef3c39a1-0002-48a8-a64b-5479a2122dc5"
/>


### **After**

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

<img width="320" alt="Screenshot 2025-01-17 at 10 05 45"
src="https://github.com/user-attachments/assets/0b95a3bc-420a-4150-908b-bed6cbb20206"
/>


## **Pre-merge author checklist**

- [ ] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask
Extension Coding
Standards](https://github.com/MetaMask/metamask-extension/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [ ] I've completed the PR template to the best of my ability
- [ ] I’ve included tests if applicable
- [ ] I’ve documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [ ] I’ve applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-extension/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.
@pedronfigueiredo pedronfigueiredo added the team-confirmations Push issues to confirmations team label Jan 29, 2025
@pedronfigueiredo pedronfigueiredo self-assigned this Jan 29, 2025
@pedronfigueiredo pedronfigueiredo requested a review from a team as a code owner January 29, 2025 16:35
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.

@dbrans dbrans merged commit 1aa9aa4 into Version-v12.11.0 Jan 30, 2025
67 of 71 checks passed
@dbrans dbrans deleted the pnf/cherry-pick-fix-send-nft-into-v12.11 branch January 30, 2025 13:48
@github-actions github-actions bot locked and limited conversation to collaborators Jan 30, 2025
@dbrans dbrans added type-bug Something isn't working release-blocker This bug is blocking the next release regression-RC-12.11.0 Regression bug that was found in release candidate (RC) for release 12.11.0 labels Jan 30, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
regression-RC-12.11.0 Regression bug that was found in release candidate (RC) for release 12.11.0 release-blocker This bug is blocking the next release team-confirmations Push issues to confirmations team type-bug Something isn't working
Projects
None yet
3 participants