App Rejected by google play store due to permissions handler

Question

I am doing internal testing on my app for Google Play Store but every time my app gets rejected by Google with the following reply:

Requested permissions do not match core functionality of the app You declared Default SMS handler (and any other core functionality usage while default handler) as the core functionality of your app. However, after review, we found that your app does not match the declared use case(s). Learn more about permitted uses and exceptions. Please either: • Make changes to your app so that it meets the requirements of the declared core functionality or, • Select a use case that matches your app's functionality

I do not know why it happen even I have already declared all permission which I used in my app. Please help me how I can resolve it.

Answer 1

SMS and Call Log Permissions are regarded as personal and sensitive user data subject to the Personal and Sensitive Information policy, and the following restrictions: Restricted Permission Requirement Call Log permission group (eg READ_CALL_LOG, WRITE_CALL_LOG, PROCESS_OUTGOING_CALLS) It must be actively registered as the default Phone or Assistant handler on the device. SMS permission group (eg READ_SMS, SEND_SMS, WRITE_SMS, RECEIVE_SMS, RECEIVE_WAP_PUSH, RECEIVE_MMS) It must be actively registered as the default SMS or Assistant handler on the device.

Apps lacking default SMS, Phone, or Assistant handler capability may not declare use of the above permissions in the manifest . This includes placeholder text in the manifest. Additionally, apps must be actively registered as the default SMS, Phone, or Assistant handler before prompting users to accept any of the above permissions and must immediately stop using the permission when they're no longer the default handler. The permitted uses and exceptions are available on this Help Center page.

Apps may only use the permission (and any data derived from the permission) to provide approved core app functionality Core functionality is defined as the main purpose of the app. This may include a set of core features, which must all be prominently documented and promoted in the app's description. Without the core feature(s), the app is “broken” or rendered unusable. The transfer, sharing, or licensed use of this data must only be for providing core features or services within the app, and its use may not be extended for any other purpose (eg, improving other apps or services, advertising, or marketing purposes). You may not use alternative methods (including other permissions, APIs, or third-party sources) to derive data attributed to Call Log or SMS related permissions. Check google documentation for reference - https://play.google.com/about/privacy-security-deception/permissions/#??zippy_activeEl=sms-call-permissions#sms-call-permissions

Answer 2

Based on your comments, your app description on the Play Store is probably not making it clear why you need the Default SMS Handler.

The Default SMS Handler permission/attribute is used by the Android OS to understand whether to ask the user whether they would like to set your app as the default SMS application. From Developer Android resources :

Given the sensitive user information that an app accesses while serving as a default handler, your app cannot become a default handler unless it meets the following Play Store listing and core functionality requirements:

Your app must be able to perform the functionality for which it's a default handler. For example, a default SMS handler should be able to send text messages.

• Your app must provide a privacy policy.

• Your app must make its core functionality clear in the Play Store description. For example, a default Phone handler should describe its phone-related capabilities in the description.

• Your app must declare permissions that are appropriate for its use case. For more details about which permissions you can declare as a given handler, see the guidance on using SMS or call log permission groups in the Play Console Help Center.

• Your app must ask to become a default handler before it requests the permissions associated with being that handler. For example, an app must request to become the default SMS handler before it requests the READ_SMS permission.

Here's what I would do if I were you:

• Add a privacy policy.
• Indicate in your Play Store listing why someone might want your app to be the default SMS app (Will a user be able to read and send messages to others? If so I would suggest mentioning that).
• Add functionality to send SMS as well (I get it that this might not be what you are looking to do from your app, but it seems like Google has increased importance on privacy regarding user SMSes)