Balances are not loading on Rinkeby when you connect with WalletConnect
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.5k
- Forks
- 5.4k
- PR merge metrics
- No merged PRs in 30d
Description
Bug Description
If you connect to Rinkeby network by scanning QR code from WalletConnect and some wallet like MetamaskMobile or Gnosis-safe, and open token list, most of the coin balances are not going to load.

Steps to Reproduce
- Go to Uniswap
- Make sure you are not connected to WalletConnect or that you don't have
walletconnectin localStorage - Click on Connect Wallet and select WalletConnect and the QR code should open
- In your MetamaskMobile app you should be on Rinkeby network
- Scan the QR code
- After the connection click on Select token button in Uniswap
- The balances are stuck on loading
Expected Behavior
After the WalletConnect connection on Rinkeby the balances should load correctly
Additional Context
It looks like the WalletConnect is making requests to Mainet https://mainnet.infura.io/v3/099fc58e0de9451d80b18d7c74caa7c1 instead of Rinkeby https://rinkeby.infura.io/v3/099fc58e0de9451d80b18d7c74caa7c1. Then after you reload the page and connect again without scanning the QR code it will load the balances correctly. This issue seems to occur after updating @web3-react/walletconnect-connector to version higher then ^6.2.4
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the WalletConnect flow on Rinkeby and inspect the connection handling around @web3-react/walletconnect-connector, especially the version change above ^6.2.4. Confirm that token balances request the Rinkeby endpoint rather than mainnet after scanning the QR code, and verify that balances load without a page reload.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- blockchain, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100