Social Sign not returning idToken

All of sudden the social sign-in (I only tested Google) stopped returning the idToken. Even the example code that I use (web3auth-pnp-examples/web-no-modal-sdk/blockchain-connection-examples/evm-no-modal-example at main · Web3Auth/web3auth-pnp-examples · GitHub) does not return it.

Did anything get changed? I tested both versions 8.0.0 and 8.3.0.

Following - also seeing the same issue (version 8.1.0)

Now, 34min later, the example code is returning the idToken. Is there any instability happening?

new update:
i’m testing with two different google accounts. on the account #1 i’m receiving the idToken, but on the account #2 i’m not.

edit: just noticed that this is happening for new accounts. if i sign in with a fresh new account i wont receive the idToken. but if i sign in with the same account again, i’ll get the idToken

Hi @felipe,

Thank you for bringing this to our attention. Our team is currently analyzing the situation, and we’ll reach out to you as soon as we have an answer.
Your patience is appreciated!

Hi @felipe and @0x4163,

The issue has been resolved. Please check your implementations to confirm. Feel free to reach out to me if you encounter any further problems.

Thank you for your patience throughout this process.

Getting the same issue on web3-modal

To add some context I am using sapphire devnet with modal sdk and provided social auth

hi @emilio

Thanks for reporting your issue. Which packages and versions are you using?

Hi @TomTom . I’m still facing the same issue. These are the libraries that I’m using:

"@web3auth/base": "^8.0.0",
"@web3auth/coinbase-adapter": "^8.0.1",
"@web3auth/ethereum-provider": "^8.0.1",
"@web3auth/metamask-adapter": "^8.0.1",
"@web3auth/no-modal": "^8.0.1",
"@web3auth/openlogin-adapter": "^8.0.1",
"@web3auth/wallet-connect-v2-adapter": "^8.0.1",

Just to give you some context: I’m using JWT sign in with Firebase. So my flow is:

  • I sign in with Firebase
  • I get the idToken from Firebase
  • I pass the Firebase idToken to W3A and do the JWT sign in
  • I get the W3A user idToken, decode it and get the wallet public key

On the above flow, the user on Firebase is created successfully, and on the first attempt I never get the W3A user idToken. But when signing in again, I do receive it.

This entire flow was working for months until yesterday.
And again, the same issue happens with the example code web3auth-pnp-examples/web-no-modal-sdk/blockchain-connection-examples/evm-no-modal-example at main · Web3Auth/web3auth-pnp-examples · GitHub

I am using:

"@web3auth/base": "^8.3.0",
"@web3auth/modal": "^8.3.0",
"@web3auth/solana-provider": "^8.3.0",```

hi @emilio ,

Thanks for contacting us again and informing us your issue. I have just tested modal SDK in solana with new accounts in devnet and mainnet and is working ok. Would you mind sending us a video or more specifications on how are you getting an empty token ?

i @felipe,

We’re unable to reproduce the problem you’re experiencing. Could you please provide us with some additional details? Specifically:

  • Your region
  • Verifier
  • Verifier ID
  • Network

Also, does this issue occur only with new users the first time they encounter it?

Lastly, if you could send us a video demonstrating the problem, that would be greatly appreciated. Thank you!

Hi @felipe

Would you like to try again. We find the problem in one of our servers.

Please confirm us that your problem is solved or not.

Many thanks :slight_smile:

Problem is fixed on my end, thanks for fixing that.

Have noticed a few other posts about a similar issue I hope the idToken is not flakey as it is a core part of our user authentication.

Hi @TomTom . I noticed that the example project I have is working fine now.

However, the project that I’m working on is not signing in at all now for old/new users with JTW authentication (the example project does not use JWT). So this may be the issue now? I’m happy to share more info/video. Is there a place we can chat, like slack/discord? Since this is a new product I’m working on and we’re planning to launch it next week. Would appreciate your help.

My region is Portugal, verifier is custom-verifier-jwt-firebase-qa, and network is Sapphire Devnet

edit: it was a dependency issue with my lock file. everything is working now! thank you!

I’m glad to hear that !

I know you are working hard !

Please contact me if you have any other question :slight_smile:

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.