SecurityException Permission Denial: opening provider com.google.android.gms.phenotype.provider.ConfigurationProvider [closed]
I had the same issue what helped me was that I had wrong credentials in my google-services.json file and after getting a new file my problem was fixed. in the process of resolving this issue I also updated my google play services but I do not think this is necessary .
You just need to include this in your build.gradle file: implementation “com.google.android.gms:play-services-location:15.0.1” or if you’re not using latest gradle version: compile “com.google.android.gms:play-services-location:15.0.1” Note: It’s recommended to use Google Play services version 15.0.1 or higher, which includes bug fixes for this class. More details here. https://developers.google.com/android/reference/com/google/android/gms/location/FusedLocationProviderClient
It is probably that your library is not linked to project properly or that you have older google-play-services library version so conflict appears and Eclipse got stupid.. :S No you don’t need to add anything in integers.xml. When you link properly Google-play-services library to your project reference android:value=”@integer/google_play_services_version” will be found and you are ready … Read more
Do I also need the ACCESS_COARSE_LOCATION permission? No. What’s the use case where I need the coarse location? If you do not ask for ACCESS_FINE_LOCATION, but you need location data, and you are willing for that data to be fuzzy (say, up to around a city block from the user’s position). In the case of … Read more
All those answers are wrong, since the release of gradle plugin v0.4.2 the setup of google play services under android studio is straight forward. You don’t need to import any jar or add any project library nor add any new module under android studio. What you have to do is to add the correct dependencies … Read more
I found simple solution: int v = getPackageManager().getPackageInfo(GoogleApiAvailability.GOOGLE_PLAY_SERVICES_PACKAGE, 0 ).versionCode; But versionCode is deprecated in API 28, so you can use PackageInfoCompat: long v = PackageInfoCompat.getLongVersionCode(getPackageManager().getPackageInfo(GoogleApiAvailability.GOOGLE_PLAY_SERVICES_PACKAGE, 0 ));
Sorry, thats a bug! It’s just spurious logging though: Google Play services does some checking to see whether you are a Google app or a regular third party one. As part of that, it calls the signature verifier and the logging ended up more verbose than intended – it will be fixed in a future … Read more
Check out Setting Up Google Play Services which says: To develop an app using the Google Play services APIs, you need to set up your project with the Google Play services SDK. If you haven’t installed the Google Play services SDK yet, go get it now by following the guide to Adding SDK Packages. To … Read more
This was found to fix the problem. Update your classpath in project level gradle com.google.gms:google-services:2.1.0 to classpath com.google.gms:google-services:3.0.0