Various PlatformExceptions recorded with single_factor_auth_flutter version SDK 7.0.1 (latest version)

Embedded Wallets (Web3Auth)
2

Thanks — I hear you and I appreciate the detailed info. I’ve pulled the key facts and written up likely causes + next steps so the support team can triage quickly.

Summary of what you reported

  • SDK: MetaMask Embedded Wallets (Web3Auth) — single_factor_auth_flutter
  • SDK version: 7.0.1 (latest)
  • Platform / Framework: Flutter (Android release builds impacted)
  • Network: sapphire_mainnet
  • Errors seen (Crashlytics / screenshot):
    • PlatformException(error, null, null, null)
    • PlatformException(error, lateinit property singleFactorAuth has not been initialized, …)
    • PlatformException(error, public nonce is missing, public nonce is missing, …)
  • You’ve already added a proguard-rules.pro (content included in your message) and clearing app data/cache temporarily resolves the issue for affected users.

What I still need (only if you don’t already have it handy)
Please share these only if you can — they’re most useful for reproducing/fixing the bug and won’t be requested otherwise:

  • The Flutter code snippet that initializes the single_factor_auth_flutter SDK and the login snippet (where you call into the SDK). If you have a custom Application class or native Android init, include that.
  • Android release Gradle settings relevant to R8/ProGuard (minifyEnabled, shrinkResources, proguardFiles entries used for release). A quick paste of the buildTypes { release { … } } block is enough.
  • A full Crashlytics stacktrace / relevant logcat lines for the two exceptions (especially the public nonce error). The screenshot helps but the textual stacktrace is more actionable.
  • Whether the problem reproduces on a debug build (minify disabled) or only on proguard/minified release builds.
  • Devices / Android OS versions where you see the issue most commonly (if known).

Immediate hypotheses and recommended checks (so you can try quick fixes)

  1. Race / initialization ordering (likely cause of lateinit singleFactorAuth error)
  • Symptom:

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