question

Hi,

Thank you for pointing out that link. I couldn't find any information though about how to setup the linked app in google play services to work with playfab. Do you if I should create a linked web app and if so what the URL should be so that it works with playfab?

-JJ

Hey JJ,

You do not need any special linkage to PlayFab to use LoginWithGoogle. That being said, you will need to have your GooglePlay and Google Developer consoles linked and the proper APIs enabled.

Steps:

1) Link your GooglePlay Project to your Google Developer Console

2) Enable Google+ API in your linked console project

3) Build your client embedded with the required android libraries. For Unity, this requires a third-party plugin. We have a sample Android project you can use for getting started here. Our example only provides coverage over the most basic scenarios. For more in-depth Google+ features you will want to extend the code provided or look into a retail plugin. 

4) Call GoogleAuthUtil to obtain your token 

5) Pass your token to PlayFab via LoginWithGoogle.

6) You should get a success callback with a valid session ticket. 

Let us know if you have any further issues and we will be happy to assist. 

Thanks,

Zac

@Zac, thanks. I have the API linked, but when you set it up it asks you what kind of app

http://cl.ly/3R0L3V2K1A1S

So, first I selected Android, and in the ADB log I got a message that I needed to setup a web app to get the token. So I setup a web app and used my website as the URL. Now I get a token that shows up in the log.

So is the token that the play games sdk (https://github.com/playgameservices/play-games-plugin-for-unity) give you via ((PlayGamesLocalUser)Social.localUser).idToken  different than the one that is retrieved with those plugin scripts from Hamza? because I am getting a token, it's just not accepted by playfab, so maybe they are different?

JJ,

First off I will say that I am not that familiar with the google play games plugin, as it did not perform the proper getToken functionality. Perhaps they have added it recently. From what I can tell, by looking at the API docs, it seems like this would get you the proper token; however, there are additional setup instructions for the unity plugin, ensure that those are completed.

Next, there are other settings that you must check to ensure they are linked correctly: 

• Your console developer project needs to have the Google+ API enabled. 
• Your GoogleDeveloper console is linked to your API console in two places: linked via the GooglePlay > Settigns > Services & APIs. I believe you need to do this at both the application level and the overall level.

Hamza's plugin was a work-arond to using the gpg unity plugin.

Also, I would like to point out a point out that I noticed a difference in the GooglePlay setup instructions. They are configuring a web app, where as for PlayFab's titles we created an Android app link using the details from the corresponding Google Console. I believe this should work in both cases; as what is truly required is the Oauth2 client ID which is provided on the Linked Apps screen:

GooglePlay Console > Game Services > <Your Title> > Linked Apps 

If you haven't already also may need (depending on the plug-in) to enable GooglePlayGames services in your API console:

If you continue to have issues then the the gpg plugin may still not be in sync with what this Google Auth API provides.

-Zac

Is that the correct token Jedrzej? The PlayFab API says it's looking for the accessToken, not the idToken. That would be:

(((PlayGamesLocalUser) Social.localUser).accessToken) 

I'm about to test this same setup myself in the next day or so. I'll post back my findings later if I learn anything new.

Hi @"Jedrzej Jonasz", @"Jason Irvan", do you have updates regarding Google tokens?

I have worked with a co-worker to figure out the problem with the GooglePlayGames plugin for unity. The problem is that the plugin starts an async process when you request the accessToken for the first time.

What we had to do to work around the problem was if we were authenticated, request the access token until it wasn't null. We had this in a coroutine that would have .25f sec ways between each attempt. Usually by the 3rd attempt we would have a valid accessToken and could move forward. Not elegant by any means but do with it what you will.

Hey Adam,

Thanks for the insight on the GPG Plugin. We worked with Hamza to create our plugin to work around the limitations of the GPG plugin. That being said, our plugin only provides minimum functionality for obtaining the Google+ ID for testing our API and to provide an example for our developers. 

Happy Developing,

Zac