We have a app on google play store something like snapchat (Social Networking App) but with advance chat features including app package installs. Our app got removed from playstore because we are using REQUEST_INSTALL_PACKAGES permission and google thinks it's not core purpose of our app. As per the document for REQUEST_INSTALL_PACKAGES permission state
Communication services that support attachments;
can request this permission. Our app has inbuilt chat functions which supports communications with chat attachments(APK). Where whatsapp,telegram etc can have this permission too.
We mentioned this in our policy section
Our app has chat feature which enable users to shares different types
of attachments including APK. To install APK inside our app we need
REQUEST_INSTALL_PACKAGES which help users to share and install APK.
It's same like other messaging app like telegram,whatsapp etc.
And selected communication services that support attachments & file sharing, transfer or management
Which permitted functionality does your app provide section and App functionality in Why does your app need to use the REQUEST_INSTALL_PACKAGES permission section
Are REQUEST_INSTALL_PACKAGES is invalid for our app because every other messaging app having this permission and we are getting rejecting even after appeal. Can anyone put insight on this issue please.
Related
Hi Developers at Ministerio de Telecomunicaciones Ecuador,
Per last email, your app FirmaEC (ec.gob.firmadigital.firmaec_app) has been rejected from Google Play for not resolving the previously communicated policy issue (copied below for your reference). To resolve this issue and get your app changes published on Google Play, please address the issues highlighted in the earlier email and resubmit the app.
Publishing Status
App Status: Rejected
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: Permission use is not directly related to your app's core purpose.
We found that your app is not compliant with how REQUEST_INSTALL_PACKAGES permission is allowed to be used. Specifically, the use of the permission is not directly related to the core purpose of the app.
Issue details
We found an issue in the following area(s):
SPLIT_BUNDLE 15
Additionally, follow these steps to bring your app into compliance:
Please remove the use of REQUEST_INSTALL_PACKAGES permission from your app.
About the Request Install Packages Permission
The REQUEST_INSTALL_PACKAGES permission allows an application to request the installation of app packages. To use this permission, your app’s core functionality must include:
Sending or receiving app packages, AND
Enabling user-initiated installation of app packages.
Permitted functionalities include any of the following:
Web browsing or search
Communication services that support attachments
File sharing, transfer or management
Enterprise device management
Backup and restore
Device migration / phone transfer
The REQUEST_INSTALL_PACKAGES permission may not be used to perform self updates, modifications, or the bundling of other APKs in the asset file unless for device management purposes. All updates or installing of packages must abide by Google Play’s Device and Network Abuse policy and must be initiated and driven by the user.
For more help addressing this issue, read more in our Help Center.
Action required: Submit an updated app for review
Here's what to do to help get your app on Google Play:
Make sure to read the applicable policies or requirements listed below:
Request Install Packages Permission
Make appropriate changes to your app (if possible), and be sure to address the issue described above. You may also want to check your app's store listing for compliance, if applicable.
Double check that your app is compliant with all other Developer Program Policies.
If you made changes to your app bundle, store listing, or APK, please sign in to your Play Console and submit the update(s).
Contact support
If you've reviewed the policy and feel our decision may have been in error, please reach out to our policy support team. We'll get back to you within 2 business days.
try:
App is not compliant with how REQUEST_INSTALL_PACKAGES permission is allowed
I got an email that is my app is rejected but in my developer console it shows in review, why?
App Status: Rejected
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: Not a core feature
The feature you identified that is dependent on this permission does not appear to be critical to the core functionality of your app.
Core functionality is defined as the main purpose of the app. Without this core functionality, the app is "broken" or rendered unusable. The core functionality, as well as any core features that comprise this core functionality, must all be prominently documented and promoted in the app's description.
Please update your app so that the feature does not use this permission or ensure that the core functionality is prominently documented and promoted in the app's description and resubmit your app on Play Developer console.
Additionally, follow these steps to bring your app into compliance:
Read more about Use of All Files Access Permission
See Android storage use cases and best practices
About the All Files Access Permission Policy
Files and directory attributes on a user's device are regarded as personal and sensitive user data subject to the Personal and Sensitive User Data policy and the following requirements:
Apps should only request access to device storage which is critical for the app to function, and may not request access to device storage on behalf of any third-party for any purpose that is unrelated to critical user-facing app functionality.
Android devices running Android "R" (Android 11) or later, will require the MANAGE_EXTERNAL_STORAGE permission in order to manage access in shared storage. All apps that target R or later and request broad access to shared storage ("All files access") must successfully pass an appropriate access review prior to publishing. Apps allowed to use this permission must clearly prompt users to enable "All files access" for their app under "Special app access" settings. For more information on the R requirements, please see this help article.
our previous apk has been removed from google play store due to new policy because of we are giving permission for READ, SEND and WRITE SMS. Now we have removed all these permission and trying to deploy this modified apk on play store. When we upload it on play store, google ask some permission like Default SMS handler, Phone handler etc. but out app didn't have such permissions. Google restrict us to select at least one permission and when we continue with one of these permission(we are selecting Default SMS handler), every time google is rejecting our apk and removing our apk from play store.
Can any one guide us to get out this problem?
I have searched over google but unable to find how to set permission for Default SMS handler in android manifest.xml?
If you have permissions which deal with Reading SMS, OR Call Logs it will come under the use of high risk or sensitive permission. Please read that for detail info.
Google Play may provide a temporary exception to apps that aren't Default SMS, Phone, or Assistant handlers when:
Use of the permission provides core app functionality to users.
There is currently no alternative method to provide the core functionality.
You must fill the form and google will approve it.
If you think that this permissions are necessary for your app and not just useless, you can follow the steps mentioned in the official document here.
I have published simple card-game in android play store. I had used crashalytics to taken care of crashes. However, as many of you must have experienced Google Play notifications about "Violation of Usage of Android Advertising ID policy and section 4.8 of the Developer Distribution Agreement". In that email it was written that
you may opt-out of this requirement by removing any requests for sensitive permissions or user data.
I have already removed Firebase analytics and Crashalytics libraries from my app. For now my app has only permission to android.permission.ACCESS_NETWORK_STATE. Is it "sensitive" permission? What are these 'sensitive' permissions which I can avoid for future development? Just another quick question, is there better alternative to crashalytics which will not violate any of these policies?
ACCESS_NETWORK_STATE category level is NORMAL which might indicate that it's not a sensitive permission like CAMERA is.
https://developer.android.com/reference/android/Manifest.permission.html#ACCESS_NETWORK_STATE
I am adding some Admin permission in manifest. after 2 days wait its not publishing app on play store with this permissions. I listed below that permissions
BIND_DEVICE_ADMIN
DEVICE_ADMIN_DISABLE_REQUESTED
DEVICE_ADMIN_ENABLED
Now, while i am trying to publish that app in play store at that time app successful upload but it's not publishing. It's every time show "Pending publication". And while i remove this permission it's published Successful.
So, any one can tell me that what is the reason behind this issue. Why play store not publishing my app with that permission?
Read through the Deceptive Device Settings Changes policy for more details, and make sure your app complies with all policies listed in the Developer Program Policies.
If you don't need the BIND_DEVICE_ADMIN permission in your app:
Remove your request for this permission from your app's manifest.
Sign in to your Play Console and submit the modified, policy compliant APK.
Or,
if you need the BIND_DEVICE_ADMIN permission in your app:
Include the following snippet in your app’s store listing description:
“This app uses the Device Administrator permission.”
Provide prominent user facing disclosure of this usage before asking the user to enable this permission within your app. Your disclosure must meet each of the following requirements:
Disclosure must be displayed in normal course of usage of your app. Your users should not be required to navigate into a menu or settings to view disclosure.
Disclosure must describe the functionality Device Admin permission is enabling for your app. Each security policy used with the Device Admin request must be declared in your disclosure, and each policy must be accompanied with justification for the request.
Disclosure cannot only be placed in your privacy policy, terms of service or end user license agreement (EULA).
If approved, your app will again be available with all installs, ratings, and reviews intact.
Publishing status
(https://productforums.google.com/forum/#!topic/play/xkxQuf-oDck)
Near the top of individual apps’ pages on your Developer Console, you can see your app’s latest publishing status. Whether you’re publishing an app for the first time or making an update, you can use your publishing status to understand your app’s availability on Google Play.
Here are the different statuses that can be displayed for your app:
Draft: App hasn’t been published on Google Play.
Note: If the Publish app option isn’t available, click Why can’t I publish? for more information or check your app’s pages on the left menu to make sure you’ve included all required information for your app.
Pending publication: App is currently being processed for publishing.
Published: App is published and available on Google Play.
Rejected: App has been rejected and wasn’t published due to a violation of Google Play policies. More information about the violation is available near the top of your app’s pages on the Developer Console. Once you make a change to your app to address the violation, you can submit it again.
Suspended: App is suspended due to a violation of Google Play Policies (Content Policy, Developer Distribution Agreement). An email with details about the suspension is sent to the account owner.