-
Notifications
You must be signed in to change notification settings - Fork 776
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
Disable passcode entry completely #477
Comments
Did you mean that you want to enable biometrics, but you do not want the passcode fallback, right? If so it's impossible. The passcode fallback option is always provided by the system. Otherwise you can completely disable biometrics and passcode. |
I see other apps have done it though, it possible to do it without using this library maybe? |
This configuration can also be done via the library. Give it a try. |
Please guide me sir, using this library |
I haven't tested but it should work. |
It does not work, please add the feature to your library thanks |
I have confirmed that the above code works. Perhaps you are using the library in the wrong way. |
Hey @kishikawakatsumi , thanks for the update, my case scenario is as below. keychain But when I use: keychain It doesn't show the passcode option at first but after three failed biometric auth attempts it falls back to "enter passcode", kindly confirm this 👍 |
Show full code. I believe you do not use return value or running it on the main thread. |
Here is the full code: import Foundation public struct KeyChainKeys { protocol BiometricIDService {
} class BiometricIDServiceDefault: BiometricIDService {
{
} enum BiometricType: String { private extension LAContext {
} I use the storePinForBiometricId method to store the pin and use the checkForBiometricId to fetch the key in a different view controller |
I have tried disabling by using policy authenticationPolicy: .biometryCurrentSet and authenticationPolicy: .biometryAny but after three failed attempts the app asks for a passcode. How do I remove passcode completely?
The text was updated successfully, but these errors were encountered: