write_external_storage - signature permission android

Warnings Your Apk Is Using Permissions That Require A Privacy Policy:(android.permission.READ_PHONE_STATE) (12)

  1. Probably you're using PlayServices of version 9.6.0. Then you should update it, it's library's bug. More info here .


  1. Add

    <uses-permission android:name="android.permission.READ_PHONE_STATE" tools:node="remove" />

to your manifest file.

In manifest not added android.permission.READ_PHONE_STATE. permission.

Why error comes when I upload new apk version error come below.

Your app has an apk with version code 1 that requests the following permission(s): android.permission.READ_PHONE_STATE. Apps using these permissions in an APK are required to have a privacy policy set.

I have attached screen shot my google play store account.

my manifest file.

<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"

    <uses-permission android:name="android.permission.INTERNET" />

                <action android:name="android.intent.action.MAIN" />

                <category android:name="android.intent.category.LAUNCHER" />

            android:screenOrientation="portrait" />

            android:screenOrientation="portrait" />
            android:screenOrientation="portrait" />



1.You need to create privacy policy page on your website and update your privacy policy for the permissions you are asking.

2.Update new SDK remove unwanted permissions and resubmit the app.

Currently some people are facing the same issue because of using 12.0.0 version of AdMob lib.

Update it to 12.0.1 . This should fix it. You can read more here

If you're testing your app on a device > android 6.0 you have also to explicitely ask the user to grant the permission.

As you can see here READ_PHONE_STATE have a dangerous level.

If a permission have a dangerous level then the user have to accept or not this permission manually. You don't have the choice, you MUST do this

To do this from your activity execute the following code :

if the user use Android M and didn't grant the permission yet it will ask for it.

public static final int READ_PHONE_STATE_PERMISSION = 100;

  if (Build.VERSION.SDK_INT > Build.VERSION_CODES.M && checkSelfPermission(Manifest.permission.READ_PHONE_STATE)
                != PackageManager.PERMISSION_GRANTED) {
            requestPermissions(new String[]{Manifest.permission.READ_PHONE_STATE}, READ_PHONE_STATE_PERMISSION);

then override onRequestPermissionsResult in your activity

    public void onRequestPermissionsResult(int requestCode, @NonNull String[] permissions, @NonNull int[] grantResults) {
        switch (requestCode){
                if (grantResults[0] == PackageManager.PERMISSION_GRANTED){
                    //Permission granted do what you want from this point
                }else {
                    //Permission denied, manage this usecase

You should read this article to know more about it

It's third party library. You can find the culprit in build/outputs/logs/manifest-merger-release-report.txt

Just try to add this line to your manifest file:

<uses-permission android:name="android.permission.READ_PHONE_STATE" tools:node="remove" />

and add attribute xmlns:tools="http://schemas.android.com/tools" to your <manifest> tag to define namespace tools

From the documentation for tools:node="remove" :

Remove this element from the merged manifest. Although it seems like you should instead just delete this element, using this is necessary when you discover an element in your merged manifest that you don't need, and it was provided by a lower-priority manifest file that's out of your control (such as an imported library).

The dependencies you have in your project, will add their own permissions. Please do the below to find from where "READ_PHONE_STATE" is coming.

  1. Rebuild your android application
  2. Press "Ctrl+Shift+F" in android studio (basically do a search all in the editor of your preference).
  3. Search for "READ_PHONE_STATE", you would find the entry in a regenerated manifest file (not the one you originally created). By the path of it you can know, from which dependency the permission is getting added.

You should drop android.permission.READ_PHONE_STATE permission. Add this to your manifest file:

    tools:node="remove" />

you need to specify the min and target sdk version in the manifest file.
If not the android.permission.READ_PHONE_STATE will be added automaticly while exporting your apk file.

        android:targetSdkVersion="19" />

2018 update:

For AdMob users, this causes AdMob version 12.0.0 (currently last version). It wrongly requests READ_PHONE_STATE permission, so even if your app doesn't require READ_PHONE_STATE permission in manifest, you won't be able to update your app in the Google Play Console (it will tell you to create a privacy policy page for your app, because your app requires this permission).

See this: https://developers.google.com/android/guides/releases#march_20_2018_-_version_1200

Also, they wrote they will publish an update to 12.0.1 fixing this soon.