# Authentication or SignIn with Google new PlayGamesServices 0.11.01

**URL:** <https://forum.heroiclabs.com/t/authentication-or-signin-with-google-new-playgamesservices-0-11-01/3303>\
**Category:** Client Libraries\
**Tags:** authentication\
**Created:** [November 29, 2022, 8:17pm UTC](https://forum.heroiclabs.com/t/authentication-or-signin-with-google-new-playgamesservices-0-11-01/3303 "2022-11-29T20:17:53Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![oscargoldman](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.heroiclabs.com/oscargoldman/32/28_2.png) [@oscargoldman](https://forum.heroiclabs.com/u/oscargoldman)\
**Post date:** [November 29, 2022, 8:17pm UTC](https://forum.heroiclabs.com/t/authentication-or-signin-with-google-new-playgamesservices-0-11-01/3303/1 "2022-11-29T20:17:53Z")

</div>

We’re looking for advice or comments related to Unity and the newest version of Google Play Games 0.11.01. It seems the latest Play Games services sdk no longer exposes the player id token, which Nakama needs to authenticate the google profile. Has anyone determined how to properly get the token required to authenticate or sign in with the latest Google sdk? There is a RequestServerSideAccess function in the PGS sdk that returns a token, but the description doesn’t seem to match up, and the token is rejected as invalid by Nakama.

Thanks

---

<div class="post-metadata">

**Author:** ![mharis](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.heroiclabs.com/mharis/32/969_2.png) [@mharis](https://forum.heroiclabs.com/u/mharis)\
**Post date:** [November 30, 2022, 1:12pm UTC](https://forum.heroiclabs.com/t/authentication-or-signin-with-google-new-playgamesservices-0-11-01/3303/2 "2022-11-30T13:12:56Z")

</div>

Hi, there is an existing issue being tracked on Nakama to enhance the token handling: [Google Play Games v0.11.x is incompatible with Nakama 3.13.1 · Issue #915 · heroiclabs/nakama · GitHub](https://github.com/heroiclabs/nakama/issues/915)

If you cannot wait/avoid upgrading the PGS SDK you should be able to use Google Sign-In SDK to get a compatible token: [Sign-in for Android Games &nbsp;|&nbsp; Play Games Services &nbsp;|&nbsp; Google Developers](https://developers.google.com/games/services/android/signin#remove_extra_scopes)

---

<div class="post-metadata">

**Author:** ![oscargoldman](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.heroiclabs.com/oscargoldman/32/28_2.png) [@oscargoldman](https://forum.heroiclabs.com/u/oscargoldman)\
**Post date:** [November 30, 2022, 3:19pm UTC](https://forum.heroiclabs.com/t/authentication-or-signin-with-google-new-playgamesservices-0-11-01/3303/3 "2022-11-30T15:19:54Z")

</div>

thanks for the confirmation.

---

<div class="post-metadata">

**Author:** ![jayaram9877](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.heroiclabs.com/jayaram9877/32/601_2.png) [@jayaram9877](https://forum.heroiclabs.com/u/jayaram9877)\
**Post date:** [January 21, 2023, 7:22pm UTC](https://forum.heroiclabs.com/t/authentication-or-signin-with-google-new-playgamesservices-0-11-01/3303/4 "2023-01-21T19:22:42Z")

</div>

Any update on this issue?

---

<div class="post-metadata">

**Author:** ![oscargoldman](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.heroiclabs.com/oscargoldman/32/28_2.png) [@oscargoldman](https://forum.heroiclabs.com/u/oscargoldman)\
**Post date:** [October 9, 2023, 6:49pm UTC](https://forum.heroiclabs.com/t/authentication-or-signin-with-google-new-playgamesservices-0-11-01/3303/5 "2023-10-09T18:49:18Z")

</div>

Getting back to this after a hiatus and living with the GPG v0.10.x plugin for unity. We have updated to v0.11.1 and Nakama 3.17 and after configuring with client access secret, are successfully getting the temporary OAuth token and successfully linking the google account with the nakama user.  
How does unlinking work? It seems like an Android user is signed in automatically to Google Play Games with the new SDK without any action on the user’s part and I don’t think we can prevent that in Unity.  
Does UnlinkGoogleAsync still work? What do we pass as the token, the same or a refreshed OAuth token?

---

<div class="post-metadata">

**Author:** ![ftkg](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.heroiclabs.com/ftkg/32/1180_2.png) [@ftkg](https://forum.heroiclabs.com/u/ftkg)\
**Post date:** [October 10, 2023, 3:10pm UTC](https://forum.heroiclabs.com/t/authentication-or-signin-with-google-new-playgamesservices-0-11-01/3303/6 "2023-10-10T15:10:58Z")

</div>

@oscargoldman Yes it is supposed to work, it will unlink the Nakama account from the respective Google account. The passed token should be your current access token. Please let us know if it does not work for you.

---

<div class="post-metadata">

**Author:** ![oscargoldman](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.heroiclabs.com/oscargoldman/32/28_2.png) [@oscargoldman](https://forum.heroiclabs.com/u/oscargoldman)\
**Post date:** [October 11, 2023, 3:24pm UTC](https://forum.heroiclabs.com/t/authentication-or-signin-with-google-new-playgamesservices-0-11-01/3303/7 "2023-10-11T15:24:22Z")

</div>

Thanks for the response. Are we supposed to use the temporary OAuth token to unlink or the Google ID that is saved in the Nakama account to unlink? When unlinking successfully, is the google ID deleted from the Nakama account record?  
Thanks

---

<div class="post-metadata">

**Author:** ![oscargoldman](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.heroiclabs.com/oscargoldman/32/28_2.png) [@oscargoldman](https://forum.heroiclabs.com/u/oscargoldman)\
**Post date:** [October 11, 2023, 4:46pm UTC](https://forum.heroiclabs.com/t/authentication-or-signin-with-google-new-playgamesservices-0-11-01/3303/8 "2023-10-11T16:46:35Z")

</div>

we’ve tried both the temp oauth token and the google id, and we get the following nakama error in both cases:  
{“level”:“info”,“ts”:“2023-10-11T12:43:49.961-0400”,“caller”:“server/core\_unlink.go:295”,“msg”:“Could not authenticate Google profile.”,“error”:“google id token invalid”}  
In testing this, the oauth temp token is the same for unlinking as linking, with less than a minute between linking and attempted unlinking.

---

<div class="post-metadata">

**Author:** ![ftkg](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.heroiclabs.com/ftkg/32/1180_2.png) [@ftkg](https://forum.heroiclabs.com/u/ftkg)\
**Post date:** [October 11, 2023, 6:57pm UTC](https://forum.heroiclabs.com/t/authentication-or-signin-with-google-new-playgamesservices-0-11-01/3303/9 "2023-10-11T18:57:33Z")

</div>

You will need to pass the same credentials needed on [Authenticate](https://heroiclabs.com/docs/nakama/concepts/authentication/#google), i.e. the _server auth code_ (a new one as it is single-use).

You can also choose not to pass anything (empty token), and Nakama will clear the Google ID from the account record without checking it.

---

<div class="post-metadata">

**Author:** ![DazyA121](https://avatars.discourse-cdn.com/v4/letter/d/65b543/32.png) [@DazyA121](https://forum.heroiclabs.com/u/DazyA121)\
**Post date:** [October 16, 2023, 10:05am UTC](https://forum.heroiclabs.com/t/authentication-or-signin-with-google-new-playgamesservices-0-11-01/3303/11 "2023-10-16T10:05:57Z")

</div>

I searched on every forum on internet and eventually end up fixing this by performing a force stop on google play [store](https://thegeekpage.com/google-play-authentication-is-required/).

---

<div class="post-metadata">

**Author:** ![LetMeKnow](https://avatars.discourse-cdn.com/v4/letter/l/3bc359/32.png) [@LetMeKnow](https://forum.heroiclabs.com/u/LetMeKnow)\
**Post date:** [June 27, 2025, 9:05am UTC](https://forum.heroiclabs.com/t/authentication-or-signin-with-google-new-playgamesservices-0-11-01/3303/12 "2025-06-27T09:05:30Z")

</div>

Did you fix it? How do you use GPGS 0.11.01 now?

---

<div class="post-metadata">

**Author:** ![LetMeKnow](https://avatars.discourse-cdn.com/v4/letter/l/3bc359/32.png) [@LetMeKnow](https://forum.heroiclabs.com/u/LetMeKnow)\
**Post date:** [June 27, 2025, 9:06am UTC](https://forum.heroiclabs.com/t/authentication-or-signin-with-google-new-playgamesservices-0-11-01/3303/13 "2025-06-27T09:06:02Z")

</div>

Was your problem same with the one in this post? How did you fix it specifically?
