17

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.

amrit kumar Saini
  • 171
  • 1
  • 1
  • 4

7 Answers7

11

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

virtual device with the message

possible solution

Christos Lytras
  • 36,310
  • 4
  • 80
  • 113
MarkT
  • 378
  • 2
  • 7
6
  1. On your Android phone, go to Settings.
  2. Click on Apps.
  3. Click Google Play services.
  4. Click on Permissions.
  5. Ensure all permission settings are turned on.
Linda Lawton - DaImTo
  • 106,405
  • 32
  • 180
  • 449
  • Even that didn't help, one interesting thing i noticed is that when i install the local debug build its working fine but same device is not working with play store build. – amrit kumar Saini Feb 05 '18 at 06:29
  • After further investigation we found out that this issue happens when we use Prod cert to sign the apk(only on 4.4.X os version). Its working fine with debug and android studio cert signed apk. Any recommended steps to fix this issue? – amrit kumar Saini Feb 07 '18 at 04:25
2

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.

Wim Fikkert
  • 106
  • 5
1

Make sure your Google Play Services is updated

royherma
  • 4,095
  • 1
  • 31
  • 42
1

For me worked: Settings > Apps and Notifications > Google Play Store > Permissions > All ON

Maurici Abad
  • 1,012
  • 9
  • 20
0

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.

wsgeorge
  • 1,928
  • 17
  • 20
0

Opening google maps once and the trying my map fixed the problem

Shreya B
  • 305
  • 2
  • 14