Google Play Services SDK Version History

A couple of times, I’ve found it necessary to know what version of google play services I’m dealing with. For example, when I was using a number of Titanium modules that were dependent on google play services, I had version conflicts. But Google Play Services versioning is a nightmare. This article tries to make sense of it all.

UPDATE
It is getting more difficult to keep this up-to-date. As of mid-to-late 2016, Google doesn’t publish blog posts each time they release a new version of google play services, so I can’t pin down the dates like I once was able to. I also can’t seem to find the revision numbers that correspond to the new releases. And the structure of the release file has changed, too, so I can’t just publish the size and checksum of the JAR file.

Google publishes Google Play Services in the Play store with version numbers like 5.0, 6.1, and 6.5. But the versioning used for developers in the Android SDK Manager is completely different: r19, r21, and r22.

To make matters worse, the google_play_services.jar file has no version number at all; there’s nothing I could find inside of the jar file that exposes either version number. So identifying a jar file that somebody bundled with their project is nearly impossible.

I’ve compiled everything I could find about each version: its version numbers (as listed by Google and as displayed in the Android SDK manager), its release date, and the jar file size and MD5 checksum so you can identify your own jar files.

8 thoughts on “Google Play Services SDK Version History

        1. Awesome. I see 9.0, but 9.2 isn’t updated yet. Will you be updating it?
          Also, if I may ask, could you please let me know where you get these zip files from? THANKS

        2. Thanks. R30 and 31 do not include libproject\google-play-services_lib\libs\
          google-play-services.jar I appreciate if you could include them.

          THANKS

Leave a Reply

Your email address will not be published. Required fields are marked *