When asking for help in this category, please make sure to provide the following details:
SDK Version:
Platform:
Browser Console Screenshots:
If the issue is related to Custom Authentication, please include the following information (optional):
Verifier Name:
JWKS Endpoint:
Sample idToken (JWT):
Also, kindly provide the Web3Auth initialization and login code snippet below. This will help us better understand your issue and provide you with the necessary assistance.
I actually have 3 emails that arrived today but a lot of time later. other emails arrive instantly. And when the code arrives it is to longer good because it has expired.
Keep in mind that this issue only affects @gmail.com email addresses.
This bug deeply impacts our operations. The app we used web3auth on has 1,000+ active wallets with more than $100K+ funds stuck on wallets. Our customers have been complaining for 2 weeks that they can’t access their funds. I hope your and your team understand the criticality of the issue and can solve it asap.
The latest version v7 is packed with essential updates, enhancements, and some pivotal changes to further ease your development process. You can read more here
We recommend to use only the latest version i.e. Web3Auth v7 as v6 is already deprecated on 31st December 2023 ,
You are using an older version of the SDK. Please upgrade to the latest version and share your feedback.
Yes, as per the feedback from users we have introduced an alternate flow. You can specify this in extraLoginOptions , flow_type as code or link , as per your choice.
Firstly, @web3auth/web3auth is deprecated, and @web3auth/modal is being used now, Please remove @web3auth/web3auth from your package.json file if you still have it.