When installing my android application I see permissions that are not in the manifest

2

I have already checked every line of the manifest well:

<uses-permission android:name="android.permission.INTERNET" />
    <uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
    <uses-permission android:name="com.google.android.providers.gsf.permission.READ_GSERVICES" />
    <uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
    <uses-permission android:name="android.permission.CALL_PHONE" />



    <uses-feature
        android:glEsVersion="0x00020000"
        android:required="true" />

apply plugin: 'com.android.application'

android {
    compileSdkVersion 25
    buildToolsVersion '24.0.3'
    defaultConfig {
        applicationId "disruptiva.com.llegueconductor"
        minSdkVersion 15
        targetSdkVersion 25
        versionCode 31
        versionName '2.1.1'
        multiDexEnabled true
    }
    buildTypes {
        release {
            minifyEnabled false
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
        }
    }
    productFlavors {
    }
}



repositories {
    maven { url "://oss.sonatype.org/content/repositories/snapshots/" }
}
repositories {
    mavenCentral()
}

dependencies {
    compile fileTree(include: ['*.jar'], dir: 'libs')
    testCompile 'junit:junit:4.12'
    compile files('libs/http-core-4.1.jar')
    compile 'com.android.support:design:25.0.0'
    compile 'com.android.support:appcompat-v7:25.0.0'
    compile 'com.android.support:support-v4:25.0.0'
    compile 'de.hdodenhof:circleimageview:1.3.0'
    compile 'com.google.android.gms:play-services:8.1.0'
    compile 'com.mcxiaoke.volley:library:1.0.19'
    compile 'com.loopj.android:android-async-http:1.4.8'
    compile 'com.android.support:cardview-v7:25.0.0'
    compile 'com.google.code.gson:gson:2.7'
    compile 'com.android.support:recyclerview-v7:25.0.0'
    compile 'com.github.castorflex.smoothprogressbar:library-circular:1.0.1'
    compile 'com.github.clans:fab:1.6.4'
    compile 'com.afollestad.material-dialogs:core:0.9.0.2'
    compile 'com.balysv:material-ripple:1.0.2'
    compile 'com.github.clans:fab:1.6.4'
}

And I have these permissions in the application:

    
asked by Jheancarlos Piñeros 06.12.2016 в 17:35
source

4 answers

1

The problem is that the libraries you used have some permissions on their manifest then when the application is compiled a single manifest of all is generated with the new merged Manifest of android studio I could solve it by adding this to the manifest for each one I want remove

<uses-permission
    android:name="android.permission.GET_ACCOUNTS"
    tools:node="remove" />
    
answered by 21.12.2016 в 19:42
0

1) android.permission.CALL_PHONE

It allows you to make phone calls (that's why you have the contacts) without the need to go through the user interface. (Degree of complexity DANGEROUS)

2) android.permission.ACCESS_FINE_LOCATION

Allows an application to access an accurate location.

3) com.google.android.providers.gsf.permission.RE‌​AD_GSERVICES

This permission is VERY VERY VERY little documented, in fact the Android permissions list does not appear. It is very likely that this permission will show some that you are not explicitly leaving in your manifesto.

    
answered by 06.12.2016 в 21:26
0

The permissions that appear in your image appear in your application if they are defined in your AndroidManifest.xml , in order:

1)

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

2)

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

3)

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

4)

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

The ones that I do not see in your AndroidManifest.xml are READ_CONTACTS and WRITE_EXTERNAL_STORAGE , it's a bit weird they do not show, they are 2 causes, the permission can be defined in another part of the AndroidManifest.xml or you are seeing a version of the application that was generated with the permissions.

    
answered by 06.12.2016 в 22:31
0

Investigating a little SO the cause it can be the version of the google play services 8 that adds the permission of WRITE_EXTERNAL_STORAGE

If you update the new version 10 of the google play services, your permissions.

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

The new version does not need com.google.android.providers.gsf.permission.READ_GSERVICES

    
answered by 14.12.2016 в 10:04