I keep getting an error when I try to log in to Apple using Web3Auth

Embedded Wallets (Web3Auth)
2

Thanks — I’ve read your report. You’re hitting a session/cookie error when trying Apple login via Web3Auth in React Native. I’ve compiled the key info for the support team and included focused troubleshooting and next steps below.

Summary (extracted from your report)

  • SDK Details: MetaMask Embedded Wallets (Web3Auth)
  • SDK Package: @web3auth/react-native-sdk
  • SDK Version Number: v8.1.0
  • Platform / Framework: React Native (react-native 0.75.4)
  • Other Web3Auth packages: @web3auth/* at ^9.6.0 (auth-adapter, base, ethereum-provider, solana-provider)
  • Repro steps: login with LOGIN_PROVIDER.APPLE using WebBrowser + EncryptedStorage
  • Exact error: “You may have pressed the back button, refreshed during login, opened too many login dialogs, or there is some issue with cookies, since we couldn’t find your session. Try logging in again from the application and if the problem persists please contact the administrator.”
  • Code snippet (provided): initialization + web3Auth.login({ loginProvider: LOGIN_PROVIDER.APPLE })

Notes / immediate red flags

  • Version mismatch: your react-native SDK is 8.1.0 while other @web3auth packages are 9.6.0. That can cause compatibility/session issues. Consider aligning/upgrading to the recommended compatible versions.
  • The message is consistent with a redirect/deep-link or cookie/session loss during the external browser OAuth flow (very common with Sign in with Apple on mobile).

Checklist — Quick things to verify (most likely causes)

  1. Redirect URL exact match
    • Ensure the redirectUrl you pass to Web3Auth exactly matches what you registered in the Apple Developer console and in the Web3Auth dashboard. Even small differences (trailing slash, scheme case) break the flow.
  2. Apple Developer setup
    • Services ID, Bundle ID, Sign in with Apple capability are enabled. The redirect URI for the Service ID must match the app’s redirect URL.
  3. Deep linking / redirect handling in app
    • Confirm iOS URL types / Android intent filters are configured so the app receives yourapp://auth (or whatever your redirect scheme is).
    • Ensure your redirect scheme is registered in both Info.plist (iOS) and AndroidManifest (Android). See web3auth deep link setup docs.
  4. Avoid interruptions + single login flow
    • Don’t press back, don’t open multiple login dialogs. Test on a real device (not just simulator) and avoid Expo Go (use bare workflow).
  5. Test whether other social logins work
    • Try another provider (Google) to determine if it’s Apple-specific or general session/deep-link problem.
  6. Package compatibility
    • Upgrade @web3auth/react-native-sdk to a version compatible with the other @web3auth/* packages, or align all @web3auth packages to the same major release. Check Web3Auth release notes for RN breaking changes.

If the problem persists — please provide (only if not already provided)

  • The exact redirect URI you configured (paste the string here) — I won’t need secrets.
  • Confirmation of deep link config (e.g., the URL scheme configured in Info.plist / AndroidManifest). If you already provided this, no need to repeat.
  • A screenshot of the browser/console error or device logs during the failed flow (useful but optional).

Suggested immediate steps you can try now

  1. Align package versions (upgrade/downgrade so @web3auth/react-native-sdk matches the other @web3auth packages) and rebuild.
  2. Double-check the exact redirectUrl string in Apple Developer → Services ID and in the Web3Auth dashboard. Must be identical to the redirectUrl passed into new Web3Auth(…).
  3. Verify your deep link handling in the app (Info.plist URL types / Android intent filters). Follow the Web3Auth RN deep-link guide.
  4. Test on a real device (not Expo Go) and ensure only one login attempt runs at a time.
  5. Try a different provider (e.g., Google) to confirm whether the embedded browser/session flow is working.

Relevant docs

If you want, paste the redirect URI you’ve configured and confirm whether you’re using a real device and bare RN workflow — I’ll review those and point out any mismatches. If you’ve already checked those and aligned versions, attach a screenshot/log and I’ll escalate to the support team with the summary above.

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