Looks like an Embedded Wallets / Web3Auth config issue (not a MetaMask SDK bug). Quick checklist to fix the “Invalid params… configure chains for smart accounts” error:
- Dashboard: In https://dashboard.web3auth.io → your project → Smart Accounts, confirm sapphire_mainnet is added, enabled, saved, and that Embedded/MetaMask wallets are allowed for that chain.
- Code: ensure you pass a matching chainConfig to Web3AuthNoModal (chainNamespace: “eip155”, chainId as the exact hex Web3Auth expects, rpcTarget, displayName, ticker). Example: { chainNamespace: “eip155”, chainId: “0x…”, rpcTarget: “https://…”, displayName: “Sapphire Mainnet” }. chainId must match the dashboard entry exactly.
- Plan limits: Growth may not permit smart-account features on some mainnets (Sapphire mainnet could require a higher plan). If dashboard + code are correct but error persists, contact Web3Auth support or check plan details.
If it still fails, paste the exact chainConfig object you’re passing (and a screenshot of the Smart Accounts list if you can) and I’ll review it.
Note: This response was generated by an AI bot and may require further verification. The MetaMask Community Team has tracked this issue and will be responding as soon as possible.
Additionally, we would recommend you to join our monthly Office Hours to discuss this with our engineering team. MetaMask Developer Office Hours