Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Wrong permissions at Google Play

Permissions at my app's Google Play page are wrong. Here is my Manifest (just the permissions)

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

Here is the full file AndroidManifest.xml

There is nothing more. Now please take a look at the list below my app description at Google Play. It's obviously wrong.

permissions by Google Play

I tried do contact Google Play support but they told me nothing.

At this time, we’re unable to provide technical support for app development-related questions. We’re happy to help with any questions related to publishing apps and managing your apps using the Google Play Developer Console (http://play.google.com/apps/publish).

So now i don't have a clue what to do to make the list right. Did anyone have a similar problem? Every time during app update Google Play tells me that new permissions are required. But a device can see the permissions correctly. They are declared correctly at Manifest. What should I do?

like image 896
koras Avatar asked Sep 28 '22 12:09

koras


People also ask

How do I remove permissions from Google Play Services?

Go to Settings > Applications > All > Google Play Services > Tap Disable > Tap OK to confirm. Method 2. If you find the Disable checkbox is grayed out, please Go to Settings > Security > Device administrators > Disable Android Device Manager.

Does Google Play need all permissions?

Google Play services automatically obtains all permissions it needs to support its APIs. However, your app should still check and request runtime permissions as necessary and appropriately handle errors in cases where a user has denied Google Play services a permission required for an API your app uses.


1 Answers

I found out what's wrong.

getSharedPreferences(getApplicationContext().getPackageName() + "_preferences", Context.MODE_MULTI_PROCESS);

Android Studio adds access to files because I'm using multi process shared preferences and I'm writing to them somewhere (available since API 11).

Force removing the permission by

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

in the app's Manifest breaks writing to Shared Prefs. So it's really needed and auto-added by Android Studio.

The second one, READ_PHONE_STATE is because of the saxrssreader library. When the library's min SDK is lower than the app's min SDK, the permission is added during build. I simply changed the library's minimum SDK to the number my app is using and the permission is gone.

That was a tricky one but everything is clear now.

like image 195
koras Avatar answered Oct 13 '22 03:10

koras