capacitor-biometric-auth  

This plugin for Capacitor 8 provides access to native biometry and device credentials on iOS and Android. It supports every type of biometry and every configuration option on both platforms. In addition, biometry and device credentials are simulated on the web so you can test your logic without making any changes to your code.

🛑 BREAKING CHANGES:

• If you are upgrading from a version prior to 9.0.0, please note that this plugin now requires Capacitor 8+.

• If you are upgrading from a version prior to 8.0.0, please note that addResumeListener now always returns a Promise and must be awaited.

• If you are upgrading from a version prior to 7.0.0, please note that authenticate() will immediately present a prompt for device credentials if deviceIsSecure is true, allowDeviceCredentials is true, and no biometry of the requested strength is available.

• If you are upgrading from a version prior to 6.0.0, please note that authenticate() now throws an instance of BiometryError, and BiometryError.code is now typed as BiometryErrorType.

Installation

pnpm add @aparajita/capacitor-biometric-auth
npm install @aparajita/capacitor-biometric-auth
yarn add @aparajita/capacitor-biometric-auth

Not using pnpm? You owe it to yourself to give it a try. It’s faster, better with monorepos, and uses way, way less disk space than the alternatives.

iOS

This plugin can be installed via Swift Package Manager (SPM) or CocoaPods:

• Swift Package Manager (recommended): No additional steps required. Capacitor 7+ automatically uses SPM.
• CocoaPods (legacy): Still fully supported. The plugin will work with existing CocoaPods-based projects.

👉 IMPORTANT!! In order to use Face ID, you must add the NSFaceIDUsageDescription key to your Info.plist file. This is a string that describes why your app needs access to Face ID. If you don't add this key, the system won't allow your app to use Face ID.

1. In Xcode, open your app’s Info.plist file.
2. Hover your mouse over one of the existing keys, and click the + button that appears.
3. In the popup that appears, type Privacy - Face ID Usage Description and press Enter.
4. In the Value column, enter a string that describes why your app needs access to Face ID.
5. Save your changes.

Usage

The API is extensively documented in the TypeScript definitions file. There is also (somewhat incomplete auto-generated) documentation below. For a complete example of how to use this plugin in practice, see the demo apps: CocoaPods variant or SPM variant.

Checking availability

Although not strictly necessary, before giving the user the option to use biometry (such as displaying a biometry icon), you will probably want to call checkBiometry() and inspect the CheckBiometryResult to see what (if any) biometry and/or device credentials are available on the device. Note the following:

• isAvailable may be false but biometryType may indicate the presence of biometry on the device. This occurs if:

  • The current user is not enrolled in biometry.
  • Biometry has been disabled for the current app.
  • On Android, biometric hardware is present but can only be used for device unlock, not by apps. see the Android note below for more information.

  In such cases the reason and code will tell you why.

• On iOS, isAvailable and strongBiometryIsAvailable will always have the same value, because traditionally that’s the whole point of biometry — it’s supposed to be strong authentication.

• Android unfortunately supports “strong” biometry (usually fingerprint) and “weak” biometry (usually face/iris). isAvailable will be true if any type of biometry is actually available for use by the app, but strongBiometryIsAvailable will be true only if strong biometry is available. For example, on a typical device, if it has hardware support for both fingerprint and face unlock, and both are available for use by apps, isAvailable will be true if either is enrolled, but strongBiometryIsAvailable will be true only if fingerprint authentication is enrolled.

❗Android note

When it comes to biometry, Android is frankly a bit of a mess. Some devices may support “weak” biometry (e.g. face unlock) only for device unlock, and not by apps. But the system reports to this plugin all types of biometric hardware, even if they are not available for use by apps.

👉 Therefore on Android the only thing you can rely on are the isAvailable and strongBiometryAvailable properties as simple on/off switches. Do NOT rely on biometryType and biometryTypes as an indication of what biometry you can actually use.

Handling app resume

Because the availability of biometry can change while your app is in the background, it’s important to check availability when your app resumes. By calling addResumeListener() you can register a callback that is passed a CheckBiometryResult when your app resumes.

Example

import { CheckBiometryResult } from './definitions'

let appListener: PluginListenerHandle

function updateBiometryInfo(info: CheckBiometryResult): void {
  if (info.isAvailable) {
    // Biometry is available, info.biometryType will tell you the primary type.
  } else {
    // Biometry is not available, info.reason and info.code will tell you why.
  }
}

async function onComponentMounted(): Promise<void> {
  updateBiometryInfo(await BiometricAuth.checkBiometry())

  try {
    appListener = await BiometricAuth.addResumeListener(updateBiometryInfo)
  } catch (error) {
    if (error instanceof Error) {
      console.error(error.message)
    }
  }
}

async function onComponentUnmounted(): Promise<void> {
  await appListener?.remove()
}

Authenticating

To initiate biometric authentication call authenticate(). authenticate takes an AuthenticateOptions object which you will want to use in order to control the behavior and appearance of the biometric prompt.

