Bug Report - Message Signing Issue After Mobile Wallet Connection

Open
#56 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
20/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
blockchain, mobile-dev

Research direction

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.

Description

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:

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,

Dominant language
No language data
Stars
49
Forks
124
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MetaMask/.github

All issues in MetaMask/.github

Similar issues

More Blockchain issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.