This is expected behaviour. You are running the demo in the browser, the web app will try to find the injected wallets, since your browser don’t have any wallet installed, it’ll show that screen. Your browser, can’t communicate with OS to know whether the app are installed or not. Even if it can, the connection won’t be established. Hence Wallet Connect exists. You should use Wallet Connect option to connect with wallets on Mobile.
Thank you, is there a way to in the SDK say to it that it should try connecting to metamask using WalletConnect. E.g. the user clicks Metamask icon, and it immediately opens the Metamask connection in WalletConnect, which then opens the app on the device.
For example do you support something like walletConnectProvider.connectTo( { selectedWallet: “metamask” } )? To skip showing the default WalletConnect selector, and immediately try to connect to Metamask instead.