Bug Report - Message Signing Issue After Mobile Wallet Connection

Hello Metamask team,

We have identified a significant issue regarding message signing immediately after wallet connection, primarily affecting Android mobile devices.

Description:
- Expected Behavior: Users should be able to sign messages as soon as the wallet enters the connected state
- Current Behavior: Although the isConnected property is correctly set to "true", calling signMessage doesn't trigger any prompt in the wallet. No errors are displayed in the browser console.

Technical Details:
- The issue is intermittent and varies across different Android device models
- Environment: Latest Chrome, Latest Metamask
- Packages: appkit 1.6.3, @wagmi/core 2.x
- Node.js: 22.12.0

Reproduction:
- Minimal example reproducing the bug: https://stackblitz.com/edit/vitejs-vite-9yovhwna?file=src%2Fmain.js
- Detailed GitHub issue: https://github.com/reown-com/appkit/issues/3601

Additional Context:
The issue has been documented in this GitHub issue: https://github.com/reown-com/appkit/issues/3601. "Reown" is the new name of "Wallet Connect" and Appkit is the package we use in our implementation.

There appears to be a delay between the completion of the connection phase and the wallet's readiness to handle message signing operations.

Could you help us investigate this issue? We're available to provide any additional information needed.

Best regards,

Start with the linked StackBlitz reproduction, especially src/main.js, and compare the behavior with reown-com/appkit issue 3601. Test the connection-to-signing sequence on Android with the stated appkit and @wagmi/core versions. Done means signMessage reliably triggers a wallet prompt immediately after the connected state is reached, without console errors.

Written by the indexing model from the issue text.