fix: send max main branch

[infiniteflower]

Description

This PR fixes an issue where if the gas estimates were not available, the user would literally try to send 100% of their gas token balance, which is impossible since we always need to account for gas. But if gas estimates were unavailable, the estimated gas would be calculated as 0.

Therefore, we just block the Use Max button if we have no gas estimates available in the odd case where the user has network connectivity but no gas estimates (possibly a provider is down).

Related issues

Fixes: #13215

Manual testing steps

1. Go to Send
2. Notice that Use Max is disabled and greyed out if no gas estimates

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I’ve followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• 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 format if applicable
• I’ve applied the right labels on the PR (see labeling guidelines). 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-actions]

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.

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 3ea54ad
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/bbf23ab9-f22a-458a-9f78-a59f0ff7f64c

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

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 1a34d49
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/557e1840-87e4-4166-9a69-96bf0db2bf33

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
83.3% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud