Question, new QUERY_ALL_PACKAGES requirements, what is at risk?

[codyfilatov]

The QUERY_ALL_PACKAGES permission is being placed under the "core functionality" deal with Google. Effectively meaning it cannot be used. If I remove this permission from my application, what functionality will not be accessible?

[Gayathri-GA]

@codyfilatov If your app uses android version 11+ QUERY_ALL_PACKAGES permission need to be added in order to make the app communicate with other app, If you tend to remove this permission the application stop to work or trigger to communicate.

[mbombonato]

Hello! First, thanks for this nice plugin!

Google is asking a huge amount of explanations for the QUERY_ALL_PACKAGES permission usage when we publish the app.

It would be possible to remove the QUERY_ALL_PACKAGES permissions and just use the code below for our specific packages? Example:

<queries>
   <package android:name="com.google.android.apps.maps"/>
</queries>

QUERY_ALL_PACKAGES it's probably too much for most use cases and should be optional. Is that possible? Is the "queries" permission enough to launch a simple external app?

Thanks!

[Gayathri-GA]

@mbombonato Thanks for posting the suggestion. @aldwinsetiawan The package code has been updated with the latest changes and will get published to pub.dev in a day.

[aldwinsetiawan]

Hi, bumping on this issue, i noticed that the QUERY_ALL_PACKAGES permission is added to my manifest from this package. I added this line <uses-permission android:name="android.permission.QUERY_ALL_PACKAGES" tools:node="remove" /> to remove it but the permission still there on the final manifest.

Any solution to this?

[kabaluyot]

@Gayathri-GA do you have ETA when it will be updated to pub.dev?

[Gayathri-GA]

@kabaluyot It will be getting published shortly.