-
Notifications
You must be signed in to change notification settings - Fork 167
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Metamask could connect, but the personal_sign method did not respond #108
Comments
You will need to synchronize your wallet and then you debug it with bech13 |
@SWCheng1122 This problem happends to me and my friend. You need add extra code to open metamask after call Hopes to help. |
Hey @Drolmen, thanks for your answer Another question with personal_sign
What's the format of the response? Im not able to find how to read the content... |
@ljs19923 the response should be as documented https://docs.walletconnect.com/1.0/json-rpc-api-methods/ethereum#personal_sign i.e. it's a hexadecimal data of the signature |
@DmitryBespalov thanks for your answer, I'm not able to extract the content of response. It's a dictionary? Because the type of response is "Response", how can I convert that to a dictionary? Can you show me how to do that in code please? If you would like to print the hexadecimal data of the signature |
@ljs19923 please try out You can convert the received response result to a Decodable type.
You can also check if the wallet responded with error:
|
Metamask could connect, but the personal_sign method did not respond
The text was updated successfully, but these errors were encountered: