Bug: No signing request/pop-up shown

[ebma]

Context

After a page refresh, no signing request is shown for the user. Tested on an Android phone using Chrome browser.
The page reloaded due to a recoverable error (the signer service was not available locally) and after I fixed that, the process reached the signing stage but no signing was requested nor any error shown.
However, there is a warning

'Navigation is blocked: wc:9c5dad9dbeb4eb6bbe40808d1899ed17db016bfec3bd042b9fdeb365e29136bd@2/wc?requestId=1730988197737568&sessionTopic=9abe69febffb3628afea0eecc23779de1e4c55e8ac474a8d3d4577a8df734db9'.

My flow was: Start the offramping process by clicking on the 'Confirm' button. Metamask opens and asks me to switch the network to polygon (this is expected and worked like a charm). I am back on Vortex but the process cannot continue because the signer-service is unavailable. The app starts reloading the page every 30 seconds. I make sure the signer-service is available again. I fill in the details with Mykobo and get back to the App. The signing-dialog shows after a brief delay but I don't get any notification/pop-up to open Metamask or similar.

After waiting for ~5 minutes, the app moved to the failure stage because the request expired.

TODO

• Investigate the Navigation is blocked warning. This indicates that the request for signing sent by vortex via the WalletConnect implementation in rainbowkit/wagmi was blocked by the browser.