Sepolia ENS console error

[thisisrii]

When using Sepolia I run into this issue in the console

`ChainDoesNotSupportContract: Chain "Sepolia" does not support contract "ensUniversalResolver".

This could be due to any of the following:

• The chain does not have the contract "ensUniversalResolver" configured.

Version: [email protected]
at getChainContractAddress (webpack-internal:///(app-client)/./node_modules/viem/dist/esm/utils/chain.js:21:15)
at getEnsName (webpack-internal:///(app-client)/./node_modules/viem/dist/esm/actions/ens/getEnsName.js:22:108)
at Object.getEnsName (webpack-internal:///(app-client)/./node_modules/viem/dist/esm/clients/decorators/public.js:101:97)
at fetchEnsName (webpack-internal:///(app-client)/./node_modules/@wagmi/core/dist/chunk-OKULXQAF.js:2670:23)
at Object.queryFn12 [as queryFn] (webpack-internal:///(app-client)/./node_modules/wagmi/dist/index.js:2055:67)
at Object.fetchFn [as fn] (webpack-internal:///(app-client)/./node_modules/@tanstack/query-core/build/lib/query.mjs:261:27)`

[lochie]

The answer to this issue is right there in the error message (thanks to viem's error handling 🙏).

The chain does not have the contract "ensUniversalResolver" configured.

[ketiddies]

So how can I turn off the call to ensUniversalResolver if I know I'm not using ens / not using eth mainnet as a chain? Would be nice to not see this error in the console

[thisisrii]

Agreed, would be nice to not see this in the console.

I use Sepolia in test environments and then ETH mainnet in production, so I'm wondering if there's a way to somehow not do the call when I''m on the Sepolia network.