Description: How to configure web3auth with no-modal setup
Purpose: We were updating from v9 to v10 of web3auth. We were using wagmi-connector and I checked that now when using the wagmi provider is trying to call to use wallet service with this error message: “The current subscription plan is growth and requesting features (wallet service) are not available on growth plan. Please upgrade to a higher plan at … to use these features”
We are in the growth plan and is complaining about it. In any case, I want to know if there is some way to don’t try to mount wallet services.
I noticed that you were updating the documentation but it’s not clear, because some pages are broken and the forum of web3auth is not available neither.
Thanks for sharing the details — it seems like Web3Auth v10 is causing the “wallet service” request error, which can be confusing given the plan and migration changes. While waiting for official support, it helps to stay organized and guide non-technical collaborators clearly; for example, resources like show how simple, user-friendly links can improve clarity and communication, highlighting why Web3Auth should surface plan or feature issues more transparently. For reference, more discussion on this thread is available here: https://community.metamask.io/t/web3auth-v10-no-modal/30858.