-
Notifications
You must be signed in to change notification settings - Fork 2
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
Nested safe --owner safe can't connect using native integration with walletconnect on Polygon #317
Comments
@liliya-soroka have you tried connecting Safe to Safe? |
hm, yes we tried and @francovenica rechecked yesterday. |
Another user having the same issue but on ETH network. Client safe address: https://app.safe.global/settings/setup?safe=eth:0x87AcDD9208f73bFc9207e1f6F0fDE906bcA95cc6 |
@Claire-serveth , could you ensure that 2 different browsers or 2 different browser sessions are used in the case of native WC +safe-as-an-owner? |
Hi @liliya-soroka oh, I haven't thought of using 2 different browsers (only 2 tabs), but let me check on my end first before I relay to users. Thank you 🙏 |
the issue about using WC+safe-as-an-owner in 2 tabs of the same browser( same session) to follow the progress - safe-global/safe-wallet-monorepo#2719 |
Thank you @liliya-soroka 🙏 I was able to connect using 2 browsers as well, so I'm closing this issue now and follow the progress on #2719 ticket. |
Issue Category
Other
What happened?
User can't connect the owner safe via native integration with walletconnect on Polygon network. After pasting the walletconnect code on the owner safe, nothing happens, it's just stuck and it doesn't connect to the client safe:
Already tried basic troubleshooting steps and tried different browsers but issue still persists. I am also able to replicate the issue on my end.
Client safe address: https://app.safe.global/home?safe=matic:0x624384d763a57985809D6383c21D708C9C64c572
Owner safe address: https://app.safe.global/home?safe=matic:0x8864E55bAaC34Fd91070B0DB5f9cAdf43360EFd0
Date and time this happened or you first noticed this issue
31-10-2023
Network
Polygon
Safe Address
matic:0x624384d763a57985809D6383c21D708C9C64c572
Token Address
No response
Token Type
None
Transactions
No response
The text was updated successfully, but these errors were encountered: