Permissions

Question 1

Why require permissions in Android?

Answer 1

To support user privacy by informing users about app capabilities and giving them control to restrict capabilities.

Question 2

What are install-time permissions?

Answer 2

Permissions granted at the time of app installation, allowing access to less sensitive data outside the app’s sandbox, e.g., internet access.

Question 3

What are runtime permissions?

Answer 3

Permissions requested while the app is running, controlling access to restricted/private data, e.g., camera access.

Question 4

What are dangerous permissions?

Answer 4

Permissions related to user privacy, such as access to microphone, contacts, and external storage.

Question 5

What is an example of a dangerous permission?

Answer 5

Access to the microphone or contacts.

Examples include access to WIFI, Bluetooth, and NFC operations.

Question 6

How to request special permissions?

Answer 6

By using an intent to direct the user to the corresponding settings page, requiring user action to grant permission.

Question 7

What are best practices for requesting permissions?

Answer 7

Require minimal permissions, use coarse location instead of fine location, and implement alternative behavior if permission is not granted.

Question 8

What happens during app hibernation?

Answer 8

All runtime permissions are reset to DENY, and background jobs, alerts, and push notifications are disabled on Android 12.

Question 9

How to deal with permissions in tests?

Answer 9

Permission dialogs can’t be scripted with Espresso; use androidx.test.GrantPermissionRule and grantRuntimePermission for newer Androids.