-
Notifications
You must be signed in to change notification settings - Fork 13
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
Biometrics not working on multiple instances #620
Comments
Raised bug to "critical", because it's already problematic on client's production. |
The issue has to be fixed in the following release branches:
|
hvge
added a commit
that referenced
this issue
Sep 16, 2024
hvge
added a commit
that referenced
this issue
Sep 17, 2024
hvge
added a commit
that referenced
this issue
Sep 20, 2024
hvge
added a commit
that referenced
this issue
Sep 20, 2024
hvge
added a commit
that referenced
this issue
Sep 20, 2024
hvge
added a commit
that referenced
this issue
Sep 20, 2024
hvge
added a commit
that referenced
this issue
Sep 20, 2024
hvge
added a commit
that referenced
this issue
Sep 23, 2024
Store biometry key for each PowerAuthSDK instance (1.7.x)
hvge
added a commit
that referenced
this issue
Sep 23, 2024
Store biometry key for each PowerAuthSDK instance (1.8.x)
hvge
added a commit
that referenced
this issue
Sep 23, 2024
Store biometry key for each PowerAuthSDK instance
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On Android, when multiple instances (with different instanceId) of
PowerAuthSDK
are created, signing with biometrics only works on the latest instance.This is due to the shared biometric key, which is force-recreated when the biometrics factor is turned on (or activation is removed) making any biometrics already added on other instances invalid.
We should also consider adding documentation and tests that are working with multiple instances because many nuances when working in such a setup are undocumented and unexpected by default.
Note: this is not an issue on iOS where this works correctly.
The text was updated successfully, but these errors were encountered: