You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 9ab9910
Browse filesBrowse the repository at this point in the historyBrowse files
fix(expo-biometrics): report missing secure key storage on Android
Report secureKeyStorageAvailable from getAvailability() on Android (false
below API 28) and reject createKey() there with
secure_key_storage_unavailable instead of biometry_not_available.
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
Copy file name to clipboardExpand all lines: packages/expo-biometrics/README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,7 +37,7 @@ The key and record layout is shared with the Clerk iOS and Android SDKs, so cred
37
37
- Expo SDK 54 or later, in a development build (the module is not available in Expo Go or on the web)
38
38
- iOS: `NSFaceIDUsageDescription` in your `Info.plist`. The `@clerk/expo` config plugin sets it through its `faceIDPermission` option.
39
39
- iOS: a device with a Secure Enclave. The iOS Simulator has none, so `createKey()` rejects there with `secure_key_storage_unavailable`.
40
-
- Android 9 (API level 28) or later with a strong (Class 3) biometric. On older versions every key operation rejects with `biometry_not_available`.
40
+
- Android 9 (API level 28) or later with a strong (Class 3) biometric. On older versions `getAvailability()` reports `secureKeyStorageAvailable: false`, `createKey()`rejects with `secure_key_storage_unavailable`, and `sign()` with `biometry_not_available`.
0 commit comments