Fixed
Status Update
No update yet.
Comments
20...@gmail.com
My application offers 'suggested applications' that it can install and then use the functionality of, acting as a plug-in. Tasker is one of those.
My only work-around is to prompt the user to reinstall my application after the suggested applications have been installed, so permissions are detected.
It's of course a horrible 'solution'. Have starred the issue.
brandall
My only work-around is to prompt the user to reinstall my application after the suggested applications have been installed, so permissions are detected.
It's of course a horrible 'solution'. Have starred the issue.
brandall
cu...@google.com
kc...@google.com
ap...@google.com
pr...@google.com
Using the terminology from the original issue report, one workaround is for App A *and* App B to define the same <permission>. This gets a bit dicey in plugin situations, where App A is not written by the author of App B, only because App A would need all relevant resources (e.g., internationalized strings). OTOH, it works.
Description
"Android 9 only includes fingerprint integration for BiometricPrompt. However, integrated support for other biometric modalities are forthcoming." - is it forthcoming to Android 9 and above, or to Android 10 and above?
"On devices running P and above, this will show a system-provided authentication prompt, using a device's supported biometric (fingerprint, iris, face, etc)." - we tested this on Galaxy S10, S9, S8, all of which are currently on P and all of which has a system setting for iris / face id, and got a fingerprint dialog only with BiometricPrompt. So again, is iris/face supposed to work on Android 9 with this API? Or is the issue that Samsung's sensors are considered "weak biometrics" so they will never be supported by BiometricPrompt? Is there a strong biometrics device on the market (besides the upcoming Pixel 4) to which face support is coming with BiometricPrompt on Android 9?