We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Originally posted by Dansando8 August 19, 2022 Hello there 🙂
If somebody had the same problem and may share some light it would be nice, thx!
When initializing web3auth, I did this as it's displayed on the documentation:
const web3authProvider = web3auth.connect();
const provider = new ethers.providers.Web3Provider(web3authProvider);
Then I get this error in the console:
Error: unsupported provider (argument="provider", value={}, code=INVALID_ARGUMENT, version=providers/5.6.0)
There is also a TypeScript error concerning the argument 'web3authProvider':
Argument of type 'Promise<SafeEventEmitterProvider | null>' is not assignable to parameter of type 'ExternalProvider | JsonRpcFetchFunc'.
Somebody managed to fix it ?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Discussed in https://github.com/orgs/Web3Auth/discussions/440
Originally posted by Dansando8 August 19, 2022
Hello there 🙂
If somebody had the same problem and may share some light it would be nice, thx!
When initializing web3auth, I did this as it's displayed on the documentation:
const web3authProvider = web3auth.connect();
const provider = new ethers.providers.Web3Provider(web3authProvider);
Then I get this error in the console:
Error: unsupported provider (argument="provider", value={}, code=INVALID_ARGUMENT, version=providers/5.6.0)
There is also a TypeScript error concerning the argument 'web3authProvider':
Argument of type 'Promise<SafeEventEmitterProvider | null>' is not assignable to parameter of type 'ExternalProvider | JsonRpcFetchFunc'.
Somebody managed to fix it ?
The text was updated successfully, but these errors were encountered: