Remove `REQUEST_INSTALL_PACKAGES` permission #204

Zazo032 · 2022-07-20T14:05:05Z

Today I received a new message regarding a Flutter app published in Play Store, with the following information:

You'll need to complete a declaration soon for apps using REQUEST_INSTALL_PACKAGES

We found that your manifest file contains the REQUEST_INSTALL_PACKAGES permission.
Starting September 29, 2022, apps that use this permission will not be able to submit updates for review until they have completed a new sensitive permission declaration.
This declaration will be available in Play Console on August 31, 2022. You'll need to declare which permitted functionality your app provides, tell us about a core feature in your app that uses the permission, and provide a video showing its use.
You must remove this sensitive permission from your manifest if your app does not use the permitted functionalities, or if you no longer use this permission. To learn more, watch this PolicyBytes video.
Learn more

We don't directly need the permission to install other packages, so this should be removed from the plugin's manifest and instead be added to the apps that require it, otherwise it'll require apps to fill that Play Store form even if they don't need to

GoldenSoju · 2022-07-22T02:37:44Z

There is a fork that got this permission removed.

Maybe that helps you for the moment.

(Kudos to this SO question.)

GoldenSoju · 2022-07-22T08:08:58Z

I created an updated fork with

updated ffi dependency (2.0.1)
removed REQUEST_INSTALL_PACKAGES permission
embedding 2 (Android)
and other smaller updates

You can use it via:

  open_filex:
    git:
      url: https://github.com/GoldenSoju/open_file.git

Zazo032 · 2022-07-22T08:18:16Z

Is that one available through pub.dev?

GoldenSoju · 2022-07-22T08:22:43Z

@Zazo032
no, for the moment only via manual dependency specification:

  open_filex:
    git:
      url: https://github.com/GoldenSoju/open_file.git

Zazo032 · 2022-07-22T08:23:50Z

I'll try it, thanks! You could also try to create a PR with the fixes

GoldenSoju · 2022-07-22T08:35:31Z

I'll try it, thanks! You could also try to create a PR with the fixes

Yeah...problem is that the other original package has no acitivity. Most fixes I did already have PRs, but they don't get merged etc...

Kishan-Somaiya · 2022-07-25T05:13:44Z

Is that one available through pub.dev?

A fork of open_file is available in pub.dev as open_filex which removes the Request Install APK Permission.

LuisMiguelSS · 2022-09-06T09:48:13Z

Could we get this fixed here? It's an important issue and the latest fix was in no more than 15 days

MilesAdamson · 2022-09-09T20:44:03Z

My app currently has a Google Play policy issue because I submitted a build with this permission but cannot properly prove I need it. I really need to open files, please do not add this to the manifest unconditionally

related issue: crazecoder/open_file#204

hedi-ghodhbane · 2022-09-16T21:43:38Z

https://pub.dev/packages/open_file_safe you can use this instead. It's the same package but it removed the .apk from the files supported so this permission is no longer needed

gerritwitkamp · 2022-09-19T08:39:52Z

are there any differences between open_file_safe and open_filex?

hedi-ghodhbane · 2022-09-19T09:00:41Z

@gerritwitkamp I think both are the same, they just removed support for .apk so this request_install_packages is not needed anymore.

LuisMiguelSS · 2022-09-19T09:27:35Z

are there any differences between open_file_safe and open_filex?

https://github.com/javaherisaber/open_filex seems more actively maintained

iamtechmanish · 2022-10-02T09:24:50Z

In my case this was related to the open_file in Flutter. This package is using REQUEST_INSTALL_PACKAGES permission in the manifest.

I fixed by using (open_file_safe) :https://pub.dev/packages/open_file_safe

or you can also use open_filex: https://pub.dev/packages/open_filex

both packages are same as open_file, but .apk file type is not supported. Thus, android.permission.REQUEST_INSTALL_PACKAGES permission not required.

Note : If you are facing this issue with native android project You may be querying all packages with the package manager, this is no longer allowed since Android 8.0. To resolve open the android project of your app in android studio and check the Merged Manifests portion of the AndroidManifest.xml to see if you find that permission being used in your app if it is being used remove the permission.

See more info here. https://support.google.com/googleplay/android-developer/answer/12085295?hl=en

undamatlamanikanta · 2022-10-13T04:29:13Z

i faced same issue and changed open_file to open_file_safe
then build the application got error Permission denied: android.Manifest.permission.MANAGE_EXTERNAL_STORAGE

My AndroidManifest.xml

<uses-permission android:name="android.permission.INTERNET"/>
<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
<uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" />
<uses-permission android:name="android.hardware.location.gps" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>
<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE"/>
<uses-permission android:name="android.permission.VIBRATE" />
<uses-permission android:name="android.permission.MANAGE_EXTERNAL_STORAGE" />



<queries>
    <!-- If your app opens https URLs -->
    <intent>
        <action android:name="android.intent.action.VIEW" />
        <data android:scheme="https" />
    </intent>
    <!-- If your app makes calls -->
    <intent>
        <action android:name="android.intent.action.DIAL" />
        <data android:scheme="tel" />
    </intent>
    <!-- If your app emails -->
    <intent>
        <action android:name="android.intent.action.SEND" />
        <data android:mimeType="*/*" />
    </intent>
</queries>

<application
    android:name="${applicationName}"
    android:label="XXXXXXXXX"
    android:icon="@mipmap/ic_launcher"
    android:exported="true">
    <activity
        android:name=".MainActivity"
        android:launchMode="singleTop"
        android:theme="@style/LaunchTheme"
        android:configChanges="orientation|keyboardHidden|keyboard|screenSize|smallestScreenSize|locale|layoutDirection|fontScale|screenLayout|density|uiMode"
        android:hardwareAccelerated="true"
        android:usesCleartextTraffic="true"
        android:windowSoftInputMode="adjustResize"
        android:exported="true">
        <!-- Specifies an Android theme to apply to this Activity as soon as
             the Android process has started. This theme is visible to the user
             while the Flutter UI initializes. After that, this theme continues
             to determine the Window background behind the Flutter UI. -->
        <meta-data
          android:name="io.flutter.embedding.android.NormalTheme"
          android:resource="@style/NormalTheme"
          />
        <!-- Displays an Android View that continues showing the launch screen
             Drawable until Flutter paints its first frame, then this splash
             screen fades out. A splash screen is useful to avoid any visual
             gap between the end of Android's launch screen and the painting of
             Flutter's first frame. -->
        <meta-data
          android:name="io.flutter.embedding.android.SplashScreenDrawable"
          android:resource="@drawable/launch_background"
          />
        <intent-filter>
            <action android:name="android.intent.action.MAIN"/>
            <category android:name="android.intent.category.LAUNCHER"/>
        </intent-filter>
        <!-- Deep links -->
        <!-- Scheme+host filter -->
        <intent-filter>
            <action android:name="android.intent.action.VIEW" />
            <category android:name="android.intent.category.DEFAULT" />
            <category android:name="android.intent.category.BROWSABLE" />
            <data
                android:scheme="https"
                android:host="xxxxxxxxxxx.link" />
        </intent-filter>
         <!-- App Links -->
        <intent-filter android:autoVerify="true">
            <action android:name="android.intent.action.VIEW" />
            <category android:name="android.intent.category.DEFAULT" />
            <category android:name="android.intent.category.BROWSABLE" />
            <!-- Accepts URIs that begin with https://YOUR_HOST -->
            <data
            android:scheme="https"
            android:host="XXXXXXXXXX.link" />
        </intent-filter>
        <!-- Scheme-only filter -->
        <intent-filter>
            <action android:name="android.intent.action.VIEW" />
            <category android:name="android.intent.category.DEFAULT" />
            <category android:name="android.intent.category.BROWSABLE" />
            <data android:scheme="https" />
        </intent-filter>
            <!-- *** FIREBASE :: FCM Add below to ensure we get the payload when tapping on a notification *** -->
        <intent-filter>
            <action android:name="FLUTTER_NOTIFICATION_CLICK" />
            <category android:name="android.intent.category.DEFAULT" />
        </intent-filter>
    </activity>
    <meta-data android:name="com.google.android.geo.API_KEY"
           android:value="XXXXXXXXXXXXXXXX"/>
    <activity
        android:name="com.yalantis.ucrop.UCropActivity"
        android:screenOrientation="portrait"
        android:theme="@style/Theme.AppCompat.Light.NoActionBar"
        android:exported="true"/>
    <!-- *** LocalNotifications ***-->
    <receiver android:name="com.dexterous.flutterlocalnotifications.ScheduledNotificationBootReceiver"
    android:exported="true">
        <intent-filter>
            <action android:name="android.intent.action.BOOT_COMPLETED"/>
            <action android:name="android.intent.action.MY_PACKAGE_REPLACED"/>
        </intent-filter>
    </receiver>
    <receiver android:name="com.dexterous.flutterlocalnotifications.ScheduledNotificationReceiver"
    android:exported="true" />
    <!-- upto this notifcation -->
    <provider
            android:name="androidx.core.content.FileProvider"
            android:authorities="${applicationId}.fileProvider"
            android:exported="false"
            android:grantUriPermissions="true"
            tools:replace="android:authorities">
        <meta-data
                android:name="android.support.FILE_PROVIDER_PATHS"
                android:resource="@xml/filepaths"
                tools:replace="android:resource" />
    </provider>
    <!-- Don't delete the meta-data below.
         This is used by the Flutter tool to generate GeneratedPluginRegistrant.java -->
    <meta-data
        android:name="flutterEmbedding"
        android:value="2" />
</application>

My Pubspec.yaml

name: *******
description: A new Flutter project.

The following line prevents the package from being accidentally published to

pub.dev using `pub publish`. This is preferred for private packages.

publish_to: 'none' # Remove this line if you wish to publish to pub.dev

The following defines the version and build number for your application.

A version number is three numbers separated by dots, like 1.2.43

followed by an optional build number separated by a +.

Both the version and the builder number may be overridden in flutter

build by specifying --build-name and --build-number, respectively.

In Android, build-name is used as versionName while build-number used as versionCode.

In iOS, build-name is used as CFBundleShortVersionString while build-number used as CFBundleVersion.

https://developer.apple.com/library/archive/documentation/General/Reference/InfoPlistKeyReference/Articles/CoreFoundationKeys.html

version: 1.0.27+27

environment:
sdk: ">=2.12.0 <3.0.0"

dependencies:
flutter:
sdk: flutter

The following adds the Cupertino Icons font to your application.

Use with the CupertinoIcons class for iOS style icons.

cupertino_icons: "^1.0.3"

#firebase

firebase_dynamic_links: ^0.5.0+11

firebase_auth: "^2.0.0"

google_sign_in: "^5.0.4"

flutter_facebook_login: ^3.0.0

