-
Notifications
You must be signed in to change notification settings - Fork 680
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
[bug] Safe wallet never connects in Safe context #2140
Comments
@bitsforpeace WIll take a look and report back. |
Just wanted to check-in to see if there are any updates here |
@bitsforpeace Can you give our example dApp a try in your Safe Browser? |
Hey @DanielSinclair. I was able to connect using the Safe Browser with the example app you provided. Is it built using Vite? If so, could you please share the source code? |
Is there an existing issue for this?
RainbowKit Version
2.1.4
wagmi Version
2.12.5
Current Behavior
When I click on the Safe wallet option, the screen hangs with a message saying ‘Confirm connection in the extension,’ but the Safe wallet never actually connects.
Expected Behavior
Upon clicking ‘Safe’ from the wallet selection modal, it should connect to the Safe multisig wallet, but the connection hangs, showing ‘Confirm connection in the extension,’ and the Safe wallet never connects.
Steps To Reproduce
I've created a MRE repo here: https://github.com/bitsforpeace/react-vite-rainbowkit
Simply run the app (
pnpm install && pnpm dev
) and attempt to connect to a safe wallet from within the safe wallet context.Link to Minimal Reproducible Example (CodeSandbox, StackBlitz, etc.)
https://github.com/bitsforpeace/react-vite-rainbowkit
Anything else?
I’ve tried this with multiple Vite apps, and they all experience the same issue—hanging on ‘Confirm connection in the extension’ without connecting to the Safe multisig wallet. This makes me wonder if the issue is related specifically to Vite. Unfortunately, there are no logs providing any clues. However, a Next.js app with the same wallet and configuration setup has no issue connecting.
The text was updated successfully, but these errors were encountered: