Google Play · REQUEST_INSTALL_PACKAGES Permission

How to Fix Google Play REQUEST_INSTALL_PACKAGES Rejection

Audit the exact AAB, remove self-update and ineligible APK installation paths, or prove an eligible user-initiated core use with release-specific evidence.

Policy-grounded recovery guideOfficial policy ↗
Have the rejection message open?Get a free diagnosis now. Upgrade to the complete $29 Fix Pack only if it is useful.
Analyze this rejection →

Direct answer

Inspect the merged manifest inside the exact signed AAB and trace every path that downloads, receives, opens, or installs an APK. Remove REQUEST_INSTALL_PACKAGES if installation is not indispensable to the app's advertised core purpose, if it is used for self-updates or feature modification, or if a less intrusive system flow can complete the task. Retain it only for an eligible core use that both sends or receives app packages and enables installation through a direct, active user choice. Make that same purpose prominent in the Play listing, keep the runtime flow user-driven, and submit an accurate Permissions Declaration Form with evidence from the reviewed release. Upload a new AAB after any manifest, dependency, code, listing-dependent behavior, or install-flow change. Appeal only when the exact reviewed artifact already complies or Google relied on a specific wrong artifact or fact.

Official sources checked

Match the wording in your rejection

“Permission use is not directly related to your app's core purpose”

APK exchange and user-initiated installation must be part of the app's main advertised purpose. A secondary updater, optional tool, support workflow, or SDK convenience is not enough.

“Your app does not meet the permitted use requirements”

Google lists categories that may qualify, including web browsing or search, communication attachments, file sharing or management, enterprise device management, backup and restore, device migration, and certain companion sync uses. Category membership is not automatic approval; the install capability must still be indispensable to the core purpose.

The app downloads its own APK or changes its functionality outside Google Play

Google prohibits using this permission for self-updates, modifications, or bundling other APKs in app assets except for the stated device-management exception.

Install starts in the background or without an immediate user decision

Every package installation must be initiated and driven by the user. A prior consent screen does not justify a later automatic install.

Google still detects REQUEST_INSTALL_PACKAGES after removal

A library, product flavor, feature module, manifest merger, or older active artifact may still contribute the permission. Inspect the exact signed bundle and every relevant served artifact.

“Invalid or inaccurate Permissions Declaration Form”

The selected use, explanation, listing, video, manifest, and runtime behavior must describe the same release-specific install workflow. A declaration cannot make an ineligible binary acceptable.

What this rejection usually means

A REQUEST_INSTALL_PACKAGES rejection is usually an eligibility, core-purpose, or user-initiation problem—not merely a missing permission explanation. Google expects the app's main purpose to involve sending or receiving app packages and enabling user-initiated installation. It separately prohibits self-updates and other invalid uses. Recovery therefore starts with the exact shipped artifact and the complete package lifecycle: where an APK originates, how it reaches the device, what the user sees, which action begins installation, what happens after denial, and whether any background component can trigger the flow. The manifest, product behavior, store listing, declaration, privacy disclosures, and video must all describe the same release.

Likely rejection signals

  • android.permission.REQUEST_INSTALL_PACKAGES appears in the merged manifest of the signed AAB
  • The app downloads its own APK, prompts for an off-Play update, or swaps executable functionality
  • An APK is bundled in app assets or downloaded by an SDK without a qualifying device-management purpose
  • Installation supports a secondary feature rather than the app's main advertised purpose
  • A package installer opens after background work, a push message, a timer, or a server command rather than an immediate user choice
  • The user cannot identify the exact package, source, or action before installation begins
  • The Play listing does not prominently describe the package-sharing, management, migration, backup, browser, communication, enterprise, or companion workflow
  • The Permissions Declaration Form and demonstration video refer to a different build, screen, category, or install path
  • A dependency, product flavor, dynamic feature, or old APK contributes the permission after the feature was removed
  • The app fails when the user declines unknown-source authorization or cancels installation

Recovery plan

  1. Preserve the full enforcement notice and record the package name, version code, release track, review date, cited policy wording, declaration answers, and reviewer attachments.
  2. Inspect the merged manifest inside the exact signed AAB and every relevant active artifact. Identify the module, manifest merger rule, SDK, dependency, flavor, feature module, or old APK that contributes REQUEST_INSTALL_PACKAGES.
  3. Trace the complete APK lifecycle. Record the package source, download or receipt mechanism, storage location, checksum or validation, UI shown to the user, the exact gesture that starts installation, PackageInstaller or intent call, denial and cancellation behavior, and any background trigger.
  4. Apply the two-part core-purpose test. Confirm that the app's main advertised purpose includes sending or receiving app packages and enabling their user-initiated installation. Map the workflow to one precise permitted category without assuming that a category label guarantees eligibility.
  5. Remove self-update, executable modification, and bundled-APK paths that do not fit Google's stated device-management exception. Do not use an external APK to update the app distributed through Google Play.
  6. Apply the minimum-scope test. If the app only links to a store page, shares a file without installing it, or can hand work to a user-controlled system surface without this permission, remove REQUEST_INSTALL_PACKAGES and use that narrower path.
  7. If the permission remains eligible, require a direct, active user choice for each package. Show the package identity and source before the system installer, never trigger installation silently or later from a background event, and handle cancellation or refusal safely.
  8. Check PackageManager.canRequestPackageInstalls before launching the installer on supported Android versions. Explain the unknown-source authorization at the moment it is needed and return the user to the exact feature without coercive loops.
  9. Make the qualifying core function prominent and accurate in the Play listing and normal first-run experience. Do not rely on reviewer notes to introduce an install capability that ordinary users would not expect from the listing.
  10. Reconcile the Permissions Declaration Form, store listing, privacy policy, Data safety answers, in-app explanation, reviewer instructions, manifest, and runtime behavior with the exact release. Update the declaration whenever the restricted-permission use changes.
  11. Record a clean-install video of the signed release. Show the main core workflow, package receipt or selection, package identity, the user's install action, unknown-source authorization when needed, system installer, cancellation path, and the resulting user-visible outcome.
  12. Choose the recovery route: submit a new AAB after any manifest, dependency, code, UI, package-source, install-trigger, or data-flow change; clarify or appeal only when the exact reviewed release already complies and the notice contains a specific verifiable error.