If authentication succeeds, the Promise resolves. If authentication fails, the Promise is rejected with an instance of BiometryError, which has two properties:

Property	Type	Description
message	string	A description of the error suitable for debugging
code	BiometryErrorType	What caused the error

Example

import {
  AndroidBiometryStrength,
  BiometryError,
  BiometryErrorType,
} from './definitions'

async function authenticate(): Promise<void> {
  try {
    await BiometricAuth.authenticate({
      reason: 'Please authenticate',
      cancelTitle: 'Cancel',
      allowDeviceCredential: true,
      iosFallbackTitle: 'Use passcode',
      androidTitle: 'Biometric login',
      androidSubtitle: 'Log in using biometric authentication',
      androidConfirmationRequired: false,
      androidBiometryStrength: AndroidBiometryStrength.weak,
    })
  } catch (error) {
    // error is always an instance of BiometryError.
    if (error instanceof BiometryError) {
      if (error.code !== BiometryErrorType.userCancel) {
        // Display the error.
        await showAlert(error.message)
      }
    }
  }
}

Biometry support

web

On the web, you can fake any of the supported biometry types by calling setBiometryType().

iOS

On iOS, Touch ID and Face ID are supported.

Android

On Android, fingerprint, face, and iris authentication are supported. Note that if a device supports more than one type of biometry, the plugin will initially present the primary (most secure) available type, which is determined by the system and cannot be determined programmatically.

❗ As discussed above, Android may support multiple types of biometry, but not all of them may be available for use by apps. For example, a device may support both fingerprint and face authentication, but only fingerprint authentication may be available for use by apps. In such cases, if the user has enrolled in face authentication only, checkBiometry() will indicate that biometry is not available.

API

• checkBiometry()
• setBiometryType(...)
• setBiometryIsEnrolled(...)
• setDeviceIsSecure(...)
• authenticate(...)
• addResumeListener(...)
• Interfaces
• Type Aliases
• Enums

This is the public interface of the plugin.

checkBiometry()

checkBiometry() => Promise<CheckBiometryResult>

Check to see what biometry type (if any) is available.

Returns: Promise<CheckBiometryResult>

---

setBiometryType(...)

setBiometryType(type: BiometryType | string | Array<BiometryType | string> | undefined) => Promise<void>

web only

On the web, this method allows you to dynamically simulate different types of biometry. You may either pass BiometryType enums or the string names of the BiometryType enums. If undefined or a string is passed and it isn't a valid value, nothing happens.

Param	Type
type	string | BiometryType | (string | BiometryType)[]

---

setBiometryIsEnrolled(...)

setBiometryIsEnrolled(isSecure: boolean) => Promise<void>

web only

On the web, this method allows you to dynamically simulate whether or not the user has enrolled in biometry.

Param	Type
isSecure	boolean

---

setDeviceIsSecure(...)

setDeviceIsSecure(isSecure: boolean) => Promise<void>

web only

On the web, this method allows you to dynamically simulate whether or not the user has secured the device with a PIN, pattern or passcode.

Param	Type
isSecure	boolean

---

authenticate(...)

authenticate(options?: AuthenticateOptions) => Promise<void>

Prompt the user for authentication. If authorization fails for any reason, the promise is rejected with a BiometryError.

For detailed information about the behavior on iOS, see:

https://developer.apple.com/documentation/localauthentication/lapolicy/deviceownerauthenticationwithbiometrics

Some versions of Android impose a limit on the number of failed attempts. If allowDeviceCredential is true, when the limit is reached the user will then be presented with a device credential prompt. If allowDeviceCredential is false, when the limit is reached authenticate() will reject with a BiometryErrorType of biometryLockout, after which the user will have to wait the system-defined length of time before being allowed to authenticate again.

Param	Type
options	AuthenticateOptions

---

addResumeListener(...)

addResumeListener(listener: ResumeListener) => Promise<PluginListenerHandle>

Register a function that will be called when the app resumes. The function will be passed the result of checkBiometry().

👉 NOTE: checkBiometry() must be called at least once before calling this method.

Param	Type
listener	ResumeListener

Returns: Promise<PluginListenerHandle>

---

Interfaces

CheckBiometryResult

Property	Type	Description
isAvailable	boolean	True if the device supports at least weak biometric authentication by apps and the current user has enrolled in some form of biometry. Note that if strongBiometryIsAvailable is true, this will also be true.
strongBiometryIsAvailable	boolean	True if the device has strong biometric authentication capability and the current user has enrolled in that strong biometry. On iOS this value and isAvailable will always be the same, since iOS only supports strong biometry. On Android, for example, if the device supports both fingerprint and face authentication by apps, and the user has enrolled only in face authentication, and Android considers face authentication on that device to be weak, then isAvailable will be true but this value will be false.
biometryType	BiometryType	The primary (most secure) type of biometry supported by the device. Note that supported is not the same as available, which requires the biometry to be enrolled.
biometryTypes	BiometryType[]	All of the biometry types supported by the hardware on the device, whether or not it is actually available for use by apps. If no biometry is supported, i.e. biometryType === <a href="#biometrytype">BiometryType.none, this will be an empty array. Note that supported is not the same as available, which requires the biometry to be enrolled.
deviceIsSecure	boolean	Returns true if the device is secure. On iOS, this means that the device has a passcode set. On Android, this means that the device has a PIN, pattern, or password set.
reason	string	If weak or better biometry is not available and the system gives a reason why, it will be returned here. Otherwise it's an empty string.
code	BiometryErrorType	If weak or better biometry is not available, the error code will be returned here. Otherwise it's an empty string. The error code will be one of the BiometryErrorType enum values, and is consistent across platforms.
strongReason	string	If strong biometry is not available and the system gives a reason why, it will be returned here. Otherwise it's an empty string. On iOS, this will always be the same as reason, since all biometry on iOS is strong.
strongCode	BiometryErrorType	If strong biometry is not available, the error code will be returned here. Otherwise it's an empty string. The error code will be one of the BiometryErrorType enum values, and is consistent across platforms. On iOS, this will always be the same as code, since all biometry on iOS is strong.

AuthenticateOptions

Prop	Type	Description
reason	string	Displays the reason for requesting authentication in the authentication dialog presented to the user. Default: System default
cancelTitle	string	iOS: The system presents a cancel button during biometric authentication to let the user abort the authentication attempt. The button appears every time the system asks the user to present a finger registered with Touch ID. For Face ID, the button only appears if authentication fails and the user is prompted to try again. Either way, the user can stop trying to authenticate by tapping the button. Android: The text for the negative button. This would typically be used as a "Cancel" button, but may be also used to show an alternative method for authentication, such as a screen that asks for a backup password. Default: "Cancel"
allowDeviceCredential	boolean	If true, allows for authentication using device unlock credentials. Default: false. iOS: If biometry is available, enrolled, and not disabled, the system uses that first. After the first Touch ID failure or second Face ID failure, if iosFallbackTitle is not an empty string, a fallback button appears in the authentication dialog. If the user taps the fallback button, the system prompts the user for the device passcode or the user’s password. If iosFallbackTitle is an empty string, no fallback button will appear. If no biometry is enrolled and enabled, and a passcode is set, the system immediately prompts the user for the device passcode or user’s password. Authentication fails with the error code passcodeNotSet if the device passcode isn’t enabled. If a passcode is not set on the device, a passcodeNotSet error is returned. The system disables passcode authentication after 6 unsuccessful attempts, with progressively increasing delays between attempts. The title of the fallback button may be customized by setting iosFallbackTitle to a non-empty string. Android: The user will first be prompted to authenticate with biometrics, but also given the option to authenticate with their device PIN, pattern, or password by tapping a button in the authentication dialog. The title of the button is supplied by the system.
iosFallbackTitle	string	The system presents a fallback button when biometric authentication fails — for example, because the system doesn’t recognize the presented finger, or after several failed attempts to recognize the user’s face. If allowDeviceCredential is false, tapping this button dismisses the authentication dialog and returns the error code userFallback. If undefined, the localized system default title is used. Passing an empty string hides the fallback button completely. If allowDeviceCredential is true and this is undefined, the localized system default title is used.
androidTitle	string	Title for the Android dialog. If not supplied, the system default is used.
androidSubtitle	string	Subtitle for the Android dialog. If not supplied, the system default is used.
androidConfirmationRequired	boolean	Determines if successful weak biometric authentication must be confirmed. For information on this setting, see https://developer.android.com/reference/android/hardware/biometrics/BiometricPrompt.Builder#setConfirmationRequired(boolean). Default: true
androidBiometryStrength	AndroidBiometryStrength	Set the strength of Android biometric authentication that will be accepted. 👉 NOTE: On Android 9 & 10 (API 28-29), this will effectively always be .weak if allowDeviceCredential is true. This is a known limitation of the Android API. 🤯 Default: AndroidBiometryStrength.weak

PluginListenerHandle

Method	Signature
remove	() => Promise<void>

Type Aliases

ResumeListener

The signature of the callback passed to addResumeListener().

(info: CheckBiometryResult): void

Enums

BiometryType

Members	Description
none
touchId	iOS Touch ID
faceId	iOS Face ID
fingerprintAuthentication	Android fingerprint authentication
faceAuthentication	Android face authentication
irisAuthentication	Android iris authentication

BiometryErrorType

Members	Value
none	''
appCancel	'appCancel'
authenticationFailed	'authenticationFailed'
invalidContext	'invalidContext'
notInteractive	'notInteractive'
passcodeNotSet	'passcodeNotSet'
systemCancel	'systemCancel'
userCancel	'userCancel'
userFallback	'userFallback'
biometryLockout	'biometryLockout'
biometryNotAvailable	'biometryNotAvailable'
biometryNotEnrolled	'biometryNotEnrolled'
noDeviceCredential	'noDeviceCredential'

AndroidBiometryStrength

Members	Description
weak	authenticate() will present any available biometry.
strong	authenticate() will only present strong biometry.