I Can 39;t Download Google Play Services On My Android

[Breanne Meisenheimer]

Today, after touching nothing of the project, my gradle yelled at me and wouldn't compile the project. It failed to resolve firebase-iid, firebase-common, play-services-analytics-impl, play-services-auth-api-phone, and play-services-auth-base. So quite a mess after the weekend.

i can 39;t download google play services on my android

DOWNLOAD https://8budimonsi.blogspot.com/?tgs=2x7na6

So I checked the versions of the different APIs, and upgraded the ones that needed upgrading, found out that Google had added a mandatory dependency to firebase-core, added it, then upgraded my google-services plugin, and even added a play-services-base dependency. I also upgraded firebase-messaging to version 17.0.0, and crashlytics to version 2.9.3.

The library com.google.android.gms:play-services-measurement-base is being requested by various other libraries at [[15.0.2,15.0.2], [15.0.4,15.0.4]], but resolves to 15.0.4. Disable the plugin and check your dependencies tree using ./gradlew :app:dependencies.

You will need to update the version of the latter dependency to 15.0.2. This addresses the issue where version 3.3.0 of the Google Services Gradle plugin reports: The library com.google.android.gms:play-services-measurement-base is being requested by various other libraries at [[15.0.0,15.0.0], [15.0.2,15.0.2]], but resolves to 15.0.2...

I tried reverting back to an old build, and it seemed to work, what i found was that the gradle-wrapper.properties was using and older version (4.5) instead of the 4.6 i had in the newer project. Changing this as well as reverting to classpath 'com.android.tools.build:gradle:3.2.0-alpha08' from alpha15 seemed to do the trick. I think you can use the alpha 15 if you like, but to be sure you can use the classpath 'com.android.tools.build:gradle:3.1.2'.Along with all these changes the firebase-core and the google-gms-services should be set to version 16.0.0.

Edit:Make sure that you use emulator with playstore is installed. Check if you have sdk manager -> sdk platforms -> Android 8 -> Google Play ... system image installed. Download it. Create new emulator using that image.

I have an application that uses the Google Maps Android v2 API. I've added the google-play-services_lib library project to my workspace and added a reference to it from my application project, following the instructions on these pages:

I just ran into this problem this morning and seemed very strange since my application was working fine up until today. I was getting the exact same "The Google Play services resources were not found..." message.

If you use any older version or version for Froyo (like me) you should put another value in it. To know what value you should put just open a Google Play services manifest and copy-paste a version_code value. For Froyo services, it is 3265130. After adding this I've stopped getting this error, and I've began to receive coordinates in my application at last.

For me the only working solution was to add the android-support-v7-appcompat library as well. It seems that this library is also needed in order to get rid of that message. Since then my applications have been working fine!

PS. I asked a question, Why does IntelliJ IDEA 13 require both lib project and lib itself (google-play-service) to be added as a dependency?, why is it a must in IntelliJ IDEA 13, and why we cannot import either the library or project only.

I had all lib and resources included as it was working, but still I was getting this error so I removed all references and lib from my project build, updated google service play to revision 10, uninstalled application completely from the device and then again added all resources and libs and ran it and it started working again.

I had the same issue i have created own API to check whether google play service is installed or not , it works fine for me. Just pass package information of google play service it will give you the value

I too had this incredibly cryptic error. It wasn't anything related to location services for me, but with not properly reading the documentation, more precisely step 3, where it says to add the following to your AndroidManifest.xml:

I was using the BaseGameActivity they suggest to use when you want to implement game services so I was a bit surprised it didn't work straight away. I did create a dedicated module for a copy of the google-play-services_lib, I did have the latest version of it (4323000 as of writing) and I did set this as a module dependency to my main module (using Android Studio here). But that little line above fixed everything.

I had the same problem. As Kristopher Johnson said, I referenced google-play-services_lib, but it didn't work. I added google_play_services_lib.jar (look at your SDK/google folder) under project properties/java build path/libraries/android dependencies and error vanished.

W/ResourceType(25122): Requesting resource 0x7f0c000d failed because it is complex

E/GooglePlayServicesUtil(25122): The Google Play services resources were not found. Check your project configuration to ensure that the resources are included.

