This App Won't Run Unless You Update Google Play Services (Via Bazaar)

This app won't run unless you update Google Play Services (via Bazaar)

According to a discussion with Android Developers on Google+, running the new Map API on the emulator is not possible at the moment.

(The comment is from Zhelyazko Atanasov yesterday at 23:18, I don't know how to link directly to it)

Also, you don't see the "(via Bazaar)" part when running from an actual device, and the update button open the Play Store. I am assuming Bazaar is meant to provide Google Play Services on the Android emulator, but it is not ready yet...

This app won't run unless you update Google Play services error

In the Android SDK Manager, you must install "Google APIs (x86 System Image)" under "Android 4.4.2 (API 19)". Quit Eclipse and restart it.

Then create a new android virtual device in AVD manager and choose "Google APIs x86 (Google Inc.) - API Level 19" as target. Check "Use Host GPU" to ensure the drawing of the map will be accelerated.

That's it, this new emulator will have Play Services preinstalled and it will run faster because it's a x86 image.

This app won't run until you update Google Play Services GameBaseUtils

I've solved the issue requiring version 5.0.+ of the Google Play Services. For that, I changed both the file build.gradle, both in my app module and in the BaseGameUtils module, from:

compile 'com.google.android.gms:play-services:+'

to

compile 'com.google.android.gms:play-services:5.0.+'

These questions mention the same issue:

Google Play Services version 5.2.08 too recent for my device

After update - crash com.google.android.gms:play-services:5.2.8

This app won't run unless you update Google Play Services when app is installed on real device

This android developer's blog entry describes what's new in the version 7.0 of Google Play services.

If you don't need those you're good to go with version 6.5 which already uses new GoogleApiClient class and provides granular dependency modules (best described here and here.

In one of my projects i use this

compile 'com.google.android.gms:play-services:6.5.87'

It's the whole package and I'll pick only the modules I need before deployment. Works fine against target API 22.

The farthest version I'd go with would be

compile 'com.google.android.gms:play-services:6.1.71'

This one introduced the unified GoogleApiClient approach used today.

So should I use an older SDK?

Absolutely not, this is not an SDK related problem. Keep everything (build tools, compile SDK, target SDK) to 22.

is there a better way to handle this than asking my users to update their Google Play Services?

See above, use older version of the library with your project.

AndroidStudio emulator won't run unless you update Google Play Services

I downgraded the SDK from 5.1 to 5.0 and it's working.

---

Related Topics