bug: Unsupported method "eth_signtypeddata_v4" with WalletConnect & Trust Wallet

[niratodev]

Is there an existing issue for this?

• I have searched the existing issues

Package Version

1.4.2

Current Behavior

When signing typed data connected via WalletConnect (Trust Wallet) an error is thrown.

Unsupported method "eth_signtypeddata_v4" 

Expected Behavior

You can use eth_signtypeddata_v4

Steps To Reproduce

Try to use useSignTypedData

Link to Minimal Reproducible Example (StackBlitz, CodeSandbox, GitHub repo etc.)

https://github.com/niratodev/wagmi-walletconnect-trust-wallet-no-method

Anything else?

Apologies if Wagmi is not the source of the issue. I have searched and cannot pinpoint the source, so I am starting here. All indications point to:

1. eth_signtypeddata_v4 is supported
2. Wagmi creates the provider and includes the optional methods

[glitch-txs]

Hi, this issue is related to WalletConnect namespaces, this happens when you use only one chain, in the configuration you can try as workaround something like

const chains = [mainnet, mainnet]

const connector = new WalletConnectConnector({
  chains,
  options: {
    projectId: import.meta.env.VITE_WC_PROJECT_ID,
  },
});

Placing it directly in the WallletConnectConnector and not through the configureChains function.

This will be fixed once we go full optional namespaces.

[niratodev]

No freakin way. How did you figure that out?

[TheJuze]

Hi, i'm having same issue but multiple chains already passed ([mainnet, bsc, okc, polygon, fantom]). So any other ideas how to fix that?
deps:
"@wagmi/core": "^1.4.12"
"viem": "^1.21.0"

[glitch-txs]

@TheJuze with which wallet? Can you share repro steps?

[TheJuze]

@TheJuze with which wallet? Can you share repro steps?

Trust wallet. Repro steps:

1. Connect to WC with TrustWallet
2. Change network to mainnet
3. call signTypedData
4. get error Unsupported method "eth_signtypeddata_v4"

[github-actions]

This issue has been locked since it has been closed for more than 14 days.

If you found a concrete bug or regression related to it, please open a new bug report with a reproduction against the latest wagmi version. If you have any other comments you can create a new discussion.