-
Notifications
You must be signed in to change notification settings - Fork 0
Description
Bug description
Our dApp uses SIWE and leverages WalletConnect to prompt users to sign messages. While everything works as expected on the desktop Safe website, using the Safe Wallet iOS app results in an error when attempting to sign a message.
Steps To Reproduce
- On an iOS device, open the Safe Wallet app and connect to the dApp using WalletConnect (you can try it via this example or another example).
- Trigger the signMessage function from the dApp example.
- Observe the response of the signMessage method.
Expected Result
The Safe Wallet iOS app should display a prompt to sign the message and return the correct signature.
Actual result
The Safe Wallet iOS app is not receiving any signature request and instead it returns this response to the dApp:
{"id":1744803438076275,"jsonrpc":"2.0","error":{"code":-32075,"message":"Method disabled"}}
Device & App version
Device/OS: [e.g. iPhone12/iOS 18.3.2]
App version: latest
Environment
Additional info
This issue appears to be related to an older report (see #3447), which was closed without explanation. We suspect there might be a discrepancy between the mobile and desktop implementations regarding the handling of the personal_sign
method.
Request
Could you please review the implementation of WalletConnect on the iOS app, specifically around the personal_sign
method? Any guidance or updates to resolve this inconsistency would be greatly appreciated.
Thank you for your assistance.