fix: remove REQUEST_INSTALL_PACKAGES permission. - #1

remove dangerous permission REQUEST_INSTALL_PACKAGES in Android in OpenFilePlugin.java

We are having this issue as well, even though the permission has been removed it from the manifest. It seems as if Google is doing a plain text search. Maybe it should be deleted altogether instead of commented out?

I did remove this commit in my app after they reject my release and submit another one and they still reject the app, 
Even though I did reverse engineering for the aab to make sure that this permission does not exist in the manifest file, I don't know why they still see that we use this permission.

I'm facing this same problem too. I was using open_file, and changed to this one, cleaned the setup and Google Play is still recusing my app update due to this permission.

The curious detail is that I've read the entire merged_manifests, and there is no such permission. Why the hell Google Play still rejecting?

Same thing here, no matter open_file with

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

or open_filex

or any fork with no mention in the code about the permission, we're getting it rejected too.

That's the same thing that happened to us too, and got rejected.
Then we submitted an appeal, but that process took too long,
We removed the permission even from commented code from the package (in case they are doing a plain search into reversed code).
Then "because our case was a new app" we created a new project on the play console, and it got approved within a couple of hours, and all updates after went smoothly as well.

The appeal seems to resolve it.

In my case, I sent an appeal, and they rejected for another reason now (this is very much strange).

Your offer does not clearly and accurately describe the terms of your subscription, including the cost, frequency of billing cycle, and whether a subscription is required to use the app.

My app is with the same subscription area for more than 1 year 😄

@thebeast1 @rpekarek-tc @marcellocamara @RafaRuiz
A new version for this issue is published now at open_filex