[bug] signMessage Does Not Launch Rainbow/Metamask on Android

[nickcherry]

Is there an existing issue for this?

• I have searched the existing issues

RainbowKit Version

0.1.0

wagmi Version

0.3.5

Current Behavior

When calling signMessage within the Chrome browser on an Android device, there is haptic feedback, but the wallet app (e.g. Rainbow, MetaMask) is not launched / brought to the foreground, requiring that the user manually open the wallet app to find the sign message prompt.

Expected Behavior

I would expect the connected wallet (e.g. Rainbow, MetaMask) to be launched / brought to the foreground, similar to the experience of connecting a wallet. See also #460.

Steps To Reproduce

1. In Chrome on an Android device, navigate to https://neon-griffin-f8c8b4.netlify.app/
2. Connect to Rainbow or MetaMask.
3. Press "Sign Message" and observe that while there is haptic feedback, the wallet app is not brought to the foreground.

Link to Minimal Reproducible Example (CodeSandbox, StackBlitz, etc.)

https://github.com/nickcherry/rainbowkit-test

Anything else?

No response

[nickbytes]

Hey sorry for no update here! We're looking into Android + general deeplinking issues. We've found some improvements that can be made to RainbowKit, as well as some app improvements that need to be made. Will update you more shortly!

[markdalgleish]

I realised this is because we weren't detecting wc: URIs when saving the WALLETCONNECT_DEEPLINK_CHOICE setting to local storage which is what WalletConnect uses for deep linking. I've opened a PR fixing this.