Description

On sponsored networks, the "send max native" feature wrongly tries to send 100% of user's balance on Hardware Wallets despite Gas Sponsorship being disabled for those. This creates an out of gas situation.
The PR restores the legacy behavior of the "max" button for such specific cases (HW + gas sponsorship + send max native).

Changelog

CHANGELOG entry: sponsored hardware wallet send max native

Related issues

Fixes: https://consensyssoftware.atlassian.net/browse/NEB-1132?atlOrigin=eyJpIjoiYjFiZWVkNWJlMTI5NDk5NmE4OTA2NTM5NjkzM2RlMzQiLCJwIjoiaiJ9

Manual testing steps

Feature: my feature name

  Scenario: user [verb for user action]
    Given [describe expected initial app state]

    When user [verb for user action]
    Then [describe expected outcome]

0. Use a HW wallet account - ex: QR Code wallet
1. Go on SEI token page on SEI network
2. Click on "Send"
3. Click on the "max" / "100%" button
4. Continue to Confirmation view. Notice that no error appear and that the tx executes without sponsorship.

Non-reg on regular accounts to check that sending max on SEI still sends the full balance - not Monad because of the 10 MON constraint.

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.

Performance checks (if applicable)

• I've tested on Android
  • Ideally on a mid-range device; emulator is acceptable
• I've tested with a power user scenario
  • Use these power-user SRPs to import wallets with many accounts and tokens
• I've instrumented key operations with Sentry traces for production performance metrics
  • See trace() for usage and addToken for an example

For performance guidelines and tooling, see the Performance Guide.

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.