Skip to content

[Bug]: Send max not working on v12.11 although a fix was cherry picked to the RC #30269

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

Closed
bschorchit opened this issue Feb 12, 2025 · 2 comments · Fixed by #30523
Closed

[Bug]: Send max not working on v12.11 although a fix was cherry picked to the RC #30269

bschorchit opened this issue Feb 12, 2025 · 2 comments · Fixed by #30523
Assignees
Labels
release-12.14.0 Issue or pull request that will be included in release 12.14.0 Sev2-normal Normal severity; minor loss of service or inconvenience. team-confirmations Push issues to confirmations team type-bug Something isn't working

Comments

@bschorchit
Copy link

Describe the bug

Original issue: #29903

Original fix PR: #29960

Cherry-pick PR: #29998

Slack thread

Goal of this issue: understand why the issue persisted on v12.11 after the cherry-pick and confirm that the issue is not present on v12.12

Expected behavior

No response

Screenshots/Recordings

No response

Steps to reproduce

  1. Start a send transaction for the native asset
  2. Click Max
  3. Confirm the transaction

Error messages or log output

Detection stage

In production (default)

Version

12.11.0

Build type

None

Browser

Brave

Operating system

MacOS

Hardware wallet

No response

Additional context

No response

Severity

No response

@bschorchit bschorchit added team-confirmations Push issues to confirmations team type-bug Something isn't working labels Feb 12, 2025
@github-project-automation github-project-automation bot moved this to To be fixed in Bugs by severity Feb 12, 2025
@bschorchit bschorchit added type-spike and removed type-bug Something isn't working labels Feb 12, 2025
@metamaskbot metamaskbot added the regression-prod-12.11.0 Regression bug that was found in production in release 12.11.0 label Feb 12, 2025
@Unik0rnMaggie
Copy link
Contributor

Present in v12.13.0:

Chrome.mov
Firefox.mov

@sleepytanya
Copy link
Contributor

Also confirming it is present in 12.13.0:

max.mov

@sleepytanya sleepytanya added the regression-RC-12.13.0 Regression bug that was found in release candidate (RC) for release 12.13.0 label Feb 16, 2025
@bschorchit bschorchit added type-bug Something isn't working and removed type-spike labels Feb 17, 2025
@github-project-automation github-project-automation bot moved this to To be fixed in Bugs by team Feb 17, 2025
@bschorchit bschorchit added Sev2-normal Normal severity; minor loss of service or inconvenience. type-bug Something isn't working and removed type-bug Something isn't working regression-prod-12.11.0 Regression bug that was found in production in release 12.11.0 regression-RC-12.13.0 Regression bug that was found in release candidate (RC) for release 12.13.0 labels Feb 17, 2025
@OGPoyraz OGPoyraz self-assigned this Feb 24, 2025
github-merge-queue bot pushed a commit that referenced this issue Feb 26, 2025
<!--
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 send max feature gas issues. 

It also adds e2e tests that cover: 
- correct amount
- gas modal changes (on picking 'low', 'medium', 'high'
- adjusting manual values on gas modal
- reacting gas estimation changes in network level

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

## **Related issues**

Fixes: #30269

## **Manual testing steps**

Usual send flow should work properly

## **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
Extension Coding
Standards](https://github.com/MetaMask/metamask-extension/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-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.
@github-project-automation github-project-automation bot moved this from To be fixed to Fixed in Bugs by severity Feb 26, 2025
@github-project-automation github-project-automation bot moved this from To be fixed to Fixed in Bugs by team Feb 26, 2025
@metamaskbot metamaskbot added the release-12.14.0 Issue or pull request that will be included in release 12.14.0 label Feb 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-12.14.0 Issue or pull request that will be included in release 12.14.0 Sev2-normal Normal severity; minor loss of service or inconvenience. team-confirmations Push issues to confirmations team type-bug Something isn't working
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

5 participants