Daniel Sinclair

@jeanregisser Do you have these wallets installed? This is currently the expected UX if a user does not have the wallet installed. There is also another case where Safari will...

We evaluated options to resolve this, but it is inherently an issue with MetaMask's chain verification logic, and other wallets are not impacted. Chains often change names over time in...

@hsuanweifu-sports-inference You can hide the chain drop-down like so: ```tsx ```

@hsuanweifu-sports-inference I see. This was an intentional design choice because users still need to choose the network via their wallet, so seeing the current network via RainbowKit is duplicative. Can...

@hsuanweifu-sports-inference Thanks for this suggestion! We'll work on a prop to always show the current chain. We'll add this upstream in our new RainbowKit v2 version which launches this week....

@pctsvn Hi! I can't seem to replicate this issue. What device/OS are you using? Can you share a CodeSandbox reproducible example for me to look at and diagnose?

@niikkiin I see. The issue you're likely seeing here is that you haven't provided a WalletConnect `projectId` (by replacing `YOUR_PROJECT_ID`) and/or whitelisted the deployment domain, so WalletConnect redirects on mobile...

@danielSoler93 @pctsvn Let me know if the above guidance resolves your issue as well. Apologies for the WalletConnect v2 confusion.

@niikkiin The RainbowKit examples you're referencing don't currently contain a valid `projectId`, so you would need to set that before they work correctly. The `projectId`s are a secret that needs...

@kuji2336 Are you able to replicate the issue when connecting on rainbowkit.com?