Hi Levente — I’m on the MetaMask & Web3Auth team. Short answer: this looks like subscription enforcement from Web3Auth — error 1003 explicitly says the Growth plan does not allow the “wallet service”, so requests that require that feature will start failing even if your code didn’t change.
Why it could appear suddenly
- Web3Auth started enforcing plan feature gates (or billing/payment changed) for the web project.
- Web and mobile often use different Dashboard projects / Client IDs — mobile may be using a project that still has the feature or has active cached sessions.
Immediate actions to take (quick checklist)
- Check the Web3Auth Dashboard for the web project: plan tier, billing status, and whether “wallet service” or related toggles are enabled.
- Confirm the Client ID used by your web app (env/config) and verify it matches the Dashboard project that has the wallet-service capability.
- Compare web vs mobile Client IDs / projects — mobile working usually means they use a different project or have long-lived sessions.
- Check dashboard audit logs / recent emails from Web3Auth about plan or policy changes.
- If you need the feature immediately, upgrade the plan or switch the web app to a project that has wallet service enabled.
What I checked for you
- I searched the Embedded Wallets docs and confirmed wallet-service features are gated by subscription and that Client ID / project mismatch is a common cause for web vs mobile differences.
If you want me to escalate / have someone from the Web3Auth team look into it, please reply with these items (don’t paste secrets):
- Web SDK + version you’re using
- Client ID used by the web app (Client ID only)
- Whether web and mobile use the same Dashboard project
- Timestamp(s) of failed login attempts and the exact error payload / a console network screenshot if available
If you prefer, you can first check the Dashboard/billing and let me know what you find — I’ll escalate immediately if it looks like a billing/plan enforcement issue.
Note: This response was generated by an AI bot and may require further verification. The MetaMask Community Team has tracked this issue and will be responding as soon as possible.
Additionally, we would recommend you to join our monthly Office Hours to discuss this with our engineering team. MetaMask Developer Office Hours