Any idea when the test net issue would be resolved? With the new arrangement, the SDK is not selecting the right network for us. Only the cyan network is being populated, even when the main or aqua network is selected. Will be glad to know how to navigate this issue.
@cpayant Thanks for your post.
We’re launching updates within the next week to make it all functional asap.
I think the reason here might be related to wrong web3authNetwork
parameter in the web3auth constructor code. Just make sure the client id and verifier are on the same network for it to work properly.
Hello @vjgee, we have done this and still it isn’t fixed. Can we get some extra assistance? Is it possible to get on a Googlemeet or zoom call? Because we have been on this for close to 2 months now.
I have forwarded your feedback to our team and we will get back with an update.
@cpayant Thanks for your continued patience.
Our team confirmed that the SDKs are working correctly. Can you provide more information below:
- SDK & Version
- Platform
- Browser Console Screenshots
- Web3Auth initialization and login code snippet
Awaiting your reply.