32 ratings
  • 1
  • 2
  • 3
  • 4
  • 5
5 star 6
4 star 8
3 star 9
2 star 3
1 star 6
Compatible with
  • Android

Google Play Services 22.0.0.0

Xamarin Inc.

Give your apps more features to attract users on a wider range of devices.

With Google Play services, your app can take advantage of the latest, Google-powered features such as Maps, Google+, and more, with automatic platform updates distributed as an APK through the Google Play store. This makes it faster for your users to receive updates and easier for you to integrate the newest that Google has to offer.

This component is only for Xamarin.Android applications that target Android 4.0 (API level 14) and higher.

Google Technology

  • Google Play services provides you with easy access to Google services and is tightly integrated with the Android OS. Easy-to-use client libraries are provided for each service that let you implement the functionality you want easier and faster.

Standard Authorization

  • All products in Google Play services share a common authorization API that leverages the existing Google accounts on the device. You and your users have a consistent and safe way to grant and receive OAuth2 access tokens to Google services.

Automatic Updates

  • Devices running Android 2.23and newer and that have the Google Play Store app automatically receive updates to Google Play services. Enhance your app with the most recent version of Google Play services without worrying about your users' Android version.

Showing a Map

This snippet shows how easy is to add a Map fragment to you app. Additional setup is required please see GettingStarted for more information.

MainActivity.cs

using Android.Gms.Maps;
// ...

protected override void OnCreate (Bundle bundle)
{
    base.OnCreate (bundle);

    // add map fragment to frame layout
    var mapFragment = new MapFragment ();
    FragmentTransaction fragmentTx = this.FragmentManager.BeginTransaction();
    fragmentTx.Add (Resource.Id.linearLayout1, mapFragment);
    fragmentTx.Commit ();

    // Set our view from the "main" layout resource
    SetContentView (Resource.Layout.Main);
}

How It Works

The Google Play services client library

The client library contains the interfaces to the individual Google services and allows you to obtain authorization from users to gain access to these services with their credentials. It also contains APIs that allow you to resolve any issues at runtime, such as a missing, disabled, or out-of-date Google Play services APK. The client library has a light footprint, so it won't have an adverse impact on your app's file size.

If you want to access added features or products, you can upgrade to a new version of the client library as they are released. However, upgrading is not necessary if you don't care about new features or bug fixes. We anticipate more Google services to be continuously added, so be on the lookout for these updates.

The Google Play services APK

The Google Play services APK contains the individual Google services and runs as a background service in the Android OS. You interact with the background service through the client library and the service carries out the actions on your behalf. An easy-to-use authorization flow is also provided to gain access to the each Google service, which provides consistency for both you and your users.

The Google Play services APK is delivered through the Google Play Store, so updates to the services are not dependent on carrier or OEM system image updates. In general, devices running Android 2.2 (Froyo) or later and have the Google Play Store app installed receive updates within a few days. This allows you to use the newest APIs in Google Play services and reach most of the devices in the Android ecosystem (devices older than Android 2.2 or devices without the Google Play Store app are not supported).

The Google Play services APK on user devices receives regular updates for new APIs, features, and bug fixes.

The benefits for your app

Google Play services gives you the freedom to use the newest APIs for popular Google services without worrying about device support. Updates to Google Play services are distributed automatically by the Google Play Store and new versions of the client library are delivered through the Android SDK Manager. This makes it easy for you to focus on what's important: your users' experience.

Release Notes

22.0.0.0

  • Updated to r22 of Google Play Services
  • Includes Google Fitness API's

19.0.0.2

  • Updated Support v7 AppCompat to surface SearchView
Write a Review

15 reviews

Louis Cote-Lapierre rates this with
  • 1
  • 2
  • 3
  • 4
  • 5

I have no clue why. But they updated the Nuget page ( https://www.nuget.org/packages/Xamarin.GooglePlayServices) with their new version 3 days ago (10/02/15) and they didn't update it here...

Posted on: February 13 / Version: 22.0.0.0
Phillip Carter rates this with
  • 1
  • 2
  • 3
  • 4
  • 5

Positives:

Does what I need, so far. Seems to be using the most recent version of GPlay services, which is nice.

Negatives:

Configuration was a bit of a pain. Although not related to this component, the documentation for Location is out-of-date.

Posted on: January 13 / Version: 22.0.0.0
Jonathan Dibble

I cannot install this component. I get the following error at the top of the component screen.

Error downloading component: Manifest file is missing Retry

Retrying just repeats the problem. What does this error mean? How can I get passed this ?

Posted on: January 8 / Version: 22.0.0.0
Jesus Gonzalez

I get this error when adding the component:

Could not install package 'Xamarin.Android.Support.v7.AppCompat 21.0.3.0'. You are trying to install this package into a project that targets 'MonoAndroid,Version=v4.0', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author.

EDIT: Seems that using the latest android sdks solves this.

Posted on: December 22, 2014 / Version: 19.0.0.2
Chintan Naik

Facing problems with App size after adding this component. It has increased App size (release version) by 4+ MB (11.8 MB vs. 16.2 MB). Have tried some options including XamGuard but none make big difference. Its big problem as Google also have stopped older AdMob.

EDIT: We just need to use AdMob feature and 4+ MB for that is a big compromise.

Posted on: November 6, 2014 / Version: 19.0.0.2
Kai Cissarek

It's broken.... Can't compile under android 4.0.

Posted on: November 4, 2014 / Version: 19.0.0.2
Neela Annamalai

Could you please update the samples with the "mobileplayground" solution to demonstrate the Google Analytics integration framework?

Posted on: September 17, 2014 / Version: 19.0.0.1
giancarlo lallopizzi rates this with
  • 1
  • 2
  • 3
  • 4
  • 5

what’s the difference with previous revision? doesn’t work on 4.0.4 btw. and very strange behaviour on my galaxy nexus with android 4.3..

Posted on: September 12, 2014 / Version: 19.0.0
Juan Carlos rates this with
  • 1
  • 2
  • 3
  • 4
  • 5

This component is only for Xamarin.Android applications that target Android 4.0 (API level 14) and higher.

Really? Sucks. Can't compile under android 4.0.

Posted on: August 25, 2014 / Version: 19.0.0
Ronny Batty rates this with
  • 1
  • 2
  • 3
  • 4
  • 5

I agree with the other comments here. The example code provided for this component doesn't represent a common use-case for Google Play Services. In-app billing and advertising support would be far more useful, Tommy Parnell's blog covers AdMob banner and interstitials very nicely:

https://blog.tommyparnell.com/admob-with-xamarin-part-1-banner-ads/

Posted on: April 30, 2014 / Version: 16.0
Matt Hughson rates this with
  • 1
  • 2
  • 3
  • 4
  • 5

Varies from the standard Google API often in confusing ways. Taking a couple days to provide samples of the common use-cases would go a really long way, as the sample provided by Google will not work.

Posted on: April 26, 2014 / Version: 16.0
Jordi Benaiges

An example to In App Billing is necessary.

Posted on: April 7, 2014 / Version: 13.0
Brett Duncavage

I agree, an In-App-Billing example is desperately needed. I can’t even find any references to com.android.vending in the assembly.

Posted on: April 7, 2014 / Version: 13.0
Benjamin Mayrargue rates this with
  • 1
  • 2
  • 3
  • 4
  • 5

compilation fails after adding the component. compile with 4.1, min target 4.0, target 4.1

Posted on: April 7, 2014 / Version: 15.0.1
Bryan Phillips rates this with
  • 1
  • 2
  • 3
  • 4
  • 5

Does what it says it does.

Posted on: April 7, 2014 / Version: 15.0.2