Repository navigation
fix: bump Auth0.Android to 3.21.2 for biometric failure fix - #968
Conversation
Auth0.Android 3.21.2 stops reporting an unrecognized biometric as a final failure, so credentials reads with local authentication no longer fail when the user retries and authenticates successfully. Also bumps the example app's auth0-spa-js to 2.24.1. Co-Authored-By: Claude <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
WalkthroughThe Android module now declares ChangesAndroid dependency update
Priority: ➖ Normal Estimated code review effort: 1 (Trivial) | ~5 minutes Change: Other Suggested reviewers: Merge Risk: ⚪ Minimal · up to
|
📋 Changes
3.21.1to3.21.2inauth0_flutter/android/build.gradle.2.24.0to2.24.1inauth0_flutter/example/web/index.html. The README's script tag uses the/2.24/CDN path, which already serves2.24.1, so the README is unchanged.Why: Auth0.Android
3.21.2fixesSecureCredentialsManagerwith local authentication reporting an unrecognized biometric as a final failure.BiometricPromptcallsonAuthenticationFailed()when it reads a biometric it doesn't recognize, but the prompt stays open and the real result comes later. Auth0.Android was treating that callback as a failure, so a singlegetCredentials()/getApiCredentials()call could produce a failure and then a success.This plugin passes those results to Dart over the method channel. Apps using
auth0_flutterwithlocalAuthenticationon Android could therefore seecredentials()fail even when the user then authenticated successfully, for example via the device credential fallback.No Dart or Kotlin source changes, and no public API changes.
🎯 Testing
:auth0_flutter:compileDebugUnitTestKotlinbuilds againstcom.auth0.android:auth0:3.21.2(confirmed via:auth0_flutter:dependencies).