Evidence to prepare

  • Full rejection notice with package name, version code, track, date, and exact policy finding
  • Merged-manifest output from the exact signed AAB and the source of REQUEST_INSTALL_PACKAGES
  • Inventory of active bundles, APKs, tracks, flavors, feature modules, SDKs, and dependencies that can contribute the permission
  • APK lifecycle diagram covering source, transfer, storage, validation, user action, installer call, result, denial, and cancellation
  • Core-purpose mapping to the exact permitted use and an explanation of why package installation is indispensable
  • Before-and-after manifest, dependency, and code diff when self-update or another ineligible path is removed
  • Current Permissions Declaration Form, listing, privacy policy, Data safety answers, and reviewer instructions
  • Clean-install video showing the main advertised workflow and a direct user choice for each package installation
  • Logs or test notes proving that no timer, push, server command, SDK, or background task can start an unintended installation

Appeal or fix first?

APPEAL / CLARIFY

Appeal or request clarification when the exact reviewed AAB does not declare REQUEST_INSTALL_PACKAGES, Google evaluated an obsolete artifact, or the release already implements an eligible core use with an accurate listing, declaration, user-driven flow, and release-specific evidence. Address one factual mismatch precisely; do not argue only that another app has similar behavior.

FIX BEFORE RESUBMITTING

Fix and upload a new AAB when the permission is unnecessary, supports self-update or another invalid use, the install capability is secondary, a narrower path works, an SDK or old artifact retains it, the flow is not directly user-initiated, or the declaration and listing do not match the binary. An appeal cannot repair a noncompliant artifact.

Choose the next action

What you can verifyRecommended path
The app uses the permission to update itself or download a replacement APKRemove the permission and self-update path. Distribute updates through Google Play and use the supported Play update experience where appropriate.
The app only opens a Play Store, browser, or system listing and does not install APK filesUse the normal user-driven intent or link and remove REQUEST_INSTALL_PACKAGES.
Receiving APK attachments or managing app packages is an indispensable advertised core functionRetain only the minimum install path, require a direct user action for each package, document the core use prominently, and submit an accurate declaration and video. Eligibility remains subject to review.
The permission comes from an SDK, abandoned feature, flavor, or old releaseRemove it at the contributing source, rebuild every affected variant, and reconcile active production, testing, and staged artifacts before resubmitting.
The exact reviewed release already has an eligible core use and fully user-driven flowClarify or appeal with the signed-artifact manifest, permitted-use mapping, listing, declaration, and timestamped video tied to the factual error.

Reviewer response framework

Your response should be factual, short, and limited to the submitted build. Cover these points:

  1. Identify the package name, version code, track, permission, and exact policy finding.
  2. State whether REQUEST_INSTALL_PACKAGES was removed or retained for one precisely defined core function.
  3. For removal, name the deleted self-update or install path and attach the signed-artifact manifest diff.
  4. For retained access, map the feature to the permitted use, show the direct user gesture, provide listing and declaration text, and cite video timestamps from the exact release.
  5. Ask for review of the corrected build or reconsideration of the documented factual error without claiming that approval is guaranteed.

Frequently asked questions

Can my app use REQUEST_INSTALL_PACKAGES to update itself?

No. Google's policy says the permission may not be used for self-updates or modifications. Remove the off-Play updater and distribute updates through Google Play using the supported update experience.

Does a file manager or browser automatically qualify?

No. Google lists file management and web browsing or search among permitted categories, but the install capability must still be indispensable to the app's main advertised purpose, directly user-initiated, accurately declared, and subject to review.

Can a messaging app install APK attachments?

A communication service supporting attachments is a listed permitted category, but eligibility is not automatic. The app must receive packages as part of its core purpose, require an active user choice for each install, and align the listing, declaration, and release behavior.

Do I need REQUEST_INSTALL_PACKAGES just to open a Play Store page?

No. Opening a store or browser page through a normal user-driven link does not require the app to request installation of an APK. Remove the permission if that is the only workflow.

Why does Play still detect the permission after I removed it?

Inspect the merged manifest in the exact signed AAB and every relevant active artifact. A dependency, manifest merger, flavor, feature module, or older APK may still contribute REQUEST_INSTALL_PACKAGES.

Should I appeal or resubmit?

Resubmit a new AAB after any manifest, dependency, code, UI, package-source, install-trigger, or data-flow 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.

Analyze my rejection

Source: Google Play — Use of the REQUEST_INSTALL_PACKAGES 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.