Link to minimal reproducible example

https://stackblitz.com/edit/vitejs-vite-9yovhwna?file=src%2Fmain.js

Summary

Expected Behavior:
After connecting a wallet, the user should be able to interact with it immediately, including signing messages, as soon as the account enters the connected state.

Current Behavior:
After connecting a wallet, the isConnected property of the account object is correctly set to true. However, attempting to call signMessage right after does not trigger a prompt in the wallet to perform the signing operation. Nothing happens and no errors are printed in the browser console.

This issue occurs predominantly on mobile devices, most of the times on Android. It appears there might be a delay between the completion of the connection phase and the wallet’s readiness to handle message signing. The problem is intermittent and varies across different Android mobile devices models.

The attached minimal reproducible example is based on https://github.com/reown-com/appkit/tree/main/examples/html-wagmi, with the simple addition to execute signMessage once the account enters the isConnected state.

I performed multiple tests with different Android devices, using up to date Chrome and Metamask and the packages listed below.

List of related npm package versions

appkit: 1.6.3
@wagmi/core: 2.x

Node.js Version

22.12.0

Package Manager

10.9.0