We have an android app on Play Store for last 2 years. We are trying to connect the Google Drive API using play services inside the app.
Things are working fine for all the android OS except 4.4.X. In 4.4.X OS devices while trying to login to the Google Account most of the users are getting the error (as reported by them) like :
" is having trouble with Google Play services.Please try again."
Does anyone know how to fix this issue?. This is Not reproducing on all 4.4.X devices.
If you are having troubles with your virtual devices when running things like Google maps etc.; try creating a new virtual device with Google Play Store incorporated
On your Android phone, go to Settings.
Click on Apps.
Click Google Play services.
Click on Permissions.
Ensure all permission settings are turned on.
I've had the same issue as reported above after updating my app dependencies from com.google.android.gms:play-services-maps:15.0.1 to ..:16.1.0 (or ..:17.0.0). The problem for was that the installed version of Google Play Services on my device (a Zebra TC51 running Android 6.0.1 in this case) is rather old and is managed by our customer using a mobile device management solution (MDM) that is very conservative. Rolling back to ..:15.0.1 or updating Google Play Services to the latest version would both solve this issue for me. Sadly, I cannot force our customers to update Google Play Services (although I'd like them to update obviously).
Reproducing this is straightforward by just installing an older Google Play Services (download the July 2018 version for example, v12.8.74. Set your dependency to 16.0.1 or newer and you'll get the above error message.
I haven't been able to find an overview that lists the compatibility between versions of the installed Google Play Services APK and which versions of the com.google.android.gms:play-services-maps dependency are supported.
Also, have a look at the Overview of Google Play Services where it is explained how the included dependency (in your app) and the installed client library (on the device) depend on one another.
Make sure your Google Play Services is updated
For me worked: Settings > Apps and Notifications > Google Play Store > Permissions > All ON
I fixed this by following the instructions on setting up Firebase on a new project. I encountered the "Try again" prompt until I added firebase-core to the project.
Opening google maps once and the trying my map fixed the problem
I'm trying to run Google Play Services on my Android emulator using Genymotion. I followed the steps in another Stack Overflow to download and install ARM Translation Installer and the Google Apps for my Android version (5.1.0). Up until this point, there doesn't seem to be any issues.
The issue occurs when I open my development app and try to connect to Google Play Services. I see Google Play services out of date. Requires 10084000 but found 8118436.
I know that this means the version of my emulator is 8.1 and the version that is being bundled is 10.0. However, I don't know how to make these two versions the same. I can't figure out how to either downgrade one, or update the other. Does anyone know how to fix this problem? Thanks in advance!
I figured out this issue. For those having the same problem, you need to download the correct APK. Go here to find it: http://www.apkmirror.com/apk/google-inc/google-play-services/
Please help me, I am a beginner in android
When running my android application about geolocalisation the emulator shows me "app-name will not run unless you update google play services" I tried to install the packages but no difference the problem persists.
I installed Google play store on my android emulator successfully. But when I try to run Google app it gives "Unfortunately, Google services framework has stopped" error message. I tried to fix it using clear cache of Google play store app, clear data of Google services framework app and restart the device. Also I tried for new emulators. But It didn't work. Does it a matter version of android sdk and Google Services Framework.apk version?
Suggest a way to fix this problem.
Read up on the guide provided by Android here.
Specifically, note:
To test your app when using the Google Play services SDK, you must use
either:
A compatible Android device that runs Android 2.3 or higher and
includes Google Play Store.
The Android emulator with an AVD that runs
the Google APIs platform based on Android 4.2.2 or higher.
As long as you satisfy those requirements, follow the installation instructions provided to install the SDK into your Developer environment.
I recently started developing for Android, and I have come into trouble when trying to use Google Maps in my app. I downloaded the Google Maps API v2 for Android, and have already performed all the required steps according to Google Developers Site.
My problem is that although the app runs, in the place where the maps should be displayed there is a texts saying that my device is missing Google Play Services.
I have already downloaded the Google Play Services from the SDK, imported the library into my project and also importing the .JAR file.
I am using Netbeans, not Eclipse, so many solutions I have found over the web aren`t useful for me. I hope you can help me with this.
Unfortunately, you can't use the emulator to run apps that use Google Play services. From http://developer.android.com/google/play-services/setup.html: "Google Play services is not supported on the Android emulator — to develop using the APIs, you need to provide a development device such as an Android phone or tablet."
From google's own site http://developer.android.com/google/play-services/setup.html
If you want to test your app on the emulator, expand the directory for
Android 4.2.2 (API 17) or a higher version, select Google APIs, and
install it. Then create a new AVD with Google APIs as the platform
target. Note: Only Android 4.2.2 and higher versions of the Google
APIs platform include Google Play services.
I had this same problem and found solution:
Here are the updated gms and vending files. Same instructions as before: Create a new emulator with any cpu/abi, a non google-api target (versions 10-17 work) and gpu emulation on or off, and then install the files:
adb install com.android.vending-20130716.apk
adb install com.google.android.gms-20130716.apk
If you are upgrading an existing emulator then you might need to uninstall previous versions by:
adb uninstall com.android.vending
adb uninstall com.google.android.gms
Bellow link contains a solution that works with Android 4.2.2 or higher
How to install Google Play Services in Android Emulator
1.1 Start your emulator. Disconnect any other Android device (such as your smartphone) from computer.
1.2 Download these two files
com.android.vending-19032013.apk : http://www.mediafire.com/download.php?7jfar2v1bzx6v59
com.google.android.gms-19032013.apk : http://www.mediafire.com/download.php?4o9fz413uavlblf
1.3 Open command console, go to \platform-tools
Install two files above with command
adb install \com.android.vending-19032013.apk
adb install \com.google.android.gms-19032013.apk
Yes, you can use Google maps on emulator. However, it's not officially supported, so takes some work. I had the best success following the info on this link.
I found this, i hope it helps you ;)
Installing Google Play on Android Emulator
Run Google Play Services in your emulator
If anyone is still experiencing this issue, first try to create your emulator with the Google API's as the platform target. After doing so, I noticed that my Google Play Services was not the correct version on the emulator.
While trying to hack together a solution, I stumbled upon the GoogleApiAvailability class here. Google did a phenomenal job handling compatibility issues.
GoogleApiAvailability.isGooglePlayServicesAvailable(Context) returns an integer status code, which can be fed directly into getErrorDialog(Activity, errorCode, requestCode) which returns a Dialog that works perfectly right out of the box. If your Play Services are out of date, the dialog will redirect you to an updater... If they are missing, it will redirect you to an installer, etc...
Thought I would share this great feature in case anyone is looking for a fix that would work in production code as well as testing.