android – Play Install Referrer Library Adding WRITE_EXTERNAL_STORAGE and READ_EXTERNAL_STORAGE permissions-ThrowExceptions

Exception or error:

We are trying to update Google Play Install Referrer Library and

Internally it’s adding some external read write permissions.

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

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

Do we really need to stick with the permissions ?

dependency implementation '


How to solve:

I’ve also come across this issue.

But in my case, the 1.1 version is also adding the READ_PHONE_STATE permission

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

I’ve decompiled the .aar file for installreferrer:1.1 and checked the manifest and pom file, there is nothing in those files to indicate that these permissions should be added.
The library manifest file only adds this permission (which is always has in previous versions):

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

I haven’t been able to find any official information regarding this.
But other Google libraries have had issues in the past with adding additional, unneeded, permissions, which have then been removed in a hotfix version shortly after.
For example, this:
Why has the READ_PHONE_STATE permission been added?

So i hope the same is gonna happen here.


Install referrer adds this permission due to the fact that the targetSdkVersion is a value lower than the version in which the restriction was added.
If you take a look at generated manifest-merger-report in the build folder of your app, you can see this information:

IMPLIED from android/app/src/main/AndroidManifest.xml:1:1-130:12 reason: has a targetSdkVersion < 4

Information on how this implicit system permission works on Android can be found in this documentation :


From this answer:

This is because they have added a dependency to

Which adds those permissions.

You can find it on the file: manifest-merger-blame-debug-report.txt which is under “yourApp/build/intermediates/manifest_merge_blame_file/debug”

It’s probably a bug. Also, installreferrer 1.1.1 doesn’t solve it.

Easiest solution is to downgrade installreferrer back to 1.0 for now.

But if you need this version, you can add:

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

To disable it.
But know that if you’ll use any API which needs it inside the library, it could lead to a crash, so I won’t recommend doing so.


Quoting from this answer (and completing):

Version 1.1 and 1.1.1 are missing “minSdkVersion”. This would automatically add those permissions (because the default SDK < 4 as said by @thiagolr). See similar issue here: Google Play Services 12.0.1.


Version 1.1.2 solves this issue.


Manifest.xml for v1.0 (from

<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="" package="" >

        android:targetSdkVersion="22" />

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

    <application />


Manifest.xml for v1.1 (from

<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="" package="">

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

    <application />



One could theoretically remove them altogether with the manifest-merger:


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


But if the library will then still work as expected is another story –

it’s rather an exception, that a Google library requires unnecessary permissions.

The release notes and the documentation do not mention permissions.


These permissions are added because has a targetSdkVersion < 4. You can see it on the manifest-merger-release-report.txt file located on Temp\gradleOut\build\outputs\logs folder inside your project. This is a bug and it will probably be fixed on a newer version.

In order to fix this, you need to find out which plugin is adding as dependency.

In my project, the culprit was the Facebook plugin. It uses the package which is responsible for adding the dependency.

The solution was to rollback to, which doesn’t have a dependency.

Edit the file FacebookSDK/Plugins/Editor/Dependencies.xml and change these packages to:

<androidPackage spec="[5,5.13.0)" />
<androidPackage spec="[5,5.13.0)" />
<androidPackage spec="[5,5.13.0)" />
<androidPackage spec="[5,5.13.0)" />

Next, don’t forget to resolve the dependencies again: Assets > Play Services Resolver > Android Resolver > Force Resolve


1.1.2 is released, it adds minSdkVersion correctly.

    android:targetSdkVersion="22" />

Leave a Reply

Your email address will not be published. Required fields are marked *