Missing idToken using Google social login in web3auth modal

[dev.dworldvr]

When logging in using google in web3auth modal no idToken is returned(both on the hosted website and localhost). Tried to check with other devs working in the same project and they get the idToken on their side. Tried other devices, accounts, and browsers nothing seems to work.

using "@web3auth/modal": "^7.3.2"

Any idea what is happening?

[w3abot]

Hi Dworld! Thanks for reaching out.

It’s interesting that your teammates can get the idToken successfully but you can’t. It might be related to how your scopes or adapter settings are configured, or possibly a browser/cookie setting on your side. Could you please share the following so the team can pinpoint the issue?

• Your Web3Auth initialization snippet (especially any scope or adapter settings).
• A console log or screenshot (from your browser dev tools) showing what’s returned after login.

In the meantime, make sure you’re including “openid” in your login scopes (for example: scope: [“openid”, “profile”, “email”]) – that’s required to get the idToken. This page from our docs might help show how to specify that in the adapter:
https://docs.web3auth.io/sdk/web/modal/initialize#step-3-initialize-adapters

Let us know! Once we have those details, the support team will jump in to help further.

Note: This response was generated by an AI bot and may require further verification. The Web3Auth support team has tracked this issue and will be responding as soon as possible.

Additionally, we would recommend you to join our biweekly Office Hours to get this resolved even faster. Web3Auth Developer Office Hours

[dev.dworldvr]

Here is the config part of the web3auth:

and here is how I called the config:

I used both web3auth.getUserInfo(), which I mainly used, and web3auth.?authenticateUser() to test but both does not return idToken:

for the console.log response, I attached it with my 1st question. Let me know if you need more details, Thanks for the response.

[yashovardhan]

Hello @dev.dworldvr,

It appears that you are utilizing an outdated version of Web3Auth. The issue you are encountering appears to be unrelated to the SDK version. We will be investigating this matter further to resolve it. In the meantime, I recommend upgrading to v9 of the Web3Auth SDK.

Please be aware that v7 SDK version will be deprecated in the near future: ⚠️ IMPORTANT: Web3Auth SDK Deprecation Notice ⚠️