Closed barnjamin closed 2 years ago
I've had these problems a number of times utilising wallet connect and figured I might have to run my own bridge connect to make it stable. Thanks @barnjamin for giving me the insight that perhaps it occurs when swapping from main->testnet.
Reproduction steps:
The fix was:
If it breaks the first time, it looks like you need to refresh the QR code along with restarting the iOS app.
ps. It may also be worth whilst considering how long the timeout is before punting users back to the accounts screen. It feels too long.
I believe that with the fixes we pushed in February and March we've resolved these WalletConnect issues.
While testing an application that uses wallet connect several iOS users reported issues around the signing prompt.
4 - Authorize Prompt would open and instantly close 2 - Authorize Prompt would be approved and nothing made it back to the web application 3 - Worked the first time without restarting the app
In all cases restarting the mobile app seemed to fix the issue. These were all using the TestNet network setting.
Since restarting the mobile app allowed the transaction to be authorized I suspect there is some cached field or setting causing this behavior but I'm not sure where to look.