Question 1

How to handle errors in react-native-passcode-auth?

Accepted Answer

Catch errors in the promise's .catch() block using the provided error codes like LAErrorAuthenticationFailed or LAErrorUserCancel. This allows you to show user-friendly messages or implement retry logic based on the specific failure scenario.

Question 2

React Native passcode auth vs Touch ID: which should I use?

Accepted Answer

Use react-native-passcode-auth as a fallback when Touch ID or biometric sensors are unavailable. For primary biometric authentication, consider libraries like react-native-touch-id for Touch ID/Face ID, and integrate passcode auth as a backup method.

Question 3

Does react-native-passcode-auth work on Android?

Accepted Answer

No, it's iOS-only and relies on the native iOS LocalAuthentication framework. For Android authentication in React Native, you'll need a separate library or implementation, as this one doesn't support cross-platform use.

Question 4

How to customize the passcode prompt in React Native?

Accepted Answer

Customization is limited to the reason string in authenticate(), as the prompt is controlled by iOS's native dialog. For full UI control, you might need to build a custom solution or use alternative libraries that offer more flexibility.

Question 5

Is react-native-passcode-auth compatible with React Native hooks?

Accepted Answer

Yes, you can use it with hooks by calling methods like authenticate() inside useEffect or event handlers. Manage the promise with useState for state updates, similar to the example in the README but adapted for functional components.

Question 6

How to test passcode authentication in the iOS simulator?

Accepted Answer

In the iOS simulator, enable or disable passcode via the Hardware menu under 'Touch ID' or 'Face ID' settings. Use isSupported() to check compatibility and simulate authentication scenarios for debugging and testing.

Question 7

What's the difference between LAErrorPasscodeNotSet and PasscodeAuthNotSet?

Accepted Answer

LAErrorPasscodeNotSet is a native iOS error code, while PasscodeAuthNotSet is a library-specific error. Both indicate the passcode isn't set on the device, but the library provides its own error for consistency in React Native error handling.

react-native-passcode-auth

What is react-native-passcode-auth?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions