URGENT! Impacting multiple clients! Testnet deprecated and Sapphire Devnet and Testnet domain whitelisting not functioning

andrew · July 1, 2023, 10:35pm

Please provide the following details too when asking for help in this category:

I’ve created a plugin client id and whitelisted my domain, upon trying to login with google (which worked fine yesterday btw) now getting this error:

There seems to be some bug in the code. Please contact support to fix this.

could not validate redirect, please whitelist your domain: https://one2all.io for provided clientId BHRh3-d7RV1KArE27mTz3JfvAWD7vf4Uf5D6wQ28yzBXzeLeSXef7y9Gi3xJtUqAicNff0rnXvdOd_E-Tew73XE at dashboard. Also, this project is on testnet network. Please ensure the the used Client ID belongs to this network.

SDK Version: 6.1.1
Platform: chrome
Browser Console Screenshots:
Related to Custom Authentication? Please provide the following info too: (Optional)
- Verifier Name:
- JWKS Endpoint:
- Sample idToken(JWT)

Please provide the Web3Auth initialization and login code snippet below:
{“browser”:{“name”:“Chrome”,“version”:“114.0.0.0”},“os”:{“name”:“Windows”,“version”:“NT 10.0”,“versionName”:“10”},“platform”:{“type”:“desktop”},“engine”:{“name”:“Blink”}} current browser info
persistPlugin.ts:12 installing persist plugin
vuexPersist.ts:95 registering module deviceModule
vuexPersist.ts:95 registering module loginPerfModule
vuexPersist.ts:95 registering module userModule
vuexPersist.ts:95 registering module tKeyModule
dapp.ts:694 registering module
inpage.js:1 MetaMask: Connected to chain with ID “0x89”.
2chunk-vendors.f5114a6c.js:sourcemap:14 registering module BHRh3-d7RV1KArE27mTz3JfvAWD7vf4Uf5D6wQ28yzBXzeLeSXef7y9Gi3xJtUqAicNff0rnXvdOd_E-Tew73XE
chunk-vendors.f5114a6c.js:sourcemap:14 BHRh3-d7RV1KArE27mTz3JfvAWD7vf4Uf5D6wQ28yzBXzeLeSXef7y9Gi3xJtUqAicNff0rnXvdOd_E-Tew73XE BHRh3-d7RV1KArE27mTz3JfvAWD7vf4Uf5D6wQ28yzBXzeLeSXef7y9Gi3xJtUqAicNff0rnXvdOd_E-Tew73XE {} setting whitelabel
chunk-vendors.f5114a6c.js:sourcemap:14 modal: setTheme {}
chunk-vendors.f5114a6c.js:sourcemap:14 Object ‘current params’
chunk-vendors.f5114a6c.js:sourcemap:14 Error: could not validate redirect, please whitelist your domain: for provided clientId BHRh3-d7RV1KArE27mTz3JfvAWD7vf4Uf5D6wQ28yzBXzeLeSXef7y9Gi3xJtUqAicNff0rnXvdOd_E-Tew73XE at
Also, this project is on testnet network. Please ensure the the used Client ID belongs to this network.
at h (middleware.ts:29:9)
at m (middleware.ts:58:9)
at async Proxy.created (start.dbaa4dbe.js:1:7519)

andrew · July 1, 2023, 10:36pm

andrew · July 1, 2023, 10:37pm

andrew · July 1, 2023, 10:38pm

andrew · July 1, 2023, 10:39pm

btw what is this craziness that there can only be one image per post and two links?!

anyway, here is a link for you to test directly

vjgee · July 2, 2023, 12:51am

@andrew Thanks for reporting this.

Your issue has been forwarded to our team and we will get back at the earliest. Rest assured, we are looking into this on priority.

andrew · July 2, 2023, 12:56am

Thanks, also now receiving this error, don’t think i’ve changed anything, i’m guessing there are changes being made on your back-end in real time so sharing if helpful:

