The documentation for the USE_BIOMETRIC
permission says
Allows an app to use device supported biometric modalities.
But AndroidX's BiometricPrompt
works without this permission. So what exactly is it needed for?
READ_PHONE_STATE is one of the Android permissions categorized as dangerous. This is because it “allows read only access to phone state, including the phone number of the device, current cellular network information, the status of any ongoing calls, and a list of any Phone Accounts registered on the device” [2] .
The android.permission.READ_PHONE_STATE or the “Read Phone State and Identity” permission can be used to do a range of tasks, from simple things to quite invasive: - turning an application's sound off when a call comes in. - verifying the user/phone with IMEI information.
Apps that target Android 10 or higher and use notifications with fullscreen intents must request the USE_FULL_SCREEN_INTENT permission in their app's manifest file. This is a normal permission, so the system automatically grants it to the requesting app.
android.permission.GET_ACCOUNTS. Allows access to the list of accounts in the Accounts Service. The app uses this permission in an effort to find the device user's name when the support session is presented to a representative.
Works because the library already declares it in its own manifest:
https://android.googlesource.com/platform/frameworks/support/+/63add6e2590077c18556dcdd96aa5c6ff68eb13b/biometric/biometric/src/main/AndroidManifest.xml
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With