Porto wagmi connector throws an error when trying to get wallet client with specified chain id.

[t0rbik]

Check existing issues

• I checked there isn't already an issue for the bug I encountered.

Describe the bug

I am using useWalletClient with chainId passed. My wagmi config is multichain.
useWalletClient({chainId: _some not default chain id_}) throws a ChainMismatchError.
I would expect to receive a wallet client with specified chain id.

Link to Minimal Reproducible Example

https://stackblitz.com/edit/vitejs-vite-bnito58r?file=src%2FApp.tsx

Steps To Reproduce

start app
connect with porto
see error:

Is wallet client defined: No
Error: The current chain of the connector (id: 84532) does not match the connection's chain (id: 11155420). Current Chain ID: 84532 Expected Chain ID: 11155420 Version: @wagmi/core@3.0.2

Porto Version

0.2.37

Viem Version

2.43.5

Wagmi Version

3.1.4

TypeScript Version

5.9.3

Anything else?

Please see another issue below.

[t0rbik]

I'm not sure if this is related, but might be and dont want to spam issues.
Here's another issue:
when porto is used with wagmi and multiple chains are setup, granting permissions on specific chain doesnt seem to be reflected correctly on Relay.
Reproduction link: https://stackblitz.com/edit/vitejs-vite-ryqi6qfo?file=src%2FApp.tsx.
Steps to reproduce:

1. start app
2. connect, notice that we provide baseSepolia chain id to grantPermissions on connect.
3. Fetch permissions and see it only exists on optimism.
4. Try to Grant Permissions manually, again on baseSepolia, returned data says chainId baseSepolia, but when we refetch permissions it is again only on optimism.

See screenshot:

[natalejoeraco1]

[Ysh204]

I dug into this and traced the full call stack.

useWalletClient({ chainId }) ultimately calls Wagmi's getConnectorClient, which compares the requested chainId with connector.getChainId() and throws ConnectorChainMismatchError if they differ.

Porto's getChainId() simply returns the provider's current active chain (eth_chainId), which appears consistent with how the official Wagmi connectors behave. From what I can tell, useWalletClient itself doesn't implicitly switch chains—the expected flow seems to be calling switchChain() first.

Given that, I'm wondering whether this is intended behavior rather than a Porto-specific bug. Is the intended design for Porto to support returning a wallet client for a different chainId without first switching the active chain, or should consumers call switchChain() before requesting the wallet client?