The Play Console permission declarations that block your release
17 November 2026
Some permissions are legal in Android and still stop your release. Google restricts them to apps whose core function needs them, and asks for a written justification before it will publish. The trigger is the permission appearing in your compiled manifest, which is why a dependency can cause one without you ever typing the permission yourself.
Where this actually happens
Play Console, under App content → Sensitive app permissions. You fill in a form describing which feature needs the permission, and for several of them you also upload a video of that feature working.
The declaration is reviewed per release. Approval is not permanent in the way developers assume: change what the feature does and you can be asked again. An app already live can be removed if the justification stops matching what the app does.
The ones that catch people out
QUERY_ALL_PACKAGES
Lets your app see every installed package. Since Android 11 the system hides most of the
package list unless you ask for specific apps in a <queries> element. Google
limits the broad permission to apps whose core purpose genuinely requires knowing everything
installed — launchers, device search, antivirus, file managers.
I build a launcher, so this is the one I cannot design around. An app drawer that can only
see apps I listed in advance is not an app drawer. For most apps the opposite is true: they
want to know whether three specific apps are present, which <queries> does
with no declaration and no review.
MANAGE_EXTERNAL_STORAGE
All Files Access. The declaration asks you to explain why the Storage Access Framework or MediaStore cannot do the job. That framing matters, because it tells you what the reviewer is looking for. "My app needs to read files" is not an answer to it. "My app is a file manager and must show the user directories it did not create" is.
Exact alarms
USE_EXACT_ALARM is for apps whose core use is an alarm clock, timer or
calendar. Everything else should be using SCHEDULE_EXACT_ALARM, where the user
grants it through a Settings screen and can revoke it. If your reminder feature is a feature
rather than the point of the app, you want the second one.
SMS and Call Log
The whole group is restricted. The usual reason an app wants READ_SMS is to
read a one-time code out of a verification message, and the SMS Retriever API does exactly that
with no permission and no declaration. If that is your case, deleting the permission is faster
than justifying it.
Foreground service types
Since Android 14 every foreground service needs a declared type and the matching permission, and Play asks for a video showing the feature that uses it. This one surprises people because it is not a permission they chose. They added a background task, and the type requirement came with it.
Accessibility services
The most scrutinised of the lot. An AccessibilityService can read screen content and act on it, so Google checks whether you are using it to help users with disabilities or because it was the easiest way to get a capability Android does not otherwise grant. The second case is allowed in narrow circumstances and requires prominent in-app disclosure. Expect a slow review and write the disclosure before you are asked for it.
Writing one that passes
Reviewers are checking one thing: that the permission is load-bearing for a feature a user can see. A declaration fails when it describes a category instead of a feature.
Name the screen. Say what the user does there, what the permission lets your code do at that moment, and what breaks without it. Three sentences of that beat a paragraph about your app's mission. If an alternative API exists and you rejected it, say which one and why it does not work for you — that is often the actual question behind the form.
The video is the part people rush
If a video is required, it has to show the feature running on a device, with the permission prompt or Settings toggle visible, followed by the thing the permission enables. A screen recording that opens your app and shows a settings menu proves nothing. Record the flow a user would take, in one take, and keep it short.
When a library added it, not you
Play reads the merged manifest, so an ad SDK, analytics library or ancient support dependency can hand you a restricted permission silently. The merged manifest after a build is the only version that matters:
app/build/intermediates/merged_manifests/release/AndroidManifest.xml
If you find one you do not want, remove it with a node marker rather than hunting for a different library:
<uses-permission android:name="android.permission.QUERY_ALL_PACKAGES"
tools:node="remove" />
Test afterwards. Some libraries degrade quietly when a permission disappears.
Permissions worth deleting before you justify anything
WRITE_EXTERNAL_STORAGE has done nothing since Android 10.
READ_EXTERNAL_STORAGE has done nothing since Android 13.
READ_PHONE_STATE stopped returning device identifiers in Android 10 and is mostly
still there out of habit, costing a runtime prompt for no capability. Manifests accumulate, and
the fastest way through a permissions review is to arrive with fewer of them.
A caveat
Play policy changes, and enforcement varies between reviewers and regions. Treat everything above as a description of how the process works rather than a ruling on your app. Play Console is the only place that can tell you definitively, and its policy pages are the current text.
Paste your manifest into the Manifest Permission Explainer and it will flag the restricted permissions, the ones that need a runtime prompt, and the ones that stopped doing anything versions ago. It runs in your browser; the manifest is not uploaded.