After logging in website using your library via e-mail/OTP-code, I cant see cryptowallet.
All worked 3 days ago, but now I get this: api-wallet.web3auth.io/user?fetchTx=false:1
Failed to load resource: the server responded with a status of 403 (Forbidden)Understand this error
Error: User doesn’t exist: traceId: undefined - spanId: undefined
at o (loglevelSentry.esm-D8pIhLDR.js:1:1971)
at a (loglevelSentry.esm-D8pIhLDR.js:1:2606)
Caused by: Error: User doesn’t exist
at v.translateError (loglevelSentry.esm-D8pIhLDR.js:1:638)
at async a (loglevelSentry.esm-D8pIhLDR.js:1:2564)
Response
(anonymous) @ index-BK3sGUfT.js:1
The problem only with widget: I get wallet address and can send there crypto. The user is exist in data base etc.
Meanwhile if I use different login methods (for instance via google authentication) all works fine.
Please help to solve the issue, I think the problem is on web3auth.io side.
Thank you for reporting the issue. Could you provide additional information about the packages you are using and their versions? Additionally, information on the web3auth network would be helpful. It would also be beneficial if you could share a brief screen recording to assist us in resolving this issue.
This is behavior of the wallet created 30 days ago - video . And this is correct behavior. Wallet address 0x2495e29E0C35840255328709f13c7Afcf605C807 (use bscscan).
The users who registered BEFORE 20th of July haven’t any problems: the wallet widget works fine for them, even now.
Now this is behavior for new wallets (this started on Thursday, 20th of July). Also, now we noticed that even for google authenticator registrations - we cant see the wallet widget (at the bottom left side of the browser). And this is critical, because its LIVE project.
So this video is today buggy behavior - video
Meanwhile, the Wallet from 2nd video is created, and can be used, wallet address 0xF131685763d744214DDe4f358e2e8C4BC0dd1099 (use bscscan)
{code: -32603, message: ‘[object Response]’, data: {…}, stack: ‘Stack trace is not available.’}
code: -32603
data: {cause: {…}}
message: “[object Response]”
stack: “Stack trace is not available.”
[[Prototype]]: Object
embed.esm.js:1223 login with session id failed
{code: -32603, message: ‘[object Response]’, data: {…}, stack: ‘Stack trace is not available.’}
code: -32603
data: {cause: {…}}
message: “[object Response]”
stack: “Stack trace is not available.”
[[Prototype]]: Object
walletServicesPlugin.esm.js:177
{code: -32603, message: ‘[object Response]’, data: {…}, stack: ‘Stack trace is not available.’}
code: -32603
data: {cause: {…}}
message: “[object Response]”
stack: “Stack trace is not available.”
[[Prototype]]: Object
index-BK3sGUfT.js:1
Error: User doesn’t exist: traceId: 80c5e80f68f44aeb83b3076ef6b6d2e9 - spanId: b7c98362f3aa2e49 at o (loglevelSentry.esm-D8pIhLDR.js:1:1971) at a (loglevelSentry.esm-D8pIhLDR.js:1:2606)
Caused by: Error: User doesn’t exist at v.translateError (loglevelSentry.esm-D8pIhLDR.js:1:638) at async a (loglevelSentry.esm-D8pIhLDR.js:1:2564)
PROJECT DETAILS:
Environment: Sapphire mainnet
Plug and Play, Core Kit (SSS)
Platform Type: Web application
Chain: EVM Based Chain
In fact we work on Binance Smart Chain (BSC / BEP-20)
Billing plan: Scale plan (we have WAY more ppl to work in project to overcome this plan)
No debts according billing system.
We really have old sdk version on our production evrironment:
“@web3auth/base”: “^8.0.0”,
“@web3auth/ethereum-provider”: “^8.0.1”,
“@web3auth/modal”: “^8.0.1”,
“@web3auth/openlogin-adapter”: “^8.0.1”,
“@web3auth/wallet-services-plugin”: “^8.0.1”,
But, when we updated our SDK to the latest version on our staging environment, the problem still exists:
“@web3auth/base”: “^8.6.2”,
“@web3auth/ethereum-provider”: “^8.6.2”,
“@web3auth/modal”: “^8.6.2”,
“@web3auth/openlogin-adapter”: “^8.6.2”,
“@web3auth/wallet-services-plugin”: “^8.6.2”
So, we get the same error, and the same behaviour.
Meanwhile, our staging and prod environments interact with PRODUCTION web3.0 project in terms of ID and secret because we are working on live blockchain both for production and staging instances.
What could be done to solve the issue, please guide us.
We have encountered an issue while using Web3Auth. After updating all Web3Auth modules and checking all the settings, we discovered the following error.
What was done:
Updated all Web3Auth modules to the latest versions.
Verified all Web3Auth settings in our project.
For thorough testing, installed Web3Auth in a new project. The error persisted.
For existing users, the Web3Auth modal displays correctly.
For new users, the following error occurs:
Error: User doesn’t exist: traceId: f532be40581e400a8dcb068cf5674805 - spanId: 8cc84454c4a1b6a6
Question:
What could be causing this error and how can it be resolved? We would appreciate any assistance in resolving this issue.
