Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Flutter and app store releases

The emulator says Google Play services must be updated

ErrorThis app won't run unless you update Google Play services

Short answer

The app needs Google Play services, and the emulator image either lacks it or has an old copy. Create an AVD with a Google Play or Google APIs system image on API 24 or higher, then update Play services from the emulator's Extended controls, Google Play tab.

  • Applies to Android Studio, Android Emulator, API 34 system image
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Check which system image the AVD uses. In Device Manager the image name shows Google APIs or Google Play; images without either have no Play services.

    avdmanager list avd
  2. 2Match what you see, then jump to its fix

    1. 1The system image name has neither Google APIs nor Google PlayThe AVD's system image has no Google Play servicesFix
    2. 2The image has Play services but the app still asks for an updateThe emulator's Play services is out of dateFix
    3. 3The app crashes or shows its own message on a device without Play servicesYour app does not check for Play services before using itFix

What does the error look like?

  • This app won't run unless you update Google Play services
  • App starts on a Google Play image but not on a plain AOSP image

Cause 1 of 3

The AVD's system image has no Google Play services

1Check

A system image labelled Google APIs includes access to Google Play services; a plain AOSP image does not.

avdmanager list target

2Fix

Create a new AVD from a profile with the Play Store logo, or a Google APIs system image, at API 24 or higher.

avdmanager create avd -n play34 -k "system-images;android-34;google_apis;x86_64"

3Verify

Launch the AVD and run the app.

# Start play34 from Device Manager and run the app

Confirmed by developer.android.com

Did this fix it?

Cause 2 of 3

The emulator's Play services is out of date

1Check

A device definition with the Play Store logo has a Google Play tab in Extended controls with a button to update Google Play services.

# Emulator toolbar > ... (Extended controls) > Google Play

2Fix

Click the update button in that tab, and sign in with a Google account if asked.

# Extended controls > Google Play > Update

3Verify

Run the app again; the update message is gone.

# App starts without the error

Confirmed by developer.android.com

Did this fix it?

Cause 3 of 3

Your app does not check for Play services before using it

1Check

Devices without the Play Store do not have Google Play services, so apps should check first.

val code = GoogleApiAvailability.getInstance().isGooglePlayServicesAvailable(this)
Log.d("GMS", "result=$code (0 = SUCCESS)")

2Fix

Call isGooglePlayServicesAvailable() before Google APIs, and keep the Play services dependency versions current in build.gradle.

if (code != ConnectionResult.SUCCESS) {
    GoogleApiAvailability.getInstance().getErrorDialog(this, code, 9000)?.show()
}

3Verify

On a device without services the user sees the dialog instead of a crash.

# Dialog or normal start

Confirmed by developers.google.com

Did this fix it?

How do I stop it coming back?

  • Use Google Play system images for AVDs that run Maps, sign-in or other Google APIs.
  • Test on API 24 or higher; Google's guide lists that as the minimum for Play services testing.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Projects of mine built on the same technologies:

Related fixes

Mobile apps

Android Studio cannot pair the phone over Wi-Fi

The Pair devices over Wi-Fi dialog lists no device

Wireless pairing needs the phone on Android 11 or higher and on the same Wi-Fi network as the computer, with current Platform-Tools.

4 causes, each with a fix

Mobile apps

adb tcpip 5555 fails because no device is found

adb: more than one device/emulator

adb tcpip only works while the device is attached and listed by adb, because it tells the phone to start listening on port 5555.

4 causes, each with a fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.