Mubarak Usmane

The page needs to be refreshed after switching unfortunately, it looks the problem is coming from the Chains.jsx file. The chainId becomes null, however successfully switches once the page refreshes.

https://github.com/ethereum-boilerplate/ethereum-boilerplate/pull/147#issue-1207796046 Here's a temporary fix, however the page needs to be refreshed to re-render the page.

I've seen something like this in a prev issue. https://github.com/WalletConnect/walletconnect-monorepo/issues/1029#issuecomment-1123618918 Not sure if `desktopLinks` method work for mobile wallets, but try and pass mobile wallets anyway, rather than desktop wallets...

It is possible: https://docs.walletconnect.com/quick-start/dapps/web3-provider#filter-mobile-linking-options Either use `desktopLinks` for desktop, or `mobileLinks` for mobile.

Try using the latest v1.7.8, and let me know what happens

#130 Refer to his solution. `yarn format` before `yarn start` worked for me. Got rid of the prettier errors, and page became responsive

https://github.com/ethereum-boilerplate/ethereum-boilerplate/pull/147#issue-1207796046 You are gonna have to refresh the page after switching networks however

ChainId 250 I think is Fantom Wallet, this is most likely a rpc connection issue from their end. Few Questions: Did you find anyone else using Fantom having this problem?...

Yeah looks like each chain will need its own transaction hash, which I am still deciding how to go about it. Hardcoding every hash doesn't seem feasible

Okay... turns out that `transaction not found` means that `debug_traceTransaction` is detected in the RPC, and is looking for the transaction based on the params. All we need is to...