-
Notifications
You must be signed in to change notification settings - Fork 431
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove REQUEST_INSTALL_PACKAGES
permission
#204
Comments
There is a fork that got this permission removed. Maybe that helps you for the moment. (Kudos to this SO question.) |
I created an updated fork with
You can use it via: open_filex:
git:
url: https://github.com/GoldenSoju/open_file.git |
Is that one available through pub.dev? |
@Zazo032 open_filex:
git:
url: https://github.com/GoldenSoju/open_file.git |
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... |
A fork of open_file is available in pub.dev as open_filex which removes the Request Install APK Permission. |
Could we get this fixed here? It's an important issue and the latest fix was in no more than 15 days |
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 |
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 |
are there any differences between open_file_safe and open_filex? |
@gerritwitkamp I think both are the same, they just removed support for .apk so this request_install_packages is not needed anymore. |
https://github.com/javaherisaber/open_filex seems more actively maintained |
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 |
i faced same issue and changed open_file to open_file_safe My AndroidManifest.xml
My Pubspec.yaml name: ******* The following line prevents the package from being accidentally published topub.dev using
|
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.1slide_button: ^0.2.8 in_app_review: 2.0.0flutter_local_notifications: 5.0.0 flutter_money_formatter: ^0.8.3flutter_spinkit: ^3.1.0 another_flushbar: ^1.10.5shimmer: ^2.0.0 |
If you add this to your AndroidManifest.xml should exclude the permission from the merged manifest.
|
Thanks for this. |
or is i possible that i am doing it long |
I have submitted an update on my build this morning and was approved. After you made your build can check if the permission is still decleared in the merged manifest in |
alright will do this and se i it works |
Just got a rejection mail from google play.. problem still exists |
Maybe you are mmissing something. |
okay |
second image is not the right one, should be from merged_manifest folder(scroll down) not from bundle_manifest In general it looks OK. |
ok |
I submitted a version 88 (3.5.4) which had I added the following row: 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. |
|
|
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 I've just submitted an update to my closed alpha track and waiting for the result... |
Set release rollout 100% it will deactivate all the builds except release build |
If its closed alpha testing - manage track - pause |
https://youtu.be/TaCxgCwQNpc - please verify all the steps done. I got approved two days before... |
Article is not available. |
@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 -
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 :( How to check whether the apk bundle is having the REQUEST_INSTALL_PACKAGE or not - 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. |
@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. |
issue solved #221 (comment) |
@mohitleo03 Go to Testing - open testing - manage track - pause. |
Thank you @bharathking but my issue is resolved i was helping someone else :) |
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 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 |
@jtaxiexpress |
I fix This problem by following these steps:
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. |
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... |
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 |
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. |
I remove this permission by this video instructions. |
Finally i resolved using this |
1 similar comment
Finally i resolved using this |
Today I received a new message regarding a Flutter app published in Play Store, with the following information:
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
The text was updated successfully, but these errors were encountered: