Question 76876 in Flutter Question posted in
The official Flutter documentation can be found here.

How to remove REQUEST_INSTALL_PACKAGES from previous verison – Flutter

In previous version of my app I used open_file and unfortunately it used REQUEST_INSTALL_PACKAGES permission.
Now I delete this permission and changed package now Im using open_filex.
Added this code to my manifest file.

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

But can not publish my new version. Google wants me fill the "Sensitive permissions and APIs" – part witch I don’t now what case I should to choose.
How can I solve this problem ?

enter image description here

enter image description here

I also tried to add new release in Internal testing but couldn’t
enter image description here

Tags:

3

Answers


  1. 0

    I had the same problem, i solved changing the plugin for this:

    open_filex

    This package is a fork of open_file to fix the following issues:

    -Remove REQUEST_INSTALL_PACKAGES permission in Android to comply with GooglePlay publish policies

    Login or Signup to reply.
  2. 0

    Remove that code from AndroidManifest. Not required.

    Alternatively check if the new package you added contains the permission.

    open_file_safe worked for me.

    Login or Signup to reply.
  3. 0

    I got this message from Google support.

    Thanks for contacting Google Play Developer Support and we apologize for not addressing your query as quickly as expected. We are currently experiencing a huge inflow of support requests which caused the delay in responding to your email.

    Your app com.copafacil is not compliant with the Permissions policy. Currently, your app still contains the following permissions in version code 140 (2.49):

    android.permission.REQUEST_INSTALL_PACKAGES
    After removing these permissions, you can submit a new release with the APK that does not contain these permissions to replace the current active APKs.

    The Play Console may still be prompting you to submit a Permissions Declaration Form if you still have active APKs in different tracks. If you have active APKs with permissions in multiple tracks, you have to submit Permissions Declaration Form and update all active tracks with APKs with the permissions. When updating the last track, the form will not be needed. You can also not include or create an empty release (a release without any APKs) for testing tracks as part of this.

    To release a new compliant APK, please follow these steps:

    Go to your Play Console.

    Select the app.

    On the left menu, select Release and choose the track (Production or Testing > Open/Closed/Internal) which includes sensitive permissions.

    Click “Create new release” or “Manage Track”.

    a. Suggested order (if tracks have non-compliant APKs): Internal track > Closed > Open > Production.
    If you are required to complete Permissions Declaration Form while releasing the app, please complete the form according to the following instructions:

    a. Choose one core functionality (e.g. Default SMS handler) to make a release with compliant APK. This release may automatically lead to rejection but this will not include the non-compliant APK(s) in the track.
    Select Save > Review at the bottom of the page.

    Click Start Rollout.

    a. Please ensure that the new release is rolled out 100% and completely not including the non-compliant APK.
    Go back to step 1 to make another release in the track where non-compliant APK(s) are in active status until there is no active APK with sensitive permissions across tracks.

    Thanks for working with us through this process and please let us know if you have any further questions.

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search