firebase_messaging: "^10.0.3"
# "^6.0.16"
flutter_local_notifications: "^6.0.0"
firebase_database: "^7.1.1"
firebase_storage: "^9.0.0"
cloud_firestore: "^2.3.0"
firebase_analytics: "^8.1.2"

 # state management - dependencies

rxdart: "^0.27.1"
get: "^4.1.4"
get_it: "^7.1.3"

fluttertoast: "^8.0.7"

hive: "^2.0.4"
path_provider: "^2.0.2"

device_preview: ^1.1.0

lottie: "^1.0.1"
flutter_treeview: "^1.0.6+1"

sms_autofill: "^2.2.0 "

contacts_service: ^0.6.1

permission_handler: "^10.0.0"
jwt_decode: "^0.3.1"

image pickers

flutter_exif_rotation: "^0.4.1"
image_picker: "^0.8.1+3"
dio: "^4.0.0"
mime: "^1.0.0"
string_splitter: "^1.0.0+1"
percent_indicator: "^3.0.1"
flutter_datetime_picker:
git:
url: https://github.com/Realank/flutter_datetime_picker.git
ref: master
flutter_typeahead: "^3.1.3"
outline_gradient_button: "^2.0.0+1"
file_picker: "^3.0.3"
uuid: "^3.0.4"
photo_view: "^0.12.0"
country_code_picker: "^2.0.2"
group_button: "^2.3.0"

flutter_localizations:

collection: ^1.15.0-nullsafety.4

currency_picker: "^2.0.4"
flutter_map: "^0.13.1"

latlong: ^0.6.1

latlong2: "^0.8.0"
geolocator:
url_launcher: "^6.0.9"
geocoding: "^2.0.0"
dotted_border: "^2.0.0"
shimmer: "^2.0.0"
pdf: "^3.4.2"
printing: "^5.4.3"
flutter_echarts: "^2.2.0"
intl_phone_number_input: "^0.7.0+2"

flutter_libphonenumber: ^1.1.0

image_cropper: "^1.4.1"
scrollable_positioned_list: "^0.2.0-nullsafety.0"
swipe_to: "^0.1.0-nullsafety.1"
share: "^2.0.4"
upgrader: "^4.4.0"
device_info: "^2.0.2"
horizontal_data_table: "^3.6.1+1"
getwidget: "^2.0.4"
package_info_plus: "^1.4.0"
flutter_app_badger: "^1.3.0"
flutter_svg: "^1.0.3"
flutter_statusbarcolor_ns: "^0.4.0"
razorpay_flutter: ^1.2.7

flutter_app_restart: ^1.0.0

flutter_phoenix: "^1.0.0"

google_maps_flutter: "^2.1.12"
showcaseview: "^1.1.8"
firebase_core: "^1.12.0"
flutter_native_splash: "^1.3.2"
open_file_safe: ^3.2.3

dev_dependencies:
flutter_test:
sdk: flutter
flutter_launcher_icons: ^0.9.0

flutter_icons:
image_path: "assets/icons/app_icon.png"
android: "ic_launcher"
ios: true
remove_alpha_ios: true

For information on the generic Dart part of this file, see the

following page: https://dart.dev/tools/pub/pubspec

The following section is specific to Flutter.

flutter:

The following line ensures that the Material Icons font is

included with your application, so that you can use the icons in

the material Icons class.

uses-material-design: true

To add assets to your application, add an assets section, like this:

assets:
- assets/images/
- assets/
- assets/icons/
- assets/tab_icons/
- assets/role_icons/
- assets/file_type_icons/
- assets/profile_icons/
- assets/lottie/

An image asset can refer to one or more resolution-specific "variants", see

https://flutter.dev/assets-and-images/#resolution-aware.

For details regarding adding assets from package dependencies, see

https://flutter.dev/assets-and-images/#from-packages

To add custom fonts to your application, add a fonts section here,

in this "flutter" section. Each entry in this list should have a

"family" key with the font family name, and a "fonts" key with a

list giving the asset and other descriptors for the font. For

example:

fonts:
- family: Gilroy
fonts:
- asset: assets/fonts/Gilroy-ExtraBold.otf
- asset: assets/fonts/Gilroy-Light.otf
- asset: assets/fonts/Gilroy-SemiBold.ttf
weight: 600
- asset: assets/fonts/Gilroy-Black.ttf
weight: 900

flutter_native_splash:
image: assets/icons/app_icon.png
color: FFFFFF

fonts:

- family: Schyler

fonts:

- asset: fonts/Schyler-Regular.ttf

- asset: fonts/Schyler-Italic.ttf

style: italic

- family: Trajan Pro

fonts:

- asset: fonts/TrajanPro.ttf

- asset: fonts/TrajanPro_Bold.ttf

weight: 700

For details regarding fonts from package dependencies,

see https://flutter.dev/custom-fonts/#from-packages

Please solve my problem, Thanks in advance

Gbarago · 2022-10-18T04:43:54Z

I am having the same issue and i have used open_file_sefee and oopen_filex i even took out the feature that depended on it but still got rejected

here are my dependencies

permission_handler: 7.1.0

permission_handler: ^8.1.1

slide_button: ^0.2.8
async: ^2.4.2
contacts_service: ^0.6.0
md2_tab_indicator: ^1.0.2
icofont_flutter: ^1.3.0
flutter_feather_icons: ^1.0.3
image_gallery_saver: ^1.7.0
showcaseview: ^1.1.1
flutter_share: ^2.0.0
flutter_svg: ^0.21.0
stack: ^0.2.1
keyboard_actions: ^3.4.6
keyboard_avoider: ^0.1.2
file_picker: ^4.4.0
overlay_support: ^1.2.1
badges: ^2.0.1
grouped_list: ^4.1.0

in_app_review: 2.0.0

flutter_local_notifications: 5.0.0
image_picker: ^0.8.4+1
flutter_html: ^0.11.1
auto_size_text: ^2.0.2
flutter_switch: ^0.3.1
ext_storage:
flutter_speed_dial: ^3.0.5
flutter_dialpad_plus: ^0.2.1
fraction: ^3.0.1
path_provider: ^2.0.1
step_progress_indicator: ^1.0.0
percent_indicator: ^2.1.5
connectivity: ^3.0.6
device_info_plus: ^3.2.2
cupertino_icons: ^0.1.3
device_info_plus_linux: ^2.1.1
device_info_plus_windows: ^2.1.1
flutter_screenutil: ^4.0.3+1
dio: ^4.0.0
tuple: 2.0.0
dartz: ^0.9.2
dotted_border: ^2.0.0
dotted_line: ^3.0.0
flushbar: ^1.10.4
firebase_core: 1.3.0
firebase_messaging: 10.0.2
pretty_dio_logger: ^1.1.1
flip_card: ^0.6.0
dropdown_search: ^0.5.0
flutter_apns: ^1.5.1
flutter_apns_only: 1.5.0
hive: ^2.0.4
hive_flutter: ^1.1.0
flutter_collapse: ^0.1.1
flutter_secure_storage: ^3.2.1+1
easy_contact_picker: ^0.0.2

flutter_money_formatter: ^0.8.3

flutter_spinkit: ^3.1.0
rate_my_app: 1.1.1
pedantic: ^1.11.1
flutter_platform_widgets: ^0.60.2
sized_context: ^0.2.1+1
flutter_swiper: ^1.1.6
http_parser: ^4.0.0
material_design_icons_flutter: 4.0.5345
modal_bottom_sheet: 1.0.0+1
modal_progress_hud: 0.1.3
share: 0.6.5
external_path: 1.0.1
signalr_netcore: 0.1.7+2-nullsafety.2
shared_preferences: 2.0.5
flutter_shimmer: 1.3.0
json_annotation: any
provider: 6.0.0
flutter_bloc: ^7.2.0
equatable: ^1.2.3
camera: ^0.5.8+17
cached_network_image: ^2.5.0
pin_entry_text_field: ^0.1.4
pull_to_refresh: ^2.0.0
pin_code_fields: ^7.0.0
introduction_screen: ^2.1.0
expandable: ^5.0.1
collection: ^1.15.0
location: ^4.4.0
qr_flutter: ^4.0.0
qr_code_scanner: ^0.4.0
timeline_tile: ^2.0.0
flutter_icons: ^1.1.0
assorted_layout_widgets: 5.5.0
popup_menu: ^1.0.5

another_flushbar: ^1.10.5

shimmer: ^2.0.0
uuid: ^3.0.2
rxdart: ^0.25.0
intl: ^0.17.0
gap: ^1.2.0
simple_tooltip: ^0.1.16
screenshot: ^1.2.3
flutter_masked_text2: ^0.9.1
stream_transform: ^0.0.19
url_launcher: ^6.0.0
syncfusion_flutter_datepicker: ^19.2.59
infinite_scroll_pagination: 2.3.0
syncfusion_flutter_pdfviewer: 19.4.55-beta
photo_view: ^0.13.0
open_file_safe: ^3.2.3
flutter_web_browser: ^0.15.0
lottie: 1.2.1
font_awesome_flutter: ^9.1.0
link_preview_flutter: ^0.0.5
share_extend: ^2.0.0
app_tracking_transparency: ^2.0.2+1
sentry_flutter: 4.0.6
appsflyer_sdk: ^6.4.0+2
flutter_linkify: ^5.0.2
mixpanel_flutter: ^1.4.5
local_auth: ^1.1.7
package_info_plus: ^1.4.2
mati_plugin_flutter: any
fluttertoast: ^8.0.7
http: ^0.13.3
webview_flutter: ^0.3.3

Galeen-Bidpath · 2022-10-18T07:01:57Z

If you add this to your AndroidManifest.xml should exclude the permission from the merged manifest.
However if you are using this functionality will probably crash the app(I haven't seen the code). In modern android apps the lib should only receive that the permission is denied.

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

Gbarago · 2022-10-18T08:25:01Z

Thanks for this.
I have also done this, but for some reason google still flags the app or having this permission.

Gbarago · 2022-10-18T08:26:15Z

or is i possible that i am doing it long

Galeen-Bidpath · 2022-10-18T08:45:32Z

I have submitted an update on my build this morning and was approved.
Make sure you are adding it in the right manifest.
app/src/main/AndroidManifest.xml

After you made your build can check if the permission is still decleared in the merged manifest in
build/app/intermediates/merged_manifest/

Gbarago · 2022-10-18T09:38:14Z

alright will do this and se i it works
thanks again

Gbarago · 2022-10-18T13:01:01Z

Just got a rejection mail from google play.. problem still exists

Galeen-Bidpath · 2022-10-18T13:03:53Z

Maybe you are mmissing something.
Make screenshots of your manifest, then the location of the manifest.
Also show the merged manifest after you have built the app, located at build/app/intermediates/merged_manifest/

Gbarago · 2022-10-18T13:05:05Z

okay

Gbarago · 2022-10-18T15:40:21Z

Galeen-Bidpath · 2022-10-18T16:10:41Z

second image is not the right one, should be from merged_manifest folder(scroll down) not from bundle_manifest

In general it looks OK.

Gbarago · 2022-10-18T16:29:44Z

ok
i will upload that too right away
thanks @Galeen-Bidpath

blue492 · 2022-10-28T06:36:31Z

I submitted a version 88 (3.5.4) which had REQUEST_INSTALL_PACKAGES and this version has been rejected.

I added the following row:
<uses-permission android:name="android.permission.REQUEST_INSTALL_PACKAGES" tools:node="remove" />

And I submitted a new version 89 (3.5.4) and in permissions section for this version in Google play I can see that "REQUEST_INSTALL_PACKAGES" is removed. But this version has been also rejected.

What I should do now?

Galeen-Bidpath · 2022-10-28T09:21:24Z

I submitted a version 88 (3.5.4) which had REQUEST_INSTALL_PACKAGES and this version has been rejected.

I added the following row: <uses-permission android:name="android.permission.REQUEST_INSTALL_PACKAGES" tools:node="remove" />

And I submitted a new version 89 (3.5.4) and in permissions section for this version in Google play I can see that "REQUEST_INSTALL_PACKAGES" is removed. But this version has been also rejected.

What I should do now?

As a start is to read the comments in this thread.
3 comment on top of yours someone is giving the solution #204 (comment)

bharathking · 2022-10-30T07:53:34Z

I submitted a version 88 (3.5.4) which had REQUEST_INSTALL_PACKAGES and this version has been rejected.

I added the following row: <uses-permission android:name="android.permission.REQUEST_INSTALL_PACKAGES" tools:node="remove" />

And I submitted a new version 89 (3.5.4) and in permissions section for this version in Google play I can see that "REQUEST_INSTALL_PACKAGES" is removed. But this version has been also rejected.

What I should do now?

https://youtu.be/TaCxgCwQNpc

bharathking · 2022-10-30T07:56:05Z

I submitted a version 88 (3.5.4) which had REQUEST_INSTALL_PACKAGES and this version has been rejected.
I added the following row: <uses-permission android:name="android.permission.REQUEST_INSTALL_PACKAGES" tools:node="remove" />
And I submitted a new version 89 (3.5.4) and in permissions section for this version in Google play I can see that "REQUEST_INSTALL_PACKAGES" is removed. But this version has been also rejected.
What I should do now?

As a start is to read the comments in this thread. 3 comment on top of yours someone is giving the solution #204 (comment)

https://youtu.be/TaCxgCwQNpc

jamesncl · 2022-10-30T11:09:51Z

For anyone else who thinks they have removed the REQUEST_INSTALL_PACKAGES permission but are still getting rejected, this might help. I had the same problem. Try this - click on the Go to declaration button, then View app bundles and APKs. For me, it showed a really old build from years ago in a track that I no longer use and is deactivated (closed alpha testing). I think (hope) this is why I'm being rejected, even though I haven't touched this track since 2020, when you publish to any track they are scanning all the latest versions in all your tracks for this permission, even if the track is not used anymore.

I've just submitted an update to my closed alpha track and waiting for the result...

bharathking · 2022-10-30T14:02:27Z

For anyone else who thinks they have removed the REQUEST_INSTALL_PACKAGES permission but are still getting rejected, this might help. I had the same problem. Try this - click on the Go to declaration button, then View app bundles and APKs. For me, it showed a really old build from years ago in a track that I no longer use and is deactivated (closed alpha testing). I think (hope) this is why I'm being rejected, even though I haven't touched this track since 2020, when you publish to any track they are scanning all the latest versions in all your tracks for this permission, even if the track is not used anymore.
I've just submitted an update to my closed alpha track and waiting for the result...

If you didn’t use these “file_open” or “permission_handler” packages and also get the issue of flutter Remove REQUEST_INSTALL_PACKAGES Permission then you have to find out which package is the culprit for this issue.

First generate the app released version from Build > Flutter > Build App Bundle. Now go to your project root folder and open > build/app/outputs/logs/manifest-merger-release-report.txt Now check which package generate that permission and use different package for that.

You can learn more from here: Fix Flutter Remove REQUEST_INSTALL_PACKAGES Permission From Play Console

Set release rollout 100% it will deactivate all the builds except release build

bharathking · 2022-10-30T14:04:04Z

For anyone else who thinks they have removed the REQUEST_INSTALL_PACKAGES permission but are still getting rejected, this might help. I had the same problem. Try this - click on the Go to declaration button, then View app bundles and APKs. For me, it showed a really old build from years ago in a track that I no longer use and is deactivated (closed alpha testing). I think (hope) this is why I'm being rejected, even though I haven't touched this track since 2020, when you publish to any track they are scanning all the latest versions in all your tracks for this permission, even if the track is not used anymore.
I've just submitted an update to my closed alpha track and waiting for the result...

If you didn’t use these “file_open” or “permission_handler” packages and also get the issue of flutter Remove REQUEST_INSTALL_PACKAGES Permission then you have to find out which package is the culprit for this issue.
First generate the app released version from Build > Flutter > Build App Bundle. Now go to your project root folder and open > build/app/outputs/logs/manifest-merger-release-report.txt Now check which package generate that permission and use different package for that.
You can learn more from here: Fix Flutter Remove REQUEST_INSTALL_PACKAGES Permission From Play Console

Set release rollout 100% it will deactivate all the builds except release build

If its closed alpha testing - manage track - pause

bharathking · 2022-10-30T15:00:26Z

https://youtu.be/TaCxgCwQNpc - please verify all the steps done. I got approved two days before...

lakshydeep-14 · 2022-11-01T04:52:43Z

Application rejected though I am using open_file in my flutter application.
What to do now?
What to add in android manifest.xml file and what not so that my application will get accepted?
Here is the image attached.

lakshydeep-14 · 2022-11-01T05:00:06Z

For anyone else who thinks they have removed the REQUEST_INSTALL_PACKAGES permission but are still getting rejected, this might help. I had the same problem. Try this - click on the Go to declaration button, then View app bundles and APKs. For me, it showed a really old build from years ago in a track that I no longer use and is deactivated (closed alpha testing). I think (hope) this is why I'm being rejected, even though I haven't touched this track since 2020, when you publish to any track they are scanning all the latest versions in all your tracks for this permission, even if the track is not used anymore.
I've just submitted an update to my closed alpha track and waiting for the result...

If you didn’t use these “file_open” or “permission_handler” packages and also get the issue of flutter Remove REQUEST_INSTALL_PACKAGES Permission then you have to find out which package is the culprit for this issue.
First generate the app released version from Build > Flutter > Build App Bundle. Now go to your project root folder and open > build/app/outputs/logs/manifest-merger-release-report.txt Now check which package generate that permission and use different package for that.
You can learn more from here: Fix Flutter Remove REQUEST_INSTALL_PACKAGES Permission From Play Console

Set release rollout 100% it will deactivate all the builds except release build

Article is not available.
Please help.
I am using open_file and it is required in my project.
My previous build have request_install_packages permission.
I am also uploading the apk with permission but still my app is getting rejected.
What to do now?
I tried many solution but not able to publish app on playstore.
Here is the mail attached.

mohitleo03 · 2022-11-01T06:36:59Z

@lakshydeep-14 the solution is discussed above but if you want assistance the try these steps -

First of all the problem started with using dart package like open_file which is having sensitive android permission REQUEST_INSTALL_PACKAGES. according to my knowledge this permission allows application to install other application (due to which it becomes sensitive according to Google Play). So for removing this permission you can do any of the following -

Best solution is to replace the dart package open_file with open_filex or open_file_safe . these both packages can open files like pdf, etc. but they don.t have sensitive permission REQUEST_INSTALL_PACKAGES due to which our application will get approval easily.
another simple solution is simply remove or comment this android permission REQUEST_INSTALL_PACKAGES from the manifest file of package open_file in android studio -
another solution is replacing the permission line with this line -

Note - using any one of the above 3 solution is enough.

IMPORTANT - Yes currently your apk is not having this permission and you can upload this apk bundle to Play Console but your can still got rejected :(
Reason - any other track (track means - production, open testing, closed testing, internal testing, pre-registration) if any of the track is having an apk bundle live with that permission your app is going to get rejected. So, what is did was created a new release in every track (only those tracks in which I earlier released the application, like I don't have created any release in pre-registration so I didn't created a new release for that) and choose full rollout.
Just make sure every track has been updated with new apk and sent for review from your side. (latest apk bundle must not have this permission REQUEST_INSTALL_PACKAGES).

How to check whether the apk bundle is having the REQUEST_INSTALL_PACKAGE or not -
Upload your apk bundle to Play Console, go to app bundle explorer (you can find this option in left sidebar menu in Play Console), you would be able to see all the apk bundles uploaded by you.
Click on this forward arrow to see details of your apk bundle.

Then click on show details of permissions -

If you have any other issue then you can tag me, still if you receive the same mail from Play console then you can submit and appeal for help in Policy Status section or wait for the updated review on Google Play Console.

lakshydeep-14 · 2022-11-01T07:45:51Z

@lakshydeep-14 the solution is discussed above but if you want assistance the try these steps -

First of all the problem started with using dart package like open_file which is having sensitive android permission REQUEST_INSTALL_PACKAGES. according to my knowledge this permission allows application to install other application (due to which it becomes sensitive according to Google Play). So for removing this permission you can do any of the following -

Best solution is to replace the dart package open_file with open_filex or open_file_safe . these both packages can open files like pdf, etc. but they don.t have sensitive permission REQUEST_INSTALL_PACKAGES due to which our application will get approval easily.

another simple solution is simply remove or comment this android permission REQUEST_INSTALL_PACKAGES from the manifest file of package open_file in android studio -

another solution is replacing the permission line with this line -

Note - using any one of the above 3 solution is enough.

IMPORTANT - Yes currently your apk is not having this permission and you can upload this apk bundle to Play Console but your can still got rejected :( Reason - any other track (track means - production, open testing, closed testing, internal testing, pre-registration) if any of the track is having an apk bundle live with that permission your app is going to get rejected. So, what is did was created a new release in every track (only those tracks in which I earlier released the application, like I don't have created any release in pre-registration so I didn't created a new release for that) and choose full rollout. Just make sure every track has been updated with new apk and sent for review from your side. (latest apk bundle must not have this permission REQUEST_INSTALL_PACKAGES).

How to check whether the apk bundle is having the REQUEST_INSTALL_PACKAGE or not - Upload your apk bundle to Play Console, go to app bundle explorer (you can find this option in left sidebar menu in Play Console), you would be able to see all the apk bundles uploaded by you. Click on this forward arrow to see details of your apk bundle. Then click on show details of permissions -

If you have any other issue then you can tag me, still if you receive the same mail from Play console then you can submit and appeal for help in Policy Status section or wait for the updated review on Google Play Console.

@mohitleo03 I have a previous version that has this permission in the first image.
I have commented the line as you said now it doesn't have that permission
in the second image.
what to select in the form in the third image?

mohitleo03 · 2022-11-01T07:49:58Z

@lakshydeep-14 No, We are not using this permission anymore so don't look for this form. I also filled this form which was a mistake.
Just create a new release on each -

only create if you have previous apk with that permission in that particular track

eggysudianto · 2022-11-02T00:48:33Z

issue solved #221 (comment)

bharathking · 2022-11-02T06:06:42Z

@mohitleo03 Go to Testing - open testing - manage track - pause.
Submit build
Open testing I hope this build5(1.0.2) using that permission

mohitleo03 · 2022-11-02T06:08:56Z

@mohitleo03 Go to Testing - open testing - manage track - pause. Submit build Open testing I hope this build5(1.0.2) using that permission

Thank you @bharathking but my issue is resolved i was helping someone else :)

blue492 · 2022-11-02T07:14:35Z

The issue is solved for me by uploading a new version to Testing, because I had an old version which included that permission in Testing. I paused Testing to avoid problem in future.

I added in AndroidManifest.xml
<uses-permission android:name="android.permission.REQUEST_INSTALL_PACKAGES" tools:node="remove"/>

You can contact the Policy team for further clarification regarding your app’s policy violation.

You can also chat with Google team: Chat Link Monday through Friday

mohitleo03 · 2022-11-03T07:15:04Z

I am removing in Android.manifest. But for some reason there is a "REQUEST_INSTALL_PACKAGES".

Android>app>src>main>AndroidManifest.xml

<manifest xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:tools="schemas.android.com/tools"
    package="com.SimpleDrawPaint">
 　<uses-permission android:name="android.permission.REQUEST_INSTALL_PACKAGES" tools:node="remove"/>
...
</manifest>

manifest-merger-release-report.txt

uses-permission#android.permission.REQUEST_INSTALL_PACKAGES
ADDED from /Users/t/StudioProjects/*****/android/app/src/main/AndroidManifest.xml:5:4-104
	tools:node
		ADDED from /Users/t/StudioProjects/*****/android/app/src/main/AndroidManifest.xml:5:80-102
	android:name
		ADDED from /Users/t/StudioProjects/*****/android/app/src/main/AndroidManifest.xml:5:21-79

you can also use another package instead of just removing the permission, like you can use open_filex inspite of open_file.

mohitleo03 · 2022-11-03T11:09:51Z

@jtaxiexpress
If you are using open_filex the I don't think that your android project should contain REQUEST_INSTALL_PACKAGES as you can see my project file too -

I think you should try to build android project by flutter build apk so that the changes you have done in flutter project should get reflected in android project too.

ayman-elslamony · 2022-11-03T14:31:01Z

I fix This problem by following these steps:

Removed open_file and added another package called open_filex
Sure you removed REQUEST_INSTALL_PACKAGES from AndroidMainfiest.xml.
Create an app bundle and upload it to Play Console.
Open Play Console and go to the testing page check if there are any app bundles in:
1. Open testing (Testing > Open testing)
2. Closed testing (Testing > Closed testing).
3. Internal testing (Testing > Internal testing).
4. ...
  if it exists create a new release and add the uploaded app bundle.
go to the Production page and create a new release then add it for review.

note: If there is an app bundle that you previously uploaded on the test page and it was accepted by Google before, be sure to replace it by creating a new release and add the uploaded app bundle.

Lazizbek97 · 2022-11-21T13:01:42Z

Has someone found which package(or plugin) requires open_file plugin? I tried to delete it from my app several times. But still, it suddenly appears...

blue492 · 2022-11-21T13:10:48Z

The issue is solved for me by uploading a new version to Testing, because I had an old version which included that permission in Testing. I paused Testing to avoid problem in future.

I added in AndroidManifest.xml <uses-permission android:name="android.permission.REQUEST_INSTALL_PACKAGES" tools:node="remove"/>

The issue is solved for me by uploading a new app version to Testing, because I had an old version which included that "REQUEST_INSTALL_PACKAGES" in Testing. Then I paused Testing to avoid problem in future.

I added in AndroidManifest.xml and uploaded a new version to Production in Google play

ca-ruthish · 2022-11-24T03:31:00Z

I used these plugins open file, open filex, open file safe but still the error does not solved. Then I add URL launcher package then my got published. And more thing when your app published in any of the testing release pause the track and create a new release in production.
Don't forget to add these lines in AndroidManifest.xml
<uses-permission android:name="android.permission.REQUEST_INSTALL_PACKAGES" tools:node="remove" />
Then under the application tag add these lines too..
<queries> <intent> <action android:name="android.intent.action.VIEW" /> <data android:scheme="file" /> </intent> </queries>
I hope this will help you REQUEST_INSTALL_PACKAGES Error.

shaileshpendams · 2022-11-24T09:26:05Z

I remove this permission by this video instructions.
https://shaileshpendam.com/blog/REQUEST_INSTALL_PACKAGES/

tamilarasansrf · 2023-01-04T09:14:28Z

Finally i resolved using this
https://gist.github.com/tamilarasansrf/d472bbd70f0c0ca5f73d7ee4cdb158a3

tamilarasansrf · 2023-01-04T09:15:05Z

Finally i resolved using this
https://gist.github.com/tamilarasansrf/d472bbd70f0c0ca5f73d7ee4cdb158a3

everfgmolinas added a commit to iHub-PTI/boldo-mobile that referenced this issue Sep 12, 2022

refactor: change plugin open_file with open_filex

ed0b573

related issue: crazecoder/open_file#204

angeloborrelli mentioned this issue Sep 18, 2022

🐛 [firebase_core] REQUEST_INSTALL_PACKAGES firebase/flutterfire#9565

Closed

tel-kho mentioned this issue Sep 20, 2022

[url_launcher_android] Issue regarding REQUEST_INSTALL_PACKAGES permission after uploading the application to PlayStore flutter/flutter#111947

Closed

jamesncl mentioned this issue Oct 30, 2022

REQUEST_INSTALL_PACKAGES due google playstore policy #222

Closed

ravitejaavv mentioned this issue Apr 12, 2023

[Android] Play store request new permission to this plugin used apps ravitejaavv/store_checker#13

Closed

crazecoder closed this as completed Apr 26, 2023

w568w mentioned this issue Aug 4, 2023

[BUG] 声明了不需要的 Android 权限 DanXi-Dev/DanXi#272

Closed

Remove REQUEST_INSTALL_PACKAGES permission #204

Remove REQUEST_INSTALL_PACKAGES permission #204

Comments

Zazo032 commented Jul 20, 2022

GoldenSoju commented Jul 22, 2022

GoldenSoju commented Jul 22, 2022

Zazo032 commented Jul 22, 2022

GoldenSoju commented Jul 22, 2022

Zazo032 commented Jul 22, 2022

GoldenSoju commented Jul 22, 2022

Kishan-Somaiya commented Jul 25, 2022 • edited

LuisMiguelSS commented Sep 6, 2022

MilesAdamson commented Sep 9, 2022

hedi-ghodhbane commented Sep 16, 2022

gerritwitkamp commented Sep 19, 2022

hedi-ghodhbane commented Sep 19, 2022

LuisMiguelSS commented Sep 19, 2022

iamtechmanish commented Oct 2, 2022 • edited

undamatlamanikanta commented Oct 13, 2022 • edited

The following line prevents the package from being accidentally published to

pub.dev using pub publish. This is preferred for private packages.

The following defines the version and build number for your application.

A version number is three numbers separated by dots, like 1.2.43

followed by an optional build number separated by a +.

Both the version and the builder number may be overridden in flutter

build by specifying --build-name and --build-number, respectively.

In Android, build-name is used as versionName while build-number used as versionCode.

Read more about Android versioning at https://developer.android.com/studio/publish/versioning

In iOS, build-name is used as CFBundleShortVersionString while build-number used as CFBundleVersion.

Read more about iOS versioning at

https://developer.apple.com/library/archive/documentation/General/Reference/InfoPlistKeyReference/Articles/CoreFoundationKeys.html

The following adds the Cupertino Icons font to your application.

Use with the CupertinoIcons class for iOS style icons.

firebase_dynamic_links: ^0.5.0+11

flutter_facebook_login: ^3.0.0

device_preview: ^1.1.0

contacts_service: ^0.6.1

image pickers

flutter_localizations:

collection: ^1.15.0-nullsafety.4

latlong: ^0.6.1

flutter_libphonenumber: ^1.1.0

flutter_app_restart: ^1.0.0

flutter_phoenix: "^1.0.0"

For information on the generic Dart part of this file, see the

following page: https://dart.dev/tools/pub/pubspec

The following section is specific to Flutter.

The following line ensures that the Material Icons font is

included with your application, so that you can use the icons in

the material Icons class.

To add assets to your application, add an assets section, like this:

An image asset can refer to one or more resolution-specific "variants", see

https://flutter.dev/assets-and-images/#resolution-aware.

For details regarding adding assets from package dependencies, see

https://flutter.dev/assets-and-images/#from-packages

To add custom fonts to your application, add a fonts section here,

in this "flutter" section. Each entry in this list should have a

"family" key with the font family name, and a "fonts" key with a

list giving the asset and other descriptors for the font. For

example:

fonts:

- family: Schyler

fonts:

- asset: fonts/Schyler-Regular.ttf

- asset: fonts/Schyler-Italic.ttf

style: italic

- family: Trajan Pro

fonts:

- asset: fonts/TrajanPro.ttf

- asset: fonts/TrajanPro_Bold.ttf

weight: 700

For details regarding fonts from package dependencies,

see https://flutter.dev/custom-fonts/#from-packages

Gbarago commented Oct 18, 2022

permission_handler: ^8.1.1

in_app_review: 2.0.0

flutter_money_formatter: ^0.8.3

another_flushbar: ^1.10.5

Galeen-Bidpath commented Oct 18, 2022

Gbarago commented Oct 18, 2022

Remove `REQUEST_INSTALL_PACKAGES` permission #204

Remove `REQUEST_INSTALL_PACKAGES` permission #204

Kishan-Somaiya commented Jul 25, 2022 •

edited

iamtechmanish commented Oct 2, 2022 •

edited

undamatlamanikanta commented Oct 13, 2022 •

edited

pub.dev using `pub publish`. This is preferred for private packages.

blue492 commented Oct 28, 2022 •

edited

bharathking commented Oct 30, 2022 •

edited

lakshydeep-14 commented Nov 1, 2022 •

edited

blue492 commented Nov 2, 2022 •

edited

mohitleo03 commented Nov 3, 2022 •

edited

ayman-elslamony commented Nov 3, 2022 •

edited