-
-
Notifications
You must be signed in to change notification settings - Fork 27
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
onComplete is not being called #16
Comments
Hi, Thanks for reporting that. Hm, I'm not sure if this is a bug. Actually, once you're authenticated and |
Hi, |
It's done like that by design. Do you have a use case, in which you're authenticating user twice within a single activity? Can you explain situation your app? If it will make sense, then we can think about re-designing the library. |
Sure. In our case, we use biometric authentication for login. However, user can choose to logout later and in that case app shows login view again. So, app has single activity and we use fragments. I believe, it’s possible use case for many apps, which use single activity approach, as navigation components has already stable versions too. |
Ok, I'll have a look how to update the library to make it work for your case. |
When I try to authenticate via fingerprint, onComplete is being invoked. After that, if I try to authenticate again successfully, onComplete is not being invoked.
The text was updated successfully, but these errors were encountered: