Issue with Web3Auth Integration on New Domain and Client ID

I am encountering an issue with Web3Auth integration in a project. Here are the details:

  • Background: I successfully used Web3Auth in a project in 2023.
  • Current Situation: I am now working on the same project but under a different domain and with a new Web3Auth account.
  • Problem: The old code works perfectly with the old domain and old client ID. However, when I update the code to use the new client ID and the new domain, it breaks and shows the following error:

When asking for help in this category, please make sure to provide the following details:

  • SDK Version(package.json):
  • Platform:
  • Browser Console Screenshots:
  • If the issue is related to Custom Authentication, please include the following information (optional):
    • Verifier Name:
    • JWKS Endpoint:
    • Sample idToken (JWT):

Also, kindly provide the Web3Auth initialization and login code snippet below. This will help us better understand your issue and provide you with the necessary assistance.
const web3auth = new Web3Auth({

      clientId,

      chainConfig: {

        chainNamespace: CHAIN_NAMESPACES.EIP155,

        chainId: '0x13881',

        rpcTarget: 'https://polygon-mumbai.api.onfinality.io/public',

      },



      uiConfig: {

        theme: 'dark',

        // loginMethodsOrder: ["facebook", "google"],

        appLogo:

          'http://localhost:3000/static/media/logo.06d79dbb05db74889e044acd02e4aaca.svg', // Your App Logo Here

      },

    });

Hi @shayanvrinsoft,

I hope you are doing well. It’s great that you continue to use Web3auth. Please go to the dashboard and add your domain to the whitelist.

https://dashboard.web3auth.io/ → Select the project and add your domain.

Its already whitelisted

Hi @shayanvrinsoft

Thanks for verifying. Can you also confirm that the projectId where you are whitelisting the domain are the same?

Thanks

Yes the client Id is also same, I also checked manually in my code, also within the error prompt which I attached above both are same client ID

Can you check if the whitelist URL has the forward slash at the end ? in that case please add another URL without it.

Screenshot from 2024-05-31 11-06-55

Already did, I dont think so there is any issue with the whitelisting domain

@shayanvrinsoft Thanks for your patience.

Your issue is still under review by our Dev team and we will get back once there is a meaningful update to share.

Thanks Vjgee for update but the thing is its super urgent for me, and I am waiting from around 3 weeks now, really looking forward for the solution soon

Can you check if your app has been configured with the web3AuthNetwork parameter as cyan since the clientId you are using belongs to a project on cyan .

Please try changing the web3AuthNetwork to cyan and let me know if it works for you.

I have attempted to address the issue described in our recent discussions using the previously suggested approach; however, I regret to inform you that the problem persists. To ensure a thorough understanding and prompt resolution, I have meticulously documented my findings and steps taken in a detailed ticket, which I have attached for your review.

Your expertise and guidance are invaluable in resolving this matter efficiently. Could you please spare some time to review the ticket and offer your insights? Your assistance will not only help us overcome the current challenge but also enable us to implement a robust solution that prevents similar issues from arising in the future.

Thank you very much for your attention to this matter. I am looking forward to your feedback and working together towards a swift and effective resolution.

hi @shayanvrinsoft,
Let’s continue the discussion in the post-> Social Sign-In Issue: "could not validate redirect" Error with New Client ID - #3 by shayanvrinsoft