It seems that the Google Play Services library attempts to read a resource file and has a generic catch-all that displays this error message when the resource fails to load. This corresponds with what kreker managed to decompile from the library and would explain the log messages.

You know, I don't think it's a bug from sdk."The Google Play services resources were not found. Check your project configuration to ensure that the resources are included" is exactly right. The jar file putted into your /libs doesn't contain any resources like *xml, *png etc. The error logs mean this. And If your ever added support libraries like v4, v7-appcompat, v7-cardview, v7-recyclerview, v7-pallete or v7-gridlayout, sometimes logs which imply that resources are in short occur. All these is because that resources in projects are not imported. So, import support projects as library ASAP. Of course, you first download this support projects through SDK Manager at the item of extras

Alternative: GrapheneOS ( GrapheneOS): "The full variant of the Google Maps app is one of the few Google apps largely working without Play services. With the latest advances in the sandboxed Play services compatibility layer, it also works with that installed with more functionality available. Still issues to resolve."nitter.it

In case you missed it you can now install the minimal flavor of the android app that does not require google services. Keep in mind things like location tracking and notifications will not work as those depend on google services. You can grab the APK from the actions tab on the github repo, just select the latest commit and download the minimal version.

By default, the FCM SDK (version 23.0.6 or higher) includes thePOST_NOTIFICATIONSpermission defined in the manifest.However, your app will also need to request the runtime version of thispermission via the constant, android.permission.POST_NOTIFICATIONS.Your app will not be allowed to show notifications untilthe user has granted this permission.

Generally, you should display a UI explaining to the user thefeatures that will be enabled if they grant permissions for theapp to post notifications. This UI should provide the user options toagree or deny, such as OK and No thanksbuttons. If the user selects OK, directly request the permission.If the user selects No thanks, allowthe user to continue without notifications.

Apps that rely on the Play Services SDKshould always check the device for a compatible Google Play services APK beforeaccessing Google Play services features. It is recommended to do this intwo places: in the main activity's onCreate() method, and in itsonResume() method. The check in onCreate() ensures that the appcan't be used without a successful check. The check in onResume() ensuresthat if the user returns to the running app through some other means, such asthrough the back button, the check is still performed.If the device doesn't have a compatible version of Google Play services, your app can callGoogleApiAvailability.makeGooglePlayServicesAvailable()to allow users to download Google Play services from the Play Store.Prevent auto initialization When an FCM registration token is generated, the library uploads the identifier and configuration data to Firebase. If you prefer to prevent token autogeneration, disable Analytics collection and FCM auto initialization (you must disable both) by adding these metadata values to your AndroidManifest.xml:

F-droid can be installed from jolla store or f-droid.org

In f-droid app you can add microg repo from settings>repo>+ or you can download the apk needed from microg webpage that also includes repo information Download - microG Project

Install microg Core, framework Proxy, fakestore, signature spoofing checker, aurora store, from f-droid. You can then use aurora store to install android apps.

The bottom of the screen is a reserved touch zone for system navigation. A line is displayed in the center to show that the navigation bar is present across the entire bottom of the screen. In most apps, this area will display padding. Modern apps are able to tell the OS that they can handle not having the padding to display app content there while still not being able to receive touches from it. Open up the Settings app for an example.

GrapheneOS includes all of the accessibility features from the Android Open Source Project and strives to fill in the gaps from not including Google apps and services. We include our own fork of the open source TalkBack accessibility service along with a Monochromacy option for the standard color correction menu.

GrapheneOS does not yet include a text-to-speech (TTS) service in the base OS due to limitations of the available options. Including one is planned in the future when a suitable option is available. RHVoice and eSpeak NG are both open source and are the most common choices by GrapheneOS users. Both of these work fine but have licensing issues. eSpeak NG has added Direct Boot based on our request for it, meaning it is able to function before the first unlock. RHVoice is missing Direct Boot and can't run before the first unlock. Installing and setting up either one of these or another TTS app will get TalkBack working. TalkBack itself supports Direct Boot and works before the first unlock but it needs to have a TTS app supporting it in order to do more than playing the activation sound before the first unlock. After installing a TTS service, you need to select it in the OS configuration to accept activating it. The OS will display one of them as already selected, but it won't simply work from being installed as that wouldn't be safe. This is the same as the stock OS but it comes with one set up already.

f448fe82f3