Description

On Sei, a Ledger swap that requires 2 signatures (token approval + trade) completes successfully on-chain, yet a misleading "Something went wrong" hardware-wallet sheet is still shown to the user.

Root cause: Sei (chainId 1329) is a Cosmos-SDK chain with EVM compatibility. In @metamask/bridge-status-controller's sequential EVM submit flow (submitEvmHandler), the controller waits for the approval tx to reach confirmed status locally and then immediately broadcasts the trade tx. On Sei, the Cosmos account_sequence has not yet propagated through the RPC at that point, so the trade tx is initially rejected with RPC submit: : incorrect account sequence. That rejection is parsed to ErrorCode.Unknown and surfaced via the hardware-wallet error bottom sheet ("Something went wrong"), even though the swap ultimately lands and succeeds.

Fix: Patch @metamask/bridge-status-controller@72.0.0 to pause for 3s only on Sei, after the approval tx confirms and before the trade tx is broadcast — mirroring the existing LINEA/BASE pattern in handleApprovalDelay. This gives the chain time to update its account state, so the trade is accepted on the first broadcast and no spurious error is shown. The delay sits inside the requireApproval && approvalTxId branch, so it only runs on hardware-wallet flows and is invisible to other users.

Implemented as a yarn-berry patch (consistent with the repo's existing dependency-patch convention):

• .yarn/patches/@metamask-bridge-status-controller-npm-72.0.0-eb8f9d1327.patch — patches both dist/strategy/evm-strategy.cjs and dist/strategy/evm-strategy.mjs
• package.json — adds the patch resolution (dependency kept at ^72.0.0)
• yarn.lock — updated accordingly (yarn install --immutable passes)

Changelog

CHANGELOG entry: Fixed a misleading "Something went wrong" error shown to Ledger users after a successful 2-approval swap on the Sei network.

Related issues

Fixes: #30730

Manual testing steps

Feature: Ledger swap on Sei network

  Scenario: User completes a 2-approval swap on Sei with a Ledger
    Given a Ledger account is connected with blind signing enabled
    And the user is on the Sei network

    When the user swaps USDC/Sei to Sei (requiring an approval + trade signature)
    Then both transactions are signed and submitted successfully
    And the swap completes successfully
    And no "Something went wrong" error sheet is shown

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
• I've instrumented key operations with Sentry traces for production performance metrics

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.

Made with Cursor