REQUEST_INSTALL_PACKAGES

Question

Status: Approved with Issues - Further Action Required We found issues with your app. You need to review and take action as described below, so that your app is not impacted in the future.

Issue found: Use of permission is not directly related to the core purpose of the app. We found that your app is not compliant with how REQUEST_INSTALL_PACKAGES permission is allowed to be used. Specifically, the use of the permission is not directly related to the core purpose of the app.

Additionally, follow these steps to bring your app into compliance:

Please remove the use of REQUEST_INSTALL_PACKAGES permission from your app. About the Request Install Packages Permission Starting September 29, 2022, your app must be in compliance with the REQUEST_INSTALL_PACKAGES permission or your app may face additional enforcement actions. The REQUEST_INSTALL_PACKAGES permission allows an application to request the installation of app packages. To use this permission, your app’s core functionality must include:

Sending or receiving app packages, AND Enabling user-initiated installation of app packages. Permitted functionalities include any of the following:

Web browsing or search Communication services that support attachments File sharing, transfer or management Enterprise device management The REQUEST_INSTALL_PACKAGES permission may not be used to perform self updates, modifications, or the bundling of other APKs in the asset file unless for device management purposes. All updates or installing of packages must abide by Google Play’s Device and Network Abuse policy and must be initiated and driven by the user.

For more help addressing this issue, read more in our Help Center.

Answer 1

If your app does not install other apps externally, simply add the following permission to the manifest.

   <uses-permission
    android:name="android.permission.REQUEST_INSTALL_PACKAGES"
    tools:node="remove"/>

Answer 2

I faced the same issue yesterdey. This permission used by open_file package. you can user alternative packages such as better_open_file or open_filex or you can by pass this permission by adding belove code to AndroidManifest.xml:

<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="{you package name}" 
xmlns:tools="http://schemas.android.com/tools">

and in permissions section add this code:

<uses-permission android:name="android.permission.REQUEST_INSTALL_PACKAGES" tools:node="remove"/>

good luck

Answer 3

If you are going to delete this permission from manifest of your app. You need to do these:

REMEMBER It's unnecessary to remove any pub.dev package which uses REQUEST_INSTALL_PACKAGES permission, after adding this to your manifest

android:name="android.permission.REQUEST_INSTALL_PACKAGES" tools:node="remove"/>

because, they remove all such kinda permission from merged manifest file(make sure that manifest opening tag involve xmlns tools like that

<manifest xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:tools="http://schemas.android.com/tools"
package="YOU_APP_PACKAGE_NAME">

ONE OF THE MOST IMPORTANT STEP: You need to update all Open Testing, Internal testing and Closed testing (all tracks even if they are not active). Update your Production channel too. You can check that you updated all required ones in Policy -> App content -> App bundles and APKs using sensitive permissions section. If section is not shown here, then you updated all tracks and channels

AFTER DOING JUST THESE SIMPLE BUT REQUIRED STEPS, YOUR NEW VERSION WILL BE ACCEPTED. GUARANTEED

Answer 4

I faced the same issue a month ago. This is related to the open_file package using REQUEST_INSTALL_PACKAGES permission in the manifest.

Issue: https://github.com/crazecoder/open_file/issues/204

The recommended solution is to use this fork: https://github.com/bertoldofonseca/better_open_file

Answer 5

Remove the permission from your manifest and in-app functionality. Double check that your app is compliant with all other Developer Program Policies. Sign in to Play Console and submit the update to your app. Alternatively, you may also choose to deactivate these versions to avoid additional enforcements that could occur. You may follow the given steps to deactivate the non-compliant app bundles or APKS:

1. Go to your Play Console.
2. Select the app.
3. Go to the track where the non-compliant APK or app bundle is.
4. Near the top right of the page, click Create new release. (You may need to click Manage track first) If the release with the violating APK is in a draft state, discard the release.
5. Under the new release page, you can choose to: A) Upload a new, compliant APK/app bundle and make sure the new release is rolled out 100% to completely deactivate the non-compliant APK. B) Not upload any new APK/app bundle (publish an empty release to just deactivate the non-compliant old version).
6. Regardless of what you choose in step 5, please make sure that the non-compliant version of APK/app bundle is under the Not included section of this new release. For further guidance, please see the "Not included (app bundles and APKs)" section in the Play Console Help article.
7. To save any changes you make to your release, select Save. When you've finished preparing your release, select Review release.
8. If the non-compliant APK is released to multiple tracks, repeat steps 3-8 in each track.

Answer 6

Experienced the same issue a week ago. Check your builds in the Internal Testing or any other environments. Because I received the same email, but there was no information about where exactly this permission exists. Because I removed it from production build. But when I wrote to policy status technical support - they answered that the issues in the build in the Internal testing environment. I updated the build for Internal Testing and app in production was accepted.

I don't know why I have to update build in the Internal testing, because I haven't updated it for months. But rules are rules.