-
Notifications
You must be signed in to change notification settings - Fork 530
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 integration does not work on https://app.safe.global with @web3-onboard/gnosis #2230
Comments
@Adamj1232 Hello there, any progress so far? We're implementing another type of smart wallet (using ERC1271, similar to Safe wallet) but are unable to integrate it with other integrated Blocknative app (ie Pendle) |
@anhntbk08 have you tried this with a built and deployed version of your application? |
I am also able to run the internal svelte demo that is part of the web3-onboard project locally.
I suspect you have something a little off in your |
I have a working version of your project on a branch but I cant push as I dont have permissions. Also, be sure to enable your preffered way of handling local CORS issues. I like to use the Changes I made to get it working was add the necessary dep noted in the docs:
Update the
|
PR to add reminders and clarity to docs and readme: #2257 |
Current Behavior
Attempting to connect the wallet via https://app.safe.global/ will show a

SafeAppProvider is not a constructor
error. I've attached the screenshot below.Expected Behavior
It should connect as expected.
Steps To Reproduce
I've created a repo brand new Vue repo with the default Web3-onboard setup instructions to demo it here:
https://github.com/WoodyDark/web3-onboard-safe-wallet-report
npm install
,npm run dev
http://localhost:5173
as Safe App URLWhat package is effected by this issue?
@web3-onboard/gnosis
Is this a build or a runtime issue?
Runtime
Package Version
2.22.1
Node Version
No response
What browsers are you seeing the problem on?
Chrome
Relevant log output
Anything else?
No response
Sanity Check
The text was updated successfully, but these errors were encountered: