Error: Failed to connect with wallet. Invalid params, Failed to fetch (api.web3auth.io)

[waqas.dev.360]

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.

it is with the latest version.

[waqas.dev.360]

only code is

const web3AuthContextConfig: Web3AuthContextConfig = {
web3AuthOptions: {
clientId,
web3AuthNetwork: WEB3AUTH_NETWORK.SAPPHIRE_MAINNET,
mfaLevel: ‘none’,
// ssr: true,
},
};

and

  {children}

</ Web3AuthProvider>

[w3abot]

Thanks for reaching out, Waqas! Here’s a summary of your issue for the support team:

Issue Summary

• SDK: Web3Auth Plug and Play (PnP) Web SDK
• SDK Version: Latest
• Platform: Not specified yet
• Error Message: Error: Failed to connect with wallet. Invalid params, Failed to fetch (api.web3auth.io)
• Details Provided: Error occurs during wallet connection using the latest SDK version.

Next Steps
To help the support team diagnose and resolve your issue faster, could you please provide:

1. Your Web3Auth initialization and login code snippet.
2. The platform/environment you’re running this on (e.g., browser, OS).
3. A screenshot of the browser console showing the full error stack (if possible).

Possible Causes & Solutions

• This error often indicates a network issue or incorrect parameters during initialization. Please double-check your Web3Auth clientId and network settings in your initialization code.
• Make sure there are no ad-blockers or network restrictions blocking requests to api.web3auth.io.
• For reference, you can review the Web3Auth PnP Web SDK integration guide.

Once you share the code snippet and additional details, the team can provide more specific guidance. Thank you!

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.

Additionally, we would recommend you to join our biweekly Office Hours to get this resolved even faster. Web3Auth Developer Office Hours

[waqas.dev.360]

Everything is correct. ClientId & NETWORK …

[waqas.dev.360]

@w3abot

1. A screenshot of the browser console showing the full error stack (if possible).

I am using it in nextjs web-app.