Repository navigation
Bug Report - Message Signing Issue After Mobile Wallet Connection #56
Description
Activity
Hi @donnagifts !
From the example you provided it seems that you're trying to trigger a signing request programmatically as soon as the user connects his wallet. Because the wallet send the user back on android to the dapp after connecting you end up not seeing the signing prompt appear in MetaMask even though it's there to be displayed.
From the video above you'll see that after connecting I manually switch to the MetaMask wallet and the signing request is there and because I manually switching from the dapp to the wallet thegoBackfeature ends up directing me to my homescreen instead of the dapp.
Generally speaking, programmatically triggering a deeplink is not advisable as some OSs' will flag this and prevent the user to be directed to the Wallet even though the request comes through.
Keep in mind that according to the example you provided you're listening to the whole modal state and thus, simply opening the modal will trigger this modal + prompt a signing request.It is strongly advised that any request that should direct the user to the wallet is tied to a user action such a tap on a button.
Screen.Recording.2025-01-16.at.1.33.47.PM.mov
Hello Metamask team,
We have identified a significant issue regarding message signing immediately after wallet connection, primarily affecting Android mobile devices.
Description:
Technical Details:
Reproduction:
Additional Context:
The issue has been documented in this GitHub issue: reown-com/appkit#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,