Problem with our client id

[sealweb3]

Yesterday after office hour, @maharshi told us that we should share the repository via this medium so that he could replicate the bug. The project runs with under Web3Auth docs clientId but not under our clientId.

GitHub - sealweb3/seal-frontend-vite-web3auth-bug

[w3abot]

Hi SEAL!

Thanks for reaching out and providing the repository link. It looks like you’re experiencing issues with your client ID when using the Plug n Play SDK. Here’s a quick way we can proceed:

1. Check Configuration: Ensure your client ID is correctly registered in your Web3Auth dashboard and configured in your project. It’s a common pitfall to have discrepancies between what’s in the dashboard and the project configuration.

2. Repository Review: Maharshi will be able to replicate the bug using the provided repository link. This should help in identifying whether the issue is with the client ID registration or another part of the setup.

Since you’ve already shared your repo, Maharshi is in a good position to take a closer look. If you have any other snippets or console logs related to this issue, you can share them here for further insight.

Feel free to let us know if there’s anything else you need help with in the meantime!

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.

[maharshi]

Hey @sealweb3,
Thank you for joining the Office Hours! It was great speaking with you and your team.

We’ve successfully reproduced the issue you mentioned and are happy to let you know that we’ve fixed it. To resolve this on your end, you need to include the WalletConnect project ID in your Web3Auth configuration if you have one. Alternatively, you can explicitly exclude it when configuring adapters.

Here’s an example of a hooks-based implementation for our PnP SDK, which can also be applied to regular implementations:

const adapters = getDefaultExternalAdapters({ options: web3AuthOptions });
const filteredAdapters = adapters.filter((adapter) => adapter.name !== "wallet-connect-v2");

export const web3AuthContextConfig: Web3AuthContextConfig = {
  web3AuthOptions,
  adapters: [authAdapter, ...filteredAdapters],
  plugins: [walletServicesPlugin],
};