Nothing happens when a wallet connect transaction signing connection is invoked on a wrong current chain.

[eniolam1000752]

Expected behavior

As a user if I get a wallet connect transaction signing request from a chain I am not currently on, the application should be able to guide me to switch to the right application if I manage it. If I don't manage it, possibly, it should give me the option to add the application and switch to it so I can continue with the transaction signing request.

Actual behavior

When I get a wallet connect transaction signing request and I am on a different chain, I am unable to proceed with the signing request.

Which version(s) does this affect? (Environment, OS, etc...)

v3.0.0