Native app issues

MetaMask SDK
2

Hi Benjamin — thanks for the clear write-up. I hear you — wallet/signature flows that work in some mobile contexts but not others are annoying, and it’s good you prioritized MetaMask for your user base. I pulled the key details below and noted what’s missing so the support team can investigate quickly.

Summary of details I grabbed from your message

  • SDK details: thirdweb for wallet connection and account abstraction (Generic Thirdweb integration)
  • SDK version number: not provided
  • Platform: iOS (MetaMask native app built-in browser; you also mentioned Safari / Chrome native mobile browsers)
  • Issue: WalletConnect signature prompt wouldn’t appear in MetaMask native app’s built-in browser; switching chains/accounts didn’t help; updating the MetaMask app to the latest version fixed it for you

Quick questions / items that will help us reproduce and triage (please only share what’s easy for you):

  • Which thirdweb package/version are you using (e.g., @thirdweb-dev/react vX.Y.Z)?
  • Which connector/protocol are you using under the hood: WalletConnect v1 or v2, or MetaMask SDK / injected provider? (Thirdweb can be configured with different connectors.)
  • Minimal code snippets showing how you initialize/connect (initialization + login/connect snippet). That helps identify if a particular WalletConnect config is being used.
  • Reproduction steps (exact flow that fails) and whether the failure is deterministic or intermittent
  • Browser console screenshots / logs (if reproducing in a browser where you can access console). For the MetaMask in-app browser, console isn’t accessible — in that case, a step-by-step repro and the MetaMask app version are most helpful.

Helpful pointers and short suggestions you can try now

  • App update: On iOS you update MetaMask via the App Store (there isn’t a separate “update” button inside the MetaMask app). You can find the app version inside MetaMask → Settings → About → Version. Here’s the App Store link if you want to surface it for users: ‎MetaMask: Crypto & Web3 Wallet App - App Store
  • Workaround: if users see signature prompts failing in an external browser (Safari/Chrome), ask them to try the MetaMask in-app browser (or vice versa) because some iOS WebView behaviors/third-party browser restrictions can interfere with WalletConnect/injected provider flows.
  • Keep dependencies up to date: ensure you’re on the latest thirdweb connector code and WalletConnect version (many mobile-specific bugs have been fixed in newer releases).

Docs/links you may find useful

If you want, paste your thirdweb init/connect code and the package versions you’re using and I’ll flag anything obvious. Once you provide those (and the MetaMask app version you saw the bug on), I’ll escalate this to the support team with the exact repro details so they can follow up. Thanks again — appreciate you reporting this and helping make the experience smoother for mobile users.

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