When I attempt to retrieve the new idToken, it instead only shows the original, which inevitably has expired.
In essence, I'm attempting to re-authenticate but it's not producing a new, valid, token.
What does best practice look like for retrieving a new token in advance of the original expiry?
I'm sending the idToken to my server for verification purposes rather than the authToken as otherwise I'd need to request extra scopes like profile information and/or email. Is there a way to retrieve another idToken while logged in to Play Services or is the intention for developers to assign their own refresh tokens for this purpose?
Edit: The only way to do this seems to involve logging out and in again. This is fine but it always shows the notification at the top of the screen unless you add .EnableHidePopups() in the PlayGamesClientConfiguration.Builder()
I'm attempting to renew the idToken retrieved via PlayGamesServices using:
Social.localUser.Authenticate
...
idToken = ((PlayGamesLocalUser)Social.localUser).GetIdToken();
When I attempt to retrieve the new idToken, it instead only shows the original, which inevitably has expired. In essence, I'm attempting to re-authenticate but it's not producing a new, valid, token.
What does best practice look like for retrieving a new token in advance of the original expiry?
I'm sending the idToken to my server for verification purposes rather than the authToken as otherwise I'd need to request extra scopes like profile information and/or email. Is there a way to retrieve another idToken while logged in to Play Services or is the intention for developers to assign their own refresh tokens for this purpose?
Edit: The only way to do this seems to involve logging out and in again. This is fine but it always shows the notification at the top of the screen unless you add .EnableHidePopups() in the PlayGamesClientConfiguration.Builder()