GamesSignInClient

Returns the current authentication status via an AuthenticationResult.

If a sign-in flow is currently in progress (such as the automatic sign-in attempt during game start), delivery of this call's result will be postponed until the current sign-in attempt has completed.

This API is useful for understanding if your game has access to Play Games Services. This method should be called when your game starts in order to conditionally enable or disable your Play Games Services integration.

Example usage:

 GamesSignInClient gamesSignInClient = PlayGames.getGamesSignInClient(this);
 gamesSignInClient.isAuthenticated().addOnCompleteListener(isAuthenticatedTask -> {
   if (!isAuthenticatedTask.isSuccessful()) {
     // Disable Play Games Services integration
     return;
   }

   AuthenticationResult authenticationResult = isAuthenticatedTask.getResult();
   if (!authenticationResult.isAuthenticated()) {
     // Disable Play Games Services integration
     return;
   }

   // Enable Play Games Services integration
 });
 

Requests server-side access to Play Games Services for the currently signed-in player.

An authorization code is returned when requested. Your server can then exchange this code for an access token (and conditionally a refresh token when forceRefreshToken is true). The access token allows your server to access the Play Games Services web APIs, which is often used to complete sign-in by verifying the Play Games Services player ID.

When forceRefreshToken is true during authorization code exchange, a refresh token is provided along with the access token. This refresh token enables your server to obtain new access tokens and continue accessing Play Games Services even when the user isn't actively playing. Note that refresh tokens are only generated for players who have auto sign-in setting enabled.

Scopes represent the AuthScope values requested such as AuthScope.EMAIL, AuthScope.PROFILE, AuthScope.OPEN_ID. For new permissions, users will see a consent screen upon the first request. Granting consent (or if permissions were already granted) results in the AuthResponse listing the effectively granted AuthScope. Declining permission results in an empty list of granted AuthScope in the AuthResponse . Regardless of granted permissions, a successful request will always return the authorization code.

Requests server-side access to Play Games Services for the currently signed-in player.

When requested, an authorization code is returned that can be used by your server to exchange for an access token (and conditionally a refresh token when forceRefreshToken is true). The access token may then be used by your server to access the Play Games Services web APIs. This is commonly used to complete a sign-in flow by verifying the Play Games Services player ID.

If forceRefreshToken is true, when exchanging the authorization code, a refresh token will be returned in addition to the access token. The refresh token allows your server to request additional access tokens, allowing your server to continue accesses Play Games Services while the user is not actively playing your game. Refresh tokens are only generated for players that have auto sign-in setting enabled.

Manually requests that your game sign in with Play Games Services.

Note that a sign-in attempt will be made automatically when your game starts. Games will only need to manually request to sign in if the automatic sign-in attempt failed.