How to Fix Google Play MANAGE_EXTERNAL_STORAGE Rejection
Audit the exact AAB, replace broad storage access when possible, or prove why an eligible core function cannot work with MediaStore or the Storage Access Framework.
Direct answer
Inspect the merged manifest inside the exact signed AAB and determine why MANAGE_EXTERNAL_STORAGE is present. If the feature only accesses media or lets a user choose files or folders, remove All files access and use MediaStore, the Photo Picker, or the Storage Access Framework. Keep the permission only when broad storage access is indispensable to an eligible user-facing core purpose—such as qualifying file management, backup and restore, antivirus, document management, on-device file search, disk or folder encryption, or device migration—and no privacy-friendly alternative can provide the critical function. Make that same core purpose prominent in the store listing, submit an accurate Permissions Declaration Form, and show the reviewed release. Upload a new AAB after any manifest, dependency, code, or access-flow change. Appeal only when the exact reviewed artifact already complies or Google evaluated the wrong version or a demonstrably incorrect fact.
Match the wording in your rejection
“Permission use is not directly related to your app's core purpose”
Broad file access must be essential to the app's main user-facing purpose. A secondary convenience, optional export, attachment picker, or occasional maintenance task is not enough.
“Use MediaStore API or Storage Access Framework”
Google believes the reviewed use can be completed with a narrower, user-controlled path. Test the applicable alternative before arguing that broad access is indispensable.
“Invalid or inaccurate Permissions Declaration Form”
The selected category, explanation, listing, video, data handling, and exact release behavior must describe the same core function. A declaration cannot make an ineligible use acceptable.
Google still detects MANAGE_EXTERNAL_STORAGE after removal
A library, product flavor, dynamic feature, or older active artifact may still contribute the permission. Inspect the signed bundle's merged manifest and every relevant served artifact, not only the source manifest.
The app qualifies as a file manager, backup, security, document, search, encryption, or migration tool
Eligibility is still subject to Google Play review. Prove why the complete core workflow requires broad access and why SAF or MediaStore would materially prevent that workflow.
What this rejection usually means
A MANAGE_EXTERNAL_STORAGE rejection is normally an eligibility or minimum-scope failure, not merely a missing explanation. Google treats files and directory attributes as personal and sensitive data. The app must first pass two gates: broad access is indispensable to a permitted or exceptional core function, and MediaStore or the Storage Access Framework cannot effectively provide that function. Recovery therefore starts with the exact shipped artifact and real runtime data flow. The app category, declaration, store listing, request screen, code behavior, and evidence must all tell the same release-specific story.
Likely rejection signals
- android.permission.MANAGE_EXTERNAL_STORAGE appears in the merged manifest of the signed AAB
- A dependency, flavor, feature module, or older active APK adds the permission even though the main source manifest does not
- The app requests broad access only to import, export, attach, edit, or delete user-selected files
- The app uses All files access only for photos, videos, or audio that MediaStore or the Photo Picker can handle
- Broad access supports a secondary feature rather than the app's main advertised purpose
- The Play listing does not prominently describe the qualifying file, backup, security, document, search, encryption, or migration workflow
- The declaration asserts that SAF or MediaStore is insufficient without demonstrating the exact missing capability
- The permission request, Settings flow, privacy policy, Data safety answers, declaration, or demonstration video does not match the reviewed build
- Files or directory metadata are collected, retained, shared, or sent to an SDK beyond the essential disclosed purpose
- The app does not work safely when the user refuses or later revokes All files access
Recovery plan
- Preserve the full enforcement notice and record the package name, version code, release track, review date, cited policy wording, declaration answers, and reviewer attachments.
- Inspect the merged manifest inside the exact signed AAB and every relevant active artifact. Identify the module, manifest merger rule, SDK, dependency, product flavor, or older APK contributing MANAGE_EXTERNAL_STORAGE.
- Create a storage-access inventory. List every directory, file type, operation, user action, background job, local database, server, SDK recipient, retention period, and behavior when access is denied or revoked.
- Apply the core-purpose gate. Map the feature to one exact permitted category—or document the basis for a narrowly claimed exception—and show why the app is broken or unusable without the critical broad-storage function.
- Run the alternative-API test before retaining the permission. Use MediaStore or the Photo Picker for shared media, SAF for user-selected documents or directories, app-specific storage for private files, and system sharing or intents where the user controls the handoff.
- If a privacy-friendly alternative works, remove the permission at its actual source, update or remove contributing dependencies, rebuild every affected variant, and verify the final signed artifact rather than only AndroidManifest.xml in the app module.
- If broad access remains indispensable, restrict code paths and file operations to the declared core purpose. Do not reuse the access for unrelated analytics, advertising, convenience features, or third-party data collection.
- Make the qualifying core function prominent in the Play listing and reviewer path. The listing should accurately describe what files the app manages and why complete access is necessary, without exaggerating eligibility.
- Reconcile the Permissions Declaration Form, privacy policy, Data safety answers, in-app explanation, Special app access flow, store listing, reviewer instructions, and runtime behavior with the exact release. Resubmit the form whenever the restricted-permission use changes.
- Record a clean-install demonstration of the release build. Show the app's main workflow, the explanation before opening Special app access, grant and refusal behavior, the exact directories and file operations used, and why the narrower alternative cannot complete the qualifying task.
- Test permission denial and revocation, Android 11 and later storage behavior, empty and large storage sets, removable volumes when relevant, and all release variants. Confirm that unrelated SDKs do not receive file or directory data.
- Choose the recovery route: submit a new AAB for any manifest, dependency, code, UI, access-scope, or data-flow change; clarify or appeal only when the reviewed artifact already meets the rule and the notice contains a specific verifiable error.
Evidence to prepare
- Full rejection notice with package, version code, track, date, and exact policy finding
- Merged-manifest output from the exact signed AAB and the source of MANAGE_EXTERNAL_STORAGE
- Inventory of active APKs, bundles, tracks, flavors, feature modules, and dependencies that can contribute the permission
- Storage-access matrix covering directories, file types, operations, recipients, retention, denial, and revocation
- Core-purpose mapping to the exact permitted use or documented exception basis
- MediaStore, Photo Picker, SAF, and app-specific-storage feasibility analysis with tested limitations
- Before-and-after manifest and dependency diff when the permission is removed or narrowed
- Current Permissions Declaration Form, listing, privacy policy, Data safety answers, and reviewer instructions
- Clean-install video showing the main workflow, explanation, Special app access grant or refusal, and actual file operations
Appeal or fix first?
Appeal or request clarification when the exact reviewed AAB does not declare MANAGE_EXTERNAL_STORAGE, Google evaluated an obsolete track or artifact, or the release already implements an eligible core use with accurate listing, declaration, minimum-scope analysis, and evidence. Address one factual mismatch precisely; do not rely on the general argument that many apps need file access.
Fix and upload a new build when the permission is unnecessary, supports an invalid or secondary use, a privacy-friendly API can provide the feature, a dependency or old artifact retains it, the declaration is inaccurate, the request flow is unclear, or storage data is used beyond the essential disclosed purpose. A revised appeal cannot correct a noncompliant binary.
Reviewer response framework
Your response should be factual, short, and limited to the submitted build. Cover these points:
- Identify the package, version code, track, permission, and policy finding.
- State whether MANAGE_EXTERNAL_STORAGE was removed or retained for one exact core function.
- For removal, name the replacement API and attach the signed-artifact manifest diff.
- For retained access, show the permitted-use mapping, why SAF and MediaStore are insufficient, the limited data flow, listing text, declaration, and video timestamps.
- Ask for review of the corrected release or reconsideration of the documented factual error without claiming guaranteed approval.
Frequently asked questions
Can a file picker app use MANAGE_EXTERNAL_STORAGE?
Not merely because users select files. Google lists manual file-selection activity as an invalid use when the Storage Access Framework can provide a user-controlled picker and persistent URI access.
Do photo or video features qualify for All files access?
Ordinary media access does not. Google directs developers to MediaStore and privacy-preserving pickers. A separate current policy also governs READ_MEDIA_IMAGES and READ_MEDIA_VIDEO, so keep the requested scope consistent with the actual feature.
Which app categories may qualify?
Google lists file management, backup and restore, antivirus, document management, on-device file search, disk or folder encryption, and device migration or phone transfer. Each request remains subject to review and must be essential to the app's core purpose.
Can I keep the permission and improve only the declaration?
Only if the shipped use is already eligible and minimum-scope. A better form does not cure an invalid use, an unnecessary permission, or a feature that can operate effectively through SAF or MediaStore.
Why is Play still detecting the permission after I removed it?
Inspect the merged manifest in the exact signed AAB plus all relevant active artifacts. A library, manifest merger, flavor, dynamic feature, or older APK may still contribute MANAGE_EXTERNAL_STORAGE.
Should I appeal or resubmit?
Resubmit a new AAB after any manifest, dependency, code, request-flow, scope, or data-handling change. Appeal only when the exact reviewed release already complies or Google relied on a specific wrong artifact or fact.
Need a rejection-specific plan?
Start with the free diagnosis. The $29 Fix Pack adds the prioritized remediation plan, evidence checklist, reviewer-ready reply, and preflight.
Source: Google Play — Use of All files access (MANAGE_EXTERNAL_STORAGE) permission. Platform policies change. Verify the official rule before submitting. Resubmit AI provides technical and editorial decision support, not an approval guarantee or legal advice.