# Google Play: QUERY_ALL_PACKAGES permission not allowed for your app > Google Play rejected or flagged your app for QUERY_ALL_PACKAGES. Find the library that adds it, replace it with a entry, or declare a real need. Canonical: https://app369.com/fix/google-play-query-all-packages-permission/ Last updated: 2026-11-09 QUERY_ALL_PACKAGES is an Android 11 permission that lists every installed app, and Google Play allows it only when an app’s core purpose needs it. Many flagged apps never asked for it on purpose: a library can add it. Remove it or swap in a narrower query, then send a new release. **Short answer** Open the merged manifest in Android Studio to see which library adds QUERY_ALL_PACKAGES. If your app only needs to open or check a few known apps, list them in a element and remove the permission with tools:node="remove". Keep it only if the app is a device search, antivirus, file manager or browser style app, and then fill in the Permissions Declaration Form. Rather not fix it yourself? [**App Fix Ticket**](https://app369.com/fixed-price/flutter-firebase-bug-fix/) starts with a fixed-price diagnosis, then a fixed price for the fix before any fix work. ## **Why Play flags it, and the fix** 1. 01 ### **A library added the permission** > “The Merged Manifest view shows the results of the merged manifest on the left and information about each merged manifest file on the right” [**Android Developers, Manage manifest files**](https://developer.android.com/build/manage-manifests) Plugins that open other apps, share to them or check if they are installed sometimes ship the permission in their own manifest, and it merges into yours. Open AndroidManifest.xml, click the Merged Manifest tab, and find which file the permission came from. Updating that library may drop it. 2. 02 ### **Your app doesn’t have a core need for it** > “Permitted uses include device search, antivirus apps, file managers, and browsers.” [**Google Play Help, Use of the broad package visibility permission**](https://support.google.com/googleplay/android-developer/answer/10158779) Play allows the permission only when searching all installed apps is the main purpose of the app. Opening a maps app, a payment app or a web link is not that purpose, so the fix is to stop requesting it. A browser app itself is a permitted use. 3. 03 ### **Replace it with a entry** > “In the rare cases where the element doesn't provide adequate package visibility, you can use the QUERY_ALL_PACKAGES permission.” [**Android Developers, Package visibility filtering on Android**](https://developer.android.com/training/package-visibility) Name the apps or intents your app needs to see in a element, then remove the broad permission so a library can’t add it back.``` ``` 4. 04 ### **Your app really needs it** > “Apps that fail to meet the policy requirements or do not submit the Permissions Declaration Form may be removed from Google Play.” [**Google Play Help, Use of the broad package visibility permission**](https://support.google.com/googleplay/android-developer/answer/10158779) If listing every installed app is the core feature, keep the permission, describe that feature prominently in the store listing, and fill in the Permissions Declaration Form in Play Console with how the app uses it. Checked against the vendor’s docs on November 9, 2026: [Google Play Help: Use of the broad package (App) visibility (QUERY_ALL_PACKAGES) permission](https://support.google.com/googleplay/android-developer/answer/10158779); [Android Developers: Package visibility filtering on Android](https://developer.android.com/training/package-visibility); [Android Developers: Manage manifest files](https://developer.android.com/build/manage-manifests). ## **Rather hand it over?** Fixed scope, fixed price, paid upfront. The work happens in writing; no call needed. - [from $450**App Fix Ticket**One reproducible bug in an existing mobile or web app, diagnosed and fixed.**See scope and start**](https://app369.com/fixed-price/flutter-firebase-bug-fix/) [**All 127 Fiverr reviews**](https://app369.com/reviews/) Related: [**Google Play photo and video permissions**](https://app369.com/fix/google-play-photo-video-permissions/) · [**Google Play foreground service declaration**](https://app369.com/fix/google-play-foreground-service-declaration/) · [**Google Play Data safety form rejected**](https://app369.com/fix/google-play-data-safety-form-rejected/) · [**Google Play USE_EXACT_ALARM rejection**](https://app369.com/fix/google-play-exact-alarm-permission/) Questions ## **More on this launch**
**Do I need a new release after removing it? **+ Yes. The permission is in the app bundle, so upload a new version without it. If an older release that still has it is on a testing or production track, replace that release too.
**Does the app still work without it? **+ For most apps, yes. When the app targets Android 11 (API level 30) or higher, the system already hides most other apps unless you name them in , so test the features that open other apps on an Android 11 or newer device before you release.
**Can you fix it for me? **+ If one bug is the whole problem, the App Fix Ticket covers it: a written diagnosis first, then the fix. If the app has more going on, the Launch Check is a written check of the whole app. Each issue found is rated critical, high, medium or low, with where it is and how it was confirmed. No issues worth fixing, no charge. If the Launch Check finds nothing rated medium or higher, Simon refunds the full $450. You keep the report either way. This applies to the first 10 Launch Checks bought after October 30, 2026.
Something else? ## **Describe it and get a written quote** Describe the app and where it is in the launch. You get a written scope, a fixed price and a timeline; Simon replies by email, usually within one business day. [**Describe your problem **→](https://app369.com/contact/) [**All fixes**](https://app369.com/fix/)