Fixed
Status Update
Comments
ju...@google.com <ju...@google.com>
je...@google.com <je...@google.com>
hm...@google.com <hm...@google.com> #2
This happens to me when using pattern+fingerprint on api 29 using 1.0.1
va...@gmail.com <va...@gmail.com> #3
happens to me on Android P using 1.0.1
hm...@google.com <hm...@google.com> #4
Is there any workaround for this? Can we expect this to be fixed?
na...@google.com <na...@google.com> #5
I am facing the same problem too! Is there any solution to this problem?
ia...@google.com <ia...@google.com> #6
Still seeing this issue on Android 10 Pixel 4.
gd...@google.com <gd...@google.com> #7
Our team is facing this issue as well. What are the alternatives available right now apart from cloning the library and changing the behavior?
hm...@google.com <hm...@google.com> #8
Biometric prompt is also not dismissed if user goes to different apps on API levels below 29. The same behavior is not true for API 29 and above. Is there any workaround for this?
Description
Coming from https://issuetracker.google.com/issues/244700433 , I changed my build.gradle files to build.gradle.kts and I had the following line:
instead of:
So the android proguard rules weren't loaded which probably caused this.
Would it be possible to warn about this when building using Gradle and potentially throw / fail the build if you're trying to use a proguard file which does not exist?