MobileServices Client not supporting Google authentication

Category: azure mobile


Sajad Deyargaroo on Mon, 05 Jun 2017 18:06:19

Google has stopped supporting webviews for authentication, which was being used by WindowsAzure.MobileServices client SDK. It seems this Mobile service client has been deprecated but will there be any patch released for it so that we can continue to use our existing Mobile Service. We have already migrated (not upgraded) our Mobile service to Mobile app, which moves the underlying infrastructure but the backend/SDK/etc. of the service remains unchanged. However, it seems the current version of Microsoft.Azure.Mobile.Client is also not working with Google Auth now and it also has issues when used with old Mobile service. So we are looking for an update to WindowsAzure.MobileServices  that supports Google Authentication outside webview.


Jacob Wallraff (MSFT) on Mon, 05 Jun 2017 20:25:01

We are currently working on fixing the server authentication flow for our .NET client, so a fix will be available in the future.  Not ETA yet, but you could consider using client flow login in the meantime.

Client flow login is documented here:

Let me know if you have any questions.  Client flow login is more complex than server flow, but if you want a solution right now it's worth checking out.

Sajad Deyargaroo on Wed, 07 Jun 2017 13:24:11

We have Xamarin app and a web app, both applications use the same Mobile service.

Even if we implement the client flow in the Xamarin app, we need to register Android Type app in the Google Developer Console and link the same to the Mobile service. Client flow will work in Xamarin app but it will break the web app for which we need to link the Client ID of the Web Type app, which is registered in Google Developer Console.

How can we make both Xamarin and Web app work with the same Mobile service?