Lack of Contextual Error When Connecting to Unavailable Namespace

[RyukTheCoder]

When attempting to connect to a namespace in Phantom Wallet that is not available in the currently selected account, the user receives an unhelpful error message:

{
  message: 'Unexpected error',
  data: undefined,
  code: -32603,
}

This message lacks context and provides no indication of what went wrong, making it confusing for both developers and end users.

Reproduction Steps:

1. Create or import an account into Phantom Wallet that supports only the EVM namespace (containing Ethereum, Polygon, Base, Monad).
2. In a dApp, attempt to connect to a different namespace not supported by the current account (e.g., Solana, Bitcoin, or Sui).
3. Observe the returned error: Unexpected error with no descriptive data or explanation.

Expected Behavior:

Phantom should return a more informative error message indicating that the selected account does not support the requested namespace.

Why This Matters

• The current error makes it hard to diagnose integration issues in dApps.
• It leads to a poor user experience by not indicating actionable steps or causes.
• Better error handling will help developers guide users appropriately (e.g., by suggesting they switch to a compatible account).

[adamdelphantom]

Hi @RyukTheCoder,

Thanks for the feedback! Are you seeing more helpful errors in the application logs when encountering issues?

[RyukTheCoder]

No there is no helpful errors. I've included the error object above.