-1

My app was using SMS permissions for certain features in the app. We submitted multiple appeals to the Google Team, but our app kept getting rejected for the past couple of months. In order to meet the 09th March 2019 deadline set by Google Play team, we removed all SMS related permissions from Android Manifest as well as removed all SMS related code from the app and submitted an apk to Google Play. Now this apk is also rejected. Is anyone facing this issue and how to solve this?

Rejection reason sighted by Google: We reviewed your app and found that it does not qualify for use of the requested permissions for the following reasons:

The declared functionality Device Automation, Physical safety / emergency alerts to send SMS is determined to be unnecessary or not aligned with the core functionality of your app.

P.S. While submitting the update, we had selected the following options in the permissions declaration form:

Compliance status: Yes, this release meets the SMS and Call Log permissions policy

Core functionality: Device Automation, Physical safety / emergency alert apps (e.g., senior safety)

Community
  • 1
  • 1
sagarpdesai
  • 193
  • 1
  • 13
  • 1
    Have you double checked your merged manifest to set of they are any remaining permissions or features. I had a library I liked that had a permission and features declared that I didn't use but still showed in the manifest. – Ge3ng Mar 13 '19 at 02:08
  • Perfect! It was indeed one of the libraries that was causing this issue. – sagarpdesai Mar 14 '19 at 11:18

1 Answers1

0

There was a library that was using one the SMS permissions. Merge Manifest helped resolve the issue. For details on merge manifest check this link:

What is the Merged Manifest in Android?

sagarpdesai
  • 193
  • 1
  • 13