Visit https://bubble.io to build your own apps
openloginAdapter.ts:132 Failed to connect with openlogin provider Error: Internal JSON-RPC error.
at s (errors.js:176:12)
at Object.internal (errors.js:42:24)
at T.t.sendAsync (openloginJrpc.esm.js:686:13)
at async T.t.request (openloginJrpc.esm.js:709:5)
at async de.getEIP1559Compatibility (index.ts:162:11)
at async de.init (index.ts:30:10)
at async pe.setupProvider (EthereumPrivateKeyProvider.ts:60:36)
at async dr.connectWithProvider (openloginAdapter.ts:264:29)
at async dr.connect (openloginAdapter.ts:130:7)
at async yr.connectTo (noModal.ts:229:11)
at async sr. (modalManager.ts:301:7)
connect @ openloginAdapter.ts:132
await in connect (async)
connectTo @ noModal.ts:229
(anonymous) @ modalManager.ts:302
b @ openloginJrpc.esm.js:112
emit @ openloginJrpc.esm.js:162
(anonymous) @ loginModal.tsx:274
O @ Modal.tsx:142
handleSocialLoginClick @ Modal.tsx:220
onClick @ SocialLogins.tsx:87
Le @ react-dom.production.min.js:54
Fe @ react-dom.production.min.js:54
(anonymous) @ react-dom.production.min.js:55
jn @ react-dom.production.min.js:105
Dn @ react-dom.production.min.js:106
(anonymous) @ react-dom.production.min.js:117
ul @ react-dom.production.min.js:274
Pe @ react-dom.production.min.js:52
$n @ react-dom.production.min.js:109
Kt @ react-dom.production.min.js:74
qt @ react-dom.production.min.js:73
loginModal.tsx:329 error Error: Internal JSON-RPC error.
at s (errors.js:176:12)
at Object.internal (errors.js:42:24)
at T.t.sendAsync (openloginJrpc.esm.js:686:13)
at async T.t.request (openloginJrpc.esm.js:709:5)
at async de.getEIP1559Compatibility (index.ts:162:11)
at async de.init (index.ts:30:10)
at async pe.setupProvider (EthereumPrivateKeyProvider.ts:60:36)
at async dr.connectWithProvider (openloginAdapter.ts:264:29)
at async dr.connect (openloginAdapter.ts:130:7)
at async yr.connectTo (noModal.ts:229:11)
at async sr. (modalManager.ts:301:7) Internal JSON-RPC error.
(anonymous) @ loginModal.tsx:329
b @ openloginJrpc.esm.js:112
emit @ openloginJrpc.esm.js:167
(anonymous) @ noModal.ts:324
b @ openloginJrpc.esm.js:112
emit @ openloginJrpc.esm.js:162
connect @ openloginAdapter.ts:135
await in connect (async)
connectTo @ noModal.ts:229
(anonymous) @ modalManager.ts:302
b @ openloginJrpc.esm.js:112
emit @ openloginJrpc.esm.js:162
(anonymous) @ loginModal.tsx:274
O @ Modal.tsx:142
handleSocialLoginClick @ Modal.tsx:220
onClick @ SocialLogins.tsx:87
Le @ react-dom.production.min.js:54
Fe @ react-dom.production.min.js:54
(anonymous) @ react-dom.production.min.js:55
jn @ react-dom.production.min.js:105
Dn @ react-dom.production.min.js:106
(anonymous) @ react-dom.production.min.js:117
ul @ react-dom.production.min.js:274
Pe @ react-dom.production.min.js:52
$n @ react-dom.production.min.js:109
Kt @ react-dom.production.min.js:74
qt @ react-dom.production.min.js:73
Web3Auth-initialize–Web3Auth-.js:4 Web3Auth Error: Error: Internal JSON-RPC error.
at s (errors.js:176:12)
at Object.internal (errors.js:42:24)
at T.t.sendAsync (openloginJrpc.esm.js:686:13)
at async T.t.request (openloginJrpc.esm.js:709:5)
at async de.getEIP1559Compatibility (index.ts:162:11)
at async de.init (index.ts:30:10)
at async pe.setupProvider (EthereumPrivateKeyProvider.ts:60:36)
at async dr.connectWithProvider (openloginAdapter.ts:264:29)
at async dr.connect (openloginAdapter.ts:130:7)
at async yr.connectTo (noModal.ts:229:11)
at async sr. (modalManager.ts:301:7)
eval @ Web3Auth-initialize–Web3Auth-.js:4
b @ openloginJrpc.esm.js:112
emit @ openloginJrpc.esm.js:167
(anonymous) @ noModal.ts:324
b @ openloginJrpc.esm.js:112
emit @ openloginJrpc.esm.js:162
connect @ openloginAdapter.ts:135
await in connect (async)
connectTo @ noModal.ts:229
(anonymous) @ modalManager.ts:302
b @ openloginJrpc.esm.js:112
emit @ openloginJrpc.esm.js:162
(anonymous) @ loginModal.tsx:274
O @ Modal.tsx:142
handleSocialLoginClick @ Modal.tsx:220
onClick @ SocialLogins.tsx:87
Le @ react-dom.production.min.js:54
Fe @ react-dom.production.min.js:54
(anonymous) @ react-dom.production.min.js:55
jn @ react-dom.production.min.js:105
Dn @ react-dom.production.min.js:106
(anonymous) @ react-dom.production.min.js:117
ul @ react-dom.production.min.js:274
Pe @ react-dom.production.min.js:52
$n @ react-dom.production.min.js:109
Kt @ react-dom.production.min.js:74
qt @ react-dom.production.min.js:73
modalManager.ts:304 Error while connecting to adapter: openlogin WalletLoginError: Failed to connect with wallet. Failed to login with openlogin
at f.fromCode (index.ts:148:12)
at f.connectionError (index.ts:152:29)
at dr.connect (openloginAdapter.ts:141:13)
at async yr.connectTo (noModal.ts:229:11)
at async sr. (modalManager.ts:301:7)
(anonymous) @ modalManager.ts:304
await in (anonymous) (async)
b @ openloginJrpc.esm.js:112
emit @ openloginJrpc.esm.js:162
(anonymous) @ loginModal.tsx:274
O @ Modal.tsx:142
handleSocialLoginClick @ Modal.tsx:220
onClick @ SocialLogins.tsx:87
Le @ react-dom.production.min.js:54
Fe @ react-dom.production.min.js:54
(anonymous) @ react-dom.production.min.js:55
jn @ react-dom.production.min.js:105
Dn @ react-dom.production.min.js:106
(anonymous) @ react-dom.production.min.js:117
ul @ react-dom.production.min.js:274
Pe @ react-dom.production.min.js:52
$n @ react-dom.production.min.js:109
Kt @ react-dom.production.min.js:74
qt @ react-dom.production.min.js:73
errors.js:176 Uncaught (in promise) Error: Internal JSON-RPC error.
at s (errors.js:176:12)
at Object.internal (errors.js:42:24)
at T.t.sendAsync (openloginJrpc.esm.js:686:13)
at async T.t.request (openloginJrpc.esm.js:709:5)
at async de.getEIP1559Compatibility (index.ts:162:11)
at async de.init (index.ts:30:10)
at async pe.setupProvider (EthereumPrivateKeyProvider.ts:60:36)
at async dr.connectWithProvider (openloginAdapter.ts:264:29)
at async dr.connect (openloginAdapter.ts:130:7)
at async yr.connectTo (noModal.ts:229:11)
at async sr. (modalManager.ts:301:7)
s @ errors.js:176
internal @ errors.js:42
T.t.sendAsync @ openloginJrpc.esm.js:686

andrew · July 2, 2023, 1:14am

another datapoint, if i revert to a VERY early version of the SDK i’m able to connect to google, this is version 2+ of SDK. any version 3 and higher and i hit the Internal JSON-RPC error

andrew · July 2, 2023, 2:03am

@vjgee FYI above

andrew · July 3, 2023, 5:05am

@yashtest @vjgee Ugh. tried both aqua mainnet and cyan mainnet and still get this error:

There seems to be some bug in the code. Please contact support to fix this.

could not validate redirect, please whitelist your domain: https://one2all.io for provided clientId BHRh3-d7RV1KArE27mTz3JfvAWD7vf4Uf5D6wQ28yzBXzeLeSXef7y9Gi3xJtUqAicNff0rnXvdOd_E-Tew73XE at https://dashboard.web3auth.io. Also, this project is on testnet network. Please ensure the the used Client ID belongs to this network.

2 weeks is not a short amount of time, we were in the middle of a version release and we are blocked from all testing/development right now as are all of our clients. a better alternative is to wait until people have a viable alternative BEFORE you turn off testnet.

andrew · July 3, 2023, 5:15am

properly whitelisted via dashboard for all environments:

maharshi · July 3, 2023, 7:41am

Hey @andrew, I couldn’t help but notice that the clientId mentioned in the error message is different from the on the dashboard screenshot which shows that https://one2all.io is whitelisted. Could you please verify if https://one2all.io is whitelisted for the clientID in the error message or you could instead try using the clientID shown on your dashboard screenshot? Please let me know if this works for you.

andrew · July 3, 2023, 8:08am

hi @maharshi thx for note, i was cycling through multiple environments to try to find one that worked, here is another attempt and screenshot for the aqua mainnet client id. same error:

andrew · July 3, 2023, 8:09am

btw out of curiosity, are others not having this issue? is this only isolated to a few certain users?

yashovardhan · July 3, 2023, 7:26pm

@andrew at this point we have not received such queries from any other user. Can you share your web3auth implementation code? I think the reason here might be related to wrong web3authNetwork parameter in the web3auth constructor code.

andrew · July 3, 2023, 9:03pm

@yashovardhan we are developing and using a dedicated plugin for the bubble ecosystem, previously we had some checks in there for mainnet vs testnet which we just pushed a hotfix to remove temporarily. It’s not ideal as switching to mainnet will force everyone to use new wallets but better than not having a functioning app. So getting a viable true testnet alternative is still critical. in the meantime, we’ll use this as a workaround. thx

chai · July 4, 2023, 3:29pm

Hello,

Pls use cyan, aqua, mainnet for the moment.
Plug n Play SDK doesn’t support Sapphire Testnet at the moment. We’re working to add support for it asap.

yashovardhan · July 4, 2023, 5:40pm

Testnet migrations are currently in progress due to which you’re experiencing this. We will be restoring it as soon as possible.

andrew · July 4, 2023, 6:36pm

@chai @yashovardhan gotcha, ok thanks for the additional context and responses. Appreciate it. We have developed a hotfix in meantime that opens up mainnet for us to use in our dev branches. but once testnet is available we will want to switch back to keep the environments “clean” so to speak. Thanks

certify · July 10, 2023, 8:06pm

hi @yashovardhan @andrew I’m facing the very same issue. In mi case, it does not work production neither. I can only locally (localhost:3000).