When submitting an app for publication within the Google Play Store, Google Play Support reviews the app (and app updates as well) to determine whether it is compliant with all the Developer Program Policies (opens in a new tab).
This document provides guidelines on how to address your branded app’s rejection by Android. In the following section of this document, you will find a common issue that causes branded mobile apps to get rejected. Details provided by Google Play Support are listed in the Rejection Reason section. In the Addressing the Rejection section, you can learn how to bring your app into compliance and submit an updated app for review.
For any other info on the Branded Mobile App, find all of the details in the dedicated articles of the Knowledge Base.
Your app has been rejected and wasn't published due to the policy issue(s) listed below. If you submitted an update, the previous version of your app is still available on Google Play.
Issue found: Less broad app-visibility method should be used
We are unable to approve your app’s use of QUERY_ALL_PACKAGES permission because the declared task can be done with a less broad app-visibility method.
Additionally, follow these steps to bring your app into compliance:
Please remove the use of QUERY_ALL_PACKAGES permission from all the artifact versions within the submission. This includes production track, internal track and testing track etc.
Addressing the Rejection
The issue is related to the QUERY_ALL_PACKAGES permission, which cannot be used when the required task can be done with a less broad app-visibility method. More information on the use of the broad package (App) visibility (QUERY_ALL_PACKAGES) permission.
Actually, this permission has already been removed by Docebo with Branded App version 4.7.0, but it was included in the previous versions.
Please perform the following steps in order to bring your app into compliance and submit an updated app for review:
- Open the Google Play Console
- Open the Production menu item
- You will see a warning dialog box (You can't submit updates as some information about your app is incomplete). Open it and click on the Go to App content button.
- In the Sensitive permissions and APIs section, click on the Start button
- A section on the query all packages permission is displayed, where you can see that your app is not compliant. In this section, click on the View app bundles and APKs button.
- Check which old bundles use sensitive permissions and copy the relative version code
- Now access the App bundle explorer menu item and paste the version code in the search box
- The app version will appear in the table below. Click on the View app version arrow icon at the end of the app bundle’s row to display the details of the selected app bundle.
- In the Details tab, expand the Releases dropdown and click on the active release link. You can find four release types: internal, closed, open testing, and production. Please note that you need to repeat steps from 9 to 15 for each one of the active releases found here.
- On the page that opens, click View in the Release Summary section
- Please note that if you have already created a release before without publishing it (it’s a draft) and the release includes the old version with the query all packages permission enabled, you need to discard the release by clicking the Discard release button.
- On the top right side of the page, click Create new release
- In the App bundles section, upload a build — version 4.9.1 or later — that you have generated in the Branded Mobile App Publisher menu in Docebo platform and that you have re-signed following all the steps in the linked article
- Fill in the required fields (Release name and Release notes), then click on Review
- Fill the Roll-out percentage field with 100.0 to completely deactivate the non-compliant APK. Click on the Start rollout button to complete the rollout of your release.
- Refresh the Google Play Console
- Reach the Production menu item and create a new production release
- Go to the Publishing overview menu item and press the Send changes for review button
- Confirm your action by clicking the Send for review button in the modal that opens
- At this point, after a few hours, Google should approve your build!