Archived Content from Web3Auth Community
This topic was originally posted by zobeir on 9/16/2023.
This content has been migrated from our previous community forum to preserve valuable discussions.
We are experiencing not deterministic behaviour using Web3Auth. More users are flagging blank white modals when trying to login via Social, but then for other it’s working. Users, who are unable to login, are able to login via incognito mode.
Here’s the error we see in the console:
@derek1 @zobeir This is a known issue with Chrome Version 116.0.5845.179. The solution is to upgrade to Openlogin V4/ Web3auth v6 version or higher(V7).
Hi @vjgee, thank you for the quick reply. We updated our package and it indeed solve the problem, but created a new one.
We utilized extensively the whitelistUrl approach to emulate dynamic whitelists. Now, this broke with the update and I receive a error message for using it on domains which are not whitelisted even though I created a signature:
I am using the exact same code as in here: https://github.com/torusresearch/OpenLoginSdk/blob/7dc7ac2d2174055b94538ec8015a0066dc1c9dea/packages/openlogin/src/utils.ts#L11
@zobeir Thanks for your reply.
Your concern has been forwarded to our team and I will get back with an update.
Hey @zobeir, Please share the web3auth initialization snippet here, so that I can help you out.
Hi @maharshi we’re experiencing the same issue after update to 7.0.1
Already checked that there are no trailing slashes in the origin url
Here is our web3auth config
{
sessionTime: 86400,
enableLogging: false,
clientId: '...',
web3AuthNetwork: 'testnet',
chainConfig: {
chainNamespace: 'eip155',
chainId: '0x5',
displayName: 'Ethereum Goerli Testnet',
rpcTarget: '...',
ticker: 'ETH',
tickerName: 'Ethereum Goerli Testnet Token',
blockExplorer: 'https://etherscan.io'
}
}
Error message:
could not validate redirect, please whitelist your domain: https://...vercel.app for provided clientId ... at https://dashboard.web3auth.io. Also, this project is on testnet network. Please ensure the the used Client ID belongs to this network.
const web3Auth = new Web3AuthNoModel({
"uiConfig": {
"defaultLanguage": "en",
"primaryButton": "socialLogin"
},
"chainConfig": {
"chainNamespace": "eip155",
"chainId": "0x13881",
"rpcTarget": "<mumbai-rpc-target>"
},
"clientId": "<client-id>",
"enableLogging": false
})
const openLoginAdapter = new OpenLoginAdapter({
adapterSettings: {
"loginConfig": {
"google": {
"clientId": "<google-client-id>",
"name": "Google",
"typeOfLogin": "google",
"verifier": "<verifier-id>"
},
},
"originData": {
"http://dev.mylocalsite.com:3001": "<signature>"
},
"network": "cyan",
"uxMode": "popup",
"whiteLabel": {
"appName": "ZeroDev"
}
},
privateKeyProvider: new EthereumPrivateKeyProvider(...)
})
web3Auth.configureAdapter(openLoginAdapter)
Hi @zobeir, first of all, please update to the latest 7.0.2 version. If you see, in the web3auth initialisation snippet you have mentioned web3authNetwork as testnet while in OpenloginAdapter you have mentioned it as Cyan. Could you please paste the screenshot of the verifier on your dashboard which clearly shows the network it’s deployed on?
Hey @vitaly, the original thread is due to some issue with programmatic whitelisting, I would advise you to please open a new thread so that your issue can be looked into separately.
Okay, I have created one: Issue with programmatic whitelisting
I am unable to update past version 5 because it’s not supported on Node 16. Is there any way this can be fixed without updating?
@kewyn.comercial hey, please plan on updating to the latest version since v5 will be sunset any time now. Please start a new thread going forward, so that your issue can be given all the attention it deserves.
Hey @zobeir, closing this thread as you have confirmed that this is working now. @here Please create another thread for your issue if not created yet.