Why I getting "SMS and CALL_LOG permissions warning"

Question

I have so many permission in my app but I dont have any call_log permission but Im getting this warning from play console . Is this common warning or this permissions below have hidden call_log permission.

 <uses-permission android:name="android.permission.INTERNET" />
        <uses-permission android:name="android.permission.WAKE_LOCK" />
        <uses-permission android:name="android.permission.CALL_PHONE" />
        <uses-permission android:name="android.permission.READ_PHONE_STATE" />
        <uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
        <uses-permission android:name="android.permission.READ_CONTACTS" />
        <uses-permission android:name="android.permission.WRITE_CONTACTS" />
        <uses-permission android:name="android.permission.BLUETOOTH" />
        <uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" />
        <uses-permission android:name="android.permission.CAMERA" />
        <uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE" />
        <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
        <uses-permission android:name="android.permission.ACCESS_WIFI_STATE" />
        <uses-permission android:name="android.permission.CHANGE_WIFI_STATE" />
        <uses-permission android:name="android.permission.CHANGE_NETWORK_STATE" />
        <uses-permission android:name="android.permission.CHANGE_WIFI_MULTICAST_STATE" />
        <uses-permission android:name="android.permission.AUTHENTICATE_ACCOUNTS" />
        <uses-permission android:name="android.permission.GET_ACCOUNTS" />
        <uses-permission android:name="android.permission.MANAGE_ACCOUNTS" />
        <uses-permission android:name="android.permission.VIBRATE" />
        <uses-permission android:name="android.permission.MODIFY_AUDIO_SETTINGS" />
        <uses-permission android:name="android.permission.RECORD_AUDIO" />

        <uses-permission android:name="android.permission.WRITE_SETTINGS"
            tools:ignore="ProtectedPermissions" />
        <uses-permission android:name="android.permission.READ_SYNC_STATS" />
        <uses-permission android:name="android.permission.READ_SYNC_SETTINGS" />
        <uses-permission android:name="android.permission.WRITE_SYNC_SETTINGS" />
        <uses-permission android:name="android.permission.BROADCAST_STICKY" />
        <uses-permission android:name="android.permission.READ_LOGS"
            tools:ignore="ProtectedPermissions" />
        <uses-permission android:name="android.permission.SYSTEM_ALERT_WINDOW" />
        <uses-permission android:name="android.permission.READ_PROFILE" />
        <uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
    <uses-permission android:name="android.permission.SEND_SMS" />

Answer 1

You have

uses-permission android:name="android.permission.SEND_SMS"

which comes under sms

Google Play may provide a temporary exception to apps that aren't Default SMS, Phone, or Assistant handlers when:

1. Use of the permission provides core app functionality to users

2. There is currently no alternative method to provide the core functionality

you must fill this form and google must approve it

you can find more info here

EDIT

For any one who is still getting this error after removing the permissions . Try deleting all previous APK from your account (from alpha,beta, internal testing if any)

Answer 2

Please see the following instructions to submit the declaration form:

A1. Go to the Console > App release > Click ‘Create a release’ > Upload a new APK that you want to release A2. Retain the current version of APK A3. Click ‘Add from library’ > Upload all active APKs to cover all permissions across the tracks in your app

You can find active APK in Release management > Artifact library

A4. Fill out the Permissions Declaration Form for extension ‘Compliance status’ > check “No, this release does not meet the SMS and Call log” ‘Declarations’ > check all A5. Click "Save" at the bottom of the page

After that, please stay on the same page and follow the next steps:

B1. Deactivate and remove ONLY the old APKs which you do not want to release. B2. Click "Save" again then select "Review" B3. Then, you'll be able to release a new version of APK by clicking "Start Roll Out" button.

After finished all the steps, if your APK does NOT have sensitive or high-risk permissions anymore, please skip the steps below(C1~4) and no additional action is required. However, if you uploaded the new APK with sensitive or high-risk permissions, please note that your app will be removed after Mar 9, 2019.

If your new APK has sensitive or high-risk permissions & you want to utilize the permission after Mar 9, you need to finish the additional step to submit the declaration form to enable further review.

C1. After the new APK release(Step B1~3), please go to the Console > App release > Click ‘Create a release’

C2. Click ‘Add from library’ > Select the APK(which will be utilized after Mar.9) C3. Retain newly updated APK in step B3 C4. Fill out Permissions Declaration Form (not for extension),

‘Compliance status’ > check “Yes, this release meets the SMS and Call log”

Choose core functionalities as well

C5. Submit the form by Clicking “Save” at the bottom of the page

Also, to make sure your app be safe after Mar 9, please do not forget to update all the APKs(with sensitive or high-risk permission) in other track with the same steps.