CODEWITHSUNDEEP
androidapkandroid-permissions
casolorz
casolorz

Reputation: 9604

My apk asks for permissions that I am not asking for on my AndroidManifest.xml

I just noticed that my app is requesting new permissions all of the sudden. 

./aapt d permissions MyApk.apk 
package: mypackage
uses-permission: android.permission.INTERNET
uses-permission: android.permission.ACCESS_WIFI_STATE
uses-permission: android.permission.CHANGE_WIFI_MULTICAST_STATE
uses-permission: android.permission.ACCESS_NETWORK_STATE
uses-permission: com.android.vending.BILLING
uses-permission: android.permission.WRITE_EXTERNAL_STORAGE
uses-permission: com.android.launcher.permission.INSTALL_SHORTCUT
uses-permission: android.permission.GET_ACCOUNTS
uses-permission: android.permission.USE_CREDENTIALS
uses-permission: android.permission.ACCESS_COARSE_LOCATION
uses-permission: android.permission.READ_EXTERNAL_STORAGE

I believe these 3 are things I'm not requesting:

  uses-permission: android.permission.GET_ACCOUNTS
  uses-permission: android.permission.USE_CREDENTIALS
  uses-permission: android.permission.ACCESS_COARSE_LOCATION

These are the only permissions on my AndroidManifest.xml

 <uses-permission android:name="android.permission.INTERNET" />
    <uses-permission android:name="android.permission.ACCESS_WIFI_STATE" />
    <uses-permission android:name="android.permission.CHANGE_WIFI_MULTICAST_STATE" />
    <uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
    <uses-permission android:name="com.android.vending.BILLING" />
    <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"></uses-permission>
    <uses-permission android:name="com.android.launcher.permission.INSTALL_SHORTCUT" />

This is an app I've been releasing new versions for at least once a month for well over a year, this is the first time this has happened.

I recently switched to using MoPub but I didn't change my permissions, plus I released that version over a month ago. The most recent thing I did was add the ChartBoost jar file but that is just a jar file.

Any ideas?

Thanks.

Upvotes: 3

Views: 377

Answers (1)

casolorz
casolorz

Reputation: 9604

All of my Google Play Services dependencies were 7+ and 7.5 just came out last week so it must be requiring the new permissions because when I changed them to 7.3 it all started working like normal again.

After the 7.3 change:

uses-permission: android.permission.INTERNET
uses-permission: android.permission.ACCESS_WIFI_STATE
uses-permission: android.permission.CHANGE_WIFI_MULTICAST_STATE
uses-permission: android.permission.ACCESS_NETWORK_STATE
uses-permission: com.android.vending.BILLING
uses-permission: android.permission.WRITE_EXTERNAL_STORAGE
uses-permission: com.android.launcher.permission.INSTALL_SHORTCUT

This is the change I made:

compile 'com.google.android.gms:play-services-ads:7+'

To:

compile 'com.google.android.gms:play-services-ads:7.3+'

I did it to all my Google Play Services dependencies so I don't know if ads is the only one requiring that or if it is all of them.

EDIT: From my testing, as soon as you add compile 'com.google.android.gms:play-services-wallet:7.5+' to a clean project, it will start requiring those new permissions.

Upvotes: 3

Related Questions