[Bug]: `Unable to create some accounts with provider '<PROVIDER NAME>'` · Issue #42063 · MetaMask/metamask-extension · GitHub
Skip to content

[Bug]: Unable to create some accounts with provider '<PROVIDER NAME>' #42063

@gantunesr

Description

@gantunesr

Describe the bug

When MetaMask attempts to create or align a specific provider accounts via the MultichainAccountWallet, the Bitcoin Snap returns an unexpected JSON-RPC error, preventing account creation. This results in the error "Unable to create some accounts with provider ''". PROVIDER could be EVM, Bitcoin, Solana, or Tron.

Sentry Issue: METAMASK-YME3

Expected behavior

Accounts are created/aligned successfully during wallet initialization without errors. If expected errors occur, these should be properly handled.

Screenshots/Recordings

None

Steps to reproduce

Possible reproduction steps detailed in #41930

Error messages or log output

Unable to create some accounts (batch) with provider "EVM"
Unable to create some accounts (batch) with provider "Solana"
Unable to create some accounts (batch) with provider "Bitcoin"
Unable to create some accounts (batch) with provider "Tron"

Where was this bug found?

Live version (from official store)

Version

13.26.0

Build type

None

Browser

Chrome

Operating system

MacOS

Hardware wallet

No response

Additional context

Stack trace

  node_modules/@metamask/multichain-account-service/dist/MultichainAccountWallet.cjs:418
    → _MultichainAccountWallet_createAccountsRangeForProvider

  node_modules/@metamask/multichain-account-service/dist/MultichainAccountWallet.cjs:460
    → _MultichainAccountWallet_buildGroupStateForRange (Promise.allSettled)

  node_modules/@metamask/multichain-account-service/dist/MultichainAccountWallet.cjs:548
    → _MultichainAccountWallet_alignAccountsForRange

  /metamask/snaps/bundle.js:2:386351 (async #b)
  /metamask/snaps/bundle.js:2:383425 (async #w)
  /metamask/snaps/bundle.js:2:383109 (async #h)
  /metamask/snaps/bundle.js:2:382787 (async #u)
  • Error is handled (non-fatal crash), but account creation silently fails
  • The Snap error is opaque (-32603) — the snap itself is the likely root cause and may need investigation to surface a more actionable error

Severity

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Sev2-normalNormal severity; minor loss of service or inconvenience.regression-prod-13.26.0Regression bug that was found in production in release 13.26.0team-accounts-frameworkAccounts teamtype-bugSomething isn't working

    Type

    No fields configured for Bug.

    Projects

    Status

    To be triaged

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions