Wallet performance issues with outdated dependencies

Help - Plug n Play PnP Web SDKs
1

Dear web3Auth support, about a week ago we encountered the fact that it is impossible to log into our cere wallet using email. In the console I see errors about Failed to load resource: https://cyan.openlogin.com/

After searching for information a little, I realized that I have outdated libraries. I started updating them and realized that a lot has changed. Could you recommend me how to solve my problem with little effort

“dependencies”: {
“@cere-wallet/communication”: “0.0.0”,
“@cere-wallet/ui”: “0.0.0”,
“@cere-wallet/wallet-engine”: “0.0.0”,
“@fontsource/lexend”: “^4.5.13”,
“@hookform/resolvers”: “^2.9.9”,
“@polkadot/api”: “^15.5.1”,
“@polkadot/types”: “^15.5.1”,
“@ramp-network/ramp-instant-sdk”: “^3.2.3”,
“@reactour/tour”: “3.1.4”,
“@sentry/react”: “^7.53.1”,
“@toruslabs/constants”: “^13.1.0”,
“@toruslabs/fetch-node-details”: “^13.1.1”,
“@toruslabs/openlogin”: “^3.2.1”,
“@toruslabs/openlogin-session-manager”: “^3.0.0”,
“@toruslabs/openlogin-subkey”: “^7.0.0”,
“@toruslabs/openlogin-utils”: “^7.0.4”,
“@toruslabs/torus.js”: “^12.1.1”,
“@web3auth/base”: “^7.3.2”,
“axios”: “^1.1.2”,
“ed2curve”: “^0.3.0”,
“ethers”: “^5.6.9”,
“firebase”: “^9.12.1”,
“input-otp”: “^1.2.4”,
“jwt-decode”: “^3.1.2”,
“mobx”: “^6.6.2”,
“mobx-react-lite”: “^3.4.0”,
“mobx-utils”: “^6.0.5”,
“react”: “^18.2.0”,
“react-dom”: “^18.2.0”,
“react-gtm-module”: “^2.0.11”,
“react-hook-form”: “^7.37.0”,
“react-router-dom”: “^6.4.1”,
“yup”: “^0.32.11”
},

2

Thank you for sharing the detailed information about your dependencies and the issue you’re encountering. Here’s a summary of your situation, and some guidance on next steps:

Summary:

  • SDK Used: Web3Auth Plug and Play (PnP) Web SDK
  • Platform: Web (React)
  • Issue:
    • Users are unable to log in to the Cere wallet using email.
    • Console error: Failed to load resource: https://cyan.openlogin.com/
    • Dependencies appear outdated, especially Web3Auth and Torus packages.

What’s Happening

The error with cyan.openlogin.com typically results from using outdated Torus/Web3Auth libraries pointing to deprecated endpoints. Web3Auth has migrated away from older Torus endpoints to new infrastructure and SDK updates are required.

Recommended Steps

1. Update Packages

You should specifically update the following dependencies to their latest versions:

  • @web3auth/base
  • @toruslabs/openlogin
  • @toruslabs/fetch-node-details
  • Any other @toruslabs/* packages

Refer to the Web3Auth Migration Guide for detailed info on upgrading from older SDKs.

2. Check SDK Integration

Once you update, your integration patterns may need minor changes. Web3Auth has introduced new initialization flows and de-coupled Torus from the main SDK.

3. Remove Deprecated Endpoints

Double-check that you’re not manually setting URLs pointing to the old Torus network in your code/configuration.

4. Test Login

After upgrading, clear browser cache and test your login flow again.

Minimal Effort Path

  • Upgrade only the Web3Auth and Torus-related dependencies first.
  • Double-check the code for any hardcoded URLs or configurations referring to .openlogin.com.

Links for Further Reading

If the Problem Persists

If, after upgrading, the issue continues:

  • Please share your Web3Auth initialization and login code snippets (redact secrets).
  • If you see new errors, include screenshots from browser console.

Let us know how the update goes, or if you need any specific guidance on changing your initialization code!

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

What versions should I update the libraries to?

  • @web3auth/base
  • @toruslabs/openlogin
  • @toruslabs/fetch-node-details
  • Any other @toruslabs/* packages
4

I ask because looking at the changes that were made in the new versions - very serious. I don’t want to break everything

5

Hey @devops_web3auth,
I’d recommend taking a look at our PnP SDK examples here. Please try creating a small PoC using your dashboard details first — if that works, you can then align your changes based on the example app’s flow.

A lot has evolved since the older package versions you’re using were released. We currently don’t support those outdated SDKs anymore. It’s always a good idea to stay updated with the latest versions — relying on old integrations can cause unnecessary blockers down the line.