Two denial rule
After two denials, Android stops showing the permission dialog.
In one line
Can ask for a permission only twice on Android, and once on iPhone
After two denials, Android stops showing the permission dialog.
Limits repeated prompts. iOS shows a permission prompt only once; later changes must be made in Settings.
What it can and can't do
What the user does: You tap Don't allow on a permission dialog
It can
- Ask again after one denial on Android
- Send you to Settings with a link to change it
- Explain why it needs the permission before asking again
It cannot
- Show the Android dialog after two denials
- Show the iPhone prompt again after you answer
- Change the permission for you; you do that in Settings
How it differs between platforms: Android shows the dialog at most twice; iPhone shows it once.
On Android and iPhone
| Android | iPhone | |
|---|---|---|
| Status | Supported | Supported |
| First version | Android 11 (API 30) | iOS 2.0 |
| Permission or entitlement | n/a (system behavior) | n/a |
| Protection level | none | prompt |
| How access is granted | prompt | prompt |
| What the user sees | Dialog shows at most twice per permission | System prompt once per permission |
| How long it lasts | Remains denied until user changes it | Until changed in Settings |
| How to take it back | Settings > Apps > Permissions | Settings > app > permission |
| Store policy | Play: apps must handle denial gracefully | App Review 5.1.1 |
| API | shouldShowRequestPermissionRationale, flags USER_SET and USER_FIXED | UIApplication.openSettingsURLString |
| Notes | USER_SET after one denial; USER_FIXED after two. | App can send the user to Settings via a deep link. |
Data you get
What comes back: Denial count
Shape: none
How often: per permission
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
count | integer | denials | 0 to 2 | exact |
Technical limits
- Apps cannot reset the prompt
The story
What it is
After you say no twice, Android stops showing the permission prompt for that app.
For you
If you deny a permission twice, the app cannot ask again. You have to change it yourself in Settings. This stops an app from nagging you into saying yes.
For makers
Apps must explain why they need a permission before asking, since they only get two tries. Good apps show a simple screen first. Bad ones may send you to Settings with a plea.
Where you see it
| Type | Example | Apps |
|---|---|---|
| games | A game asks for location, you say no twice, and it works without it or shows a settings link. | None named |
| social | A social app asks for contacts and has to live without it after two denials. | None named |
| maps | A maps app shows a screen explaining why location helps before the prompt. | Google Maps |
| shopping | A store app asks for the camera and sends you to Settings if you refuse twice. | None named |
| fitness | A fitness app asks for body sensors and explains its use. | None named |
| security | A researcher tests how an app behaves when permissions are blocked. | None named |
| developer | A developer builds a pre prompt screen to win consent. | None named |
Risks
- App may stop working
- Hard to change your mind
- Nag tricks
Android and iPhone in short
- Android: Android marks a permission as user set after one denial, and fixed after two.
- iPhone: iPhone shows a permission prompt only once. After that, changes must be made in Settings, and an app can link to Settings.
Good uses and abuse
Legitimate uses
- User control
Known abuse
- Dark pattern re-prompts
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 2 of 5 | How revealing the data is |
| Utility | 2 of 5 | How useful it is to honest apps |
| Friction | 2 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
History
- 2008-07, iPhone iOS 2: Single-shot permission prompts
- 2020-09, Android 11 (API 30): Dialog suppressed after two denials
Related capabilities
Related
- One-time permissions. Can use location, camera or mic only until you leave, if you pick one time access
Same idea on the web
- Permissions API. Can check whether you allowed or blocked a feature, without asking you
Sources
How well checked: Based on official documentation.