-
Notifications
You must be signed in to change notification settings - Fork 476
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
touch id no longer supported if user fails to authenticate too many times #48
Comments
I could be wrong, but I think this is baked into how iOS implements Touch ID. You can reproduce this behaviour simply by trying to log into your phone with Touch ID. If you fail three times, then you have to re-enter your passcode before you can re-enable Touch ID. It seems to me that if one fails to successfully authenticate after three attempts, iOS disables Touch ID support until the user has re-enabled it by entering in their passcode. I'd love to know if you know any way around this, or have heard otherwise. |
@zibs that makes sense. I tried on another app (LastPass) and after failing to authenticate, it said I could reenable it from Settings, but I didn't see the option. This library does not seem to support re-enabling, would be a great feature. Again, not sure what support for this looks like on the native ios level UPDATE (5 minutes later lol) thanks! |
Would you mind posting screenshots or linking to official Apple TouchID
documentation?
…On Thu, Aug 31, 2017 at 3:33 PM Cole Bradley ***@***.***> wrote:
@zibs <https://github.com/zibs> that makes sense. I tried on another app
(LastPass) and after failing to authenticate, it said I could reenable it
from Settings, but I didn't see the option. This library does not seem to
support re-enabling, would be a great feature. Again, not sure what support
for this looks like on the native ios level
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#48 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABjWsNYaCmz-uE0pJTQVhTkzgL_EmBm4ks5sdzTCgaJpZM4PIIFu>
.
|
@naoufal did you see the update to my comment? not seeing anything relevant in the docs or general google searching. here is the alert from lastpass: |
Thanks for the great lib!
If a user enters an invalid touch too many times, touch id is permanently no longer supported for the app. Is this intended behavior? Seems like strange behavior and in our case not desirable. Any insight into this?
Ideally I think, it would be up to application devs if we want to disable touch support on too many failures. or at least there should be a way to enable it again?
Thanks!!!
The text was updated successfully, but these errors were encountered: