Hi roy — thanks for the clear report. It sounds like you’re reporting an issue (not exploring a new integration) where the OKX option in Web3Auth on mobile Chrome always redirects to an old OKX download page instead of deep-linking into the installed OKX app.
Summary of what I extracted from your message (so the support team can triage quickly):
- SDK Details: MetaMask Embedded Wallets (using Web3Auth integration)
- Platform: Web (mobile web)
- Framework: Next.js + React + TypeScript
- Browser: Chrome on Android (not an in-app WebView)
- Web3Auth usage: calling web3auth.connect() for social/login flow
- Issue: Selecting OKX in Web3Auth always opens an external “download OKX” landing page instead of deep-linking into the installed OKX app
Helpful next info (only request things you haven’t already provided):
- Exact Web3Auth package names and versions from your package.json (e.g. @web3auth/modal, @web3auth/core, @web3auth/openlogin, etc.). If you don’t know, a copy/paste of the relevant package.json deps is perfect.
- The Web3Auth initialization snippet you use (the code where you construct the Web3Auth instance / adapters) and the call site where you call web3auth.connect(). If any adapter options or custom modal settings are used, include those lines. (You already said you call web3auth.connect() — paste the actual code if available.)
- A screenshot of the landing page that appears and any browser console output (errors or warnings) captured when selecting OKX. If possible, a HAR or network trace of the redirect sequence is helpful.
- Does this happen on multiple Android devices and Chrome versions, or only one device/version?
What to try right now (possible causes & quick checks):
- Confirm Web3Auth OKX adapter support and version — older Web3Auth adapters may use an older OKX link/flow. If you’re on older @web3auth packages, upgrading may fix it.
- Remote-debug Chrome on your phone (chrome://inspect) and capture the console/network activity while choosing OKX — that often shows whether the SDK is calling an old OKX URL or whether the browser is rewriting the link.
- Try manually opening OKX’s deep-link URI (if you know it) from the browser address bar or a test link to see if the device handles the scheme correctly. If the scheme resolves to the app, then the problem is likely Web3Auth using a wrong URL; if it doesn’t, the device/OKX app may not have registered the intent.
- As a temporary workaround, consider allowing users to authenticate via WalletConnect (if OKX supports it) or another provider until the OKX deep-link is resolved.
Relevant docs to check:
- MetaMask docs: https://docs.metamask.io
- MetaMask Builder Hub: https://builder.metamask.io
- Web3Auth docs (for adapter config & deep linking behavior): Introduction | Documentation | Web3Auth
- Chrome remote debugging guide (to capture console logs on mobile): Remote debug Android devices | Chrome DevTools | Chrome for Developers
If you want, paste the package.json deps and your Web3Auth initialization + connect snippet and I’ll look for likely misconfiguration or adapter version issues. If you can attach the console screenshot or the final redirect URL that opens, that will speed up triage. I’ll follow up once you provide those details — thanks for reporting this, and I’ll help get it tracked with the support team.
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 biweekly Office Hours to get this resolved even faster. MetaMask Developer Office Hours