Email Sign In Issue

Embedded Wallets (Web3Auth)
1

:classical_building: Content from Web3Auth Community

This topic was originally posted by betnow on 8/22/2025.
This content has been migrated from our previous community forum to preserve valuable discussions.

SDK version: @web3auth/modal@^10.1.0 .

There’s an issue when the user signs in from his browser the sign-in fails with the error below. However, when trying on mobile or incognito, the sign-in works fine. This is happening only for this specific user.

{"code":1003,"error":"The current subscription plan is growth and requesting features (wallet service) are not available on growth plan. Please upgrade to a higher plan at https://dashboard.web3auth.io to use these features","success":false,"metadata":{"team_id":22885}}
2

Here’s a summary of the issue and the details needed for the support team:

Issue Summary

User: DexWin.Bet
Problem: Email Sign-In fails for a specific user in their browser (works on mobile/incognito).
SDK: @web3auth/modal
SDK Version: ^10.1.0
Platform: Web (Plug n Play)
Error Message:

{
  "code": 1003,
  "error": "The current subscription plan is growth and requesting features (wallet service) are not available on growth plan. Please upgrade to a higher plan at https://dashboard.web3auth.io to use these features",
  "success": false,
  "metadata": {
    "team_id": 22885
  }
}

Authentication Method: Email Sign-In (possibly via Firebase, based on context)

Analysis & Next Steps

  • The error indicates your current Web3Auth subscription (Growth plan) does not support the “wallet service” feature being requested during login.
  • The fact that it works on mobile/incognito for the same user suggests there may be a difference in login flow, session, or cached data between environments, but the root cause is the plan limitation.
  • This is not a code or integration bug but a subscription/feature access issue.

Proposed Solution

  • Upgrade Plan: To resolve this, you’ll need to upgrade your Web3Auth subscription to a plan that includes wallet services. You can do this at Web3Auth Dashboard.
  • Documentation Reference:
  • Temporary Workaround: If you do not intend to use wallet services, review your Web3Auth initialization and login flow to ensure you are not requesting features restricted to higher plans.

Support Team:

All relevant details (SDK, version, platform, error, context) are provided above.
If further investigation is needed, please check:

  • User’s Web3Auth dashboard for plan/feature status.
  • Whether the login flow is inadvertently requesting wallet services.

If you have any more questions or need help with the upgrade process, let us know!

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

3

Can you please try upgrading to the latest version and let me know if it still continues?
Also, please ask the user to clear out the cookies and try again.

4

Facing this issue again only for a particular staging environment client id

5

Which Web3Auth network does the client id belong to?

6

The client ID I’m using belongs to the mainnet Web3Auth network.
My codebase works completely fine when I replace the staging client ID with the production client ID , everything behaves as expected.
The issue only happens with the staging environment client ID, so it looks like something is wrong on the staging configuration on your side rather than in our implementation.

7

Can you please check on the latest SDK version? Also make sure if you are using wallet services, just even triggering it somehow, it can show this error on growth plan.

1 Like