Thanks — I checked our Embedded Wallets docs. Short answer: MetaMask’s mobile app uses deeper, wallet-level native integration and session preloading that third‑party React Native apps can’t fully replicate, but you can often speed up onboarding a lot with a few changes.
What I need from you to help further (only if you haven’t already):
- SDK & package versions (Embedded Wallets / @web3auth/react-native-sdk exact version)
- RN environment: Expo (Dev client/EAS) or bare React Native
- Platform: iOS, Android, or both
- Are you using Web3Auth’s default social web login (webview) or a native Google Sign‑In flow?
Quick, practical optimizations to try now:
- Use native provider + custom JWT verifier: perform Google Sign‑In natively, mint a short‑lived JWT on your server and pass it to Web3Auth (this avoids the Google web popup). Note: JWT must include iat within 60s.
- Headless/no-modal + pre-initialize Web3Auth on app start and enable session caching to avoid full re-auth on each onboarding.
- Ensure deep links, bundle/package allowlisting, and Info.plist/AndroidManifest entries match the dashboard exactly.
- Import required polyfills (react-native-get-random-values, buffer/process polyfills) before any app code and use a custom Expo dev client if using Expo.
- Measure where time is spent (native sign-in vs webview load). If you can, capture a short video or timing logs.
If you share the SDK version, RN type (Expo vs bare), and whether you already use native Google sign-in, I’ll route this to the team with concrete next steps or a short checklist tuned to your setup. If anything here is unclear, someone on the team will follow up and help implement.
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