Skip to content
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

Safe-as-an-owner doesn't work with native WC implementation in the same browser in 2 different tabs #2719

Closed
liliya-soroka opened this issue Oct 31, 2023 · 4 comments
Labels
bug Something isn't working

Comments

@liliya-soroka
Copy link
Member

liliya-soroka commented Oct 31, 2023

Bug description

Safe-as-an-owner doesn't work with native WC implementation in the same browser in 2 different tabs## Environment

  • Browser: Chrome
  • Wallet: MetaMask
  • Chain: any

Steps to reproduce

  1. Open web app in 2 tabs in the same browser under the same session
  2. try to connect safe-as-owner to the parent safe
    Current result: Nothing happens after the wc url is passed

Expected result

It should be possible to connect safe-as-an-owner when 2 tabs in the same browser are used for connecting the safe-as-an-owner via wc native implementation

Obtained result

Screenshots

@Dracaena27
Copy link

The issue persist.

@Dracaena27
Copy link

The nested wallets are connecting now using different browsers, but I´d like to use the same browser. Do you know if this is possible?

@katspaugh
Copy link
Member

We don’t support multi tab operation very well atm due to state persistence. There’s a tech debt issue to fix this. I’ll prioritize it.

@katspaugh
Copy link
Member

Fixed in #2793.

@github-project-automation github-project-automation bot moved this from New issues to Done in Safe{Wallet} Nov 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Archived in project
Development

No branches or pull requests

3 participants