Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

opens TouchID, not passcode #1

Open
davidskaarup opened this issue Jan 17, 2016 · 5 comments
Open

opens TouchID, not passcode #1

davidskaarup opened this issue Jan 17, 2016 · 5 comments

Comments

@davidskaarup
Copy link

When I call PasscodeAuth.authenticate I don't get the passcode screen, but instead the TouchID dialog and can validate with my fingerprint. I might be misunderstanding something, but I thought this should launch passcode directly and you should use react-native-touchid for touch validation.

If I select "Enter passcode" after a failed touch validation the passcode screen opens.

@DannyvanderJagt
Copy link

@davidskaarup After some searching I found out that when TouchID is enabled (on the device) it is impossible to get only the passcode screen. (without getting the TouchID dialog first). The best solution would be to create a custom password screen for your app.

@davidskaarup
Copy link
Author

@DannyvanderJagt Thanks for the answer. If I understand correctly that means that it is actually better to use this component for validation over react-native-touchid since it automatically launches passcode or touchid depending on what the device supports.

@DannyvanderJagt
Copy link

@davidskaarup I looked at the source code and it looks like that this component is created as fallback for react-native-touch-id. When touch-id is not supported or activated this component can be used to provide the passcode screen. However I found the component: react-native-local-auth (a fork of react-native-touch-id) which combines touch-id and the password screen as fallback in one component. It also supports more features like touch-id only and the option to disallow enter password fallback.

@alexandergunnarson
Copy link

@davidskaarup Good catch. I think it would be nice to note that somewhere in the docs, as the required combination of try-touch-ID-first-and-only-then-fall-back-to-passcode is a little misleading. That said, this is a great component and it's really useful.

@Krish143git
Copy link

@davidskaarup I looked at the source code and it looks like that this component is created as fallback for react-native-touch-id. When touch-id is not supported or activated this component can be used to provide the passcode screen. However I found the component: react-native-local-auth (a fork of react-native-touch-id) which combines touch-id and the password screen as fallback in one component. It also supports more features like touch-id only and the option to disallow enter password fallback.

@DannyvanderJagt Finally i seen your comment. You are legend bro i tried many packages react-native-biometrics,react-native-finger-print-scanner ,react-native-Touch ID , React-native-passcode-auth but not happy .This react-native-local-auth looks like phone pay lock behaviour.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants