title: Unity play game service authenticate fail
body: <p>I download play games unity plugin from
  <a href="https://github.com/playgameservices/play-games-plugin-for-unity" rel="noreferrer">https://github.com/playgameservices/play-games-plugin-for-unity</a></p>
  
  <p>and run MainScene in android device</p>
  
  <p>then click "Authenticate" button ,and popup google play dialog..</p>
  
  <p>finally Social.localUser.authenticated is always false.</p>
  
  <p>then I draw debug info in the scene below:</p>
  
  <pre><code>Createing platform-specific Play Games client
  Creating real IPlayGamesClient
  Entering state:ShutdownState
  ShutdownState.OnStateEntered:Defaulting to no-op.
  Starting Auth Transition.Op SIGN_IN status ERROR_NOT_AUTHORIZED
  PlayGamesHelperObject.OnApplicationPause True
  PlayGamesHelperObject.OnApplicationPause False
  PlayGamesHelperObject.OnApplicationPause True
  PlayGamesHelperObject.OnApplicationPause False
  Invoking user callback on game thread
  </code></pre>
  
  <p>I try these methods to fix below,
  but I can't still login successfully</p>
  
  <p>Method1 In the google play game console, 
  add test user and active alpha,beta test.</p>
  
  <p>Method2 In the unity,to create android keystore and signing</p>
  
  <p>The keystore is a signature file that is used to sign your apk. When you create development builds Unity will not sign the apk.</p>
  
  <p>You only need one Keystore file for your projects. The file is your signature. To create one do this:</p>
  
  <p>In the publishing settings check the "Create New Keystore" box.</p>
  
  <p>Click browse and choose a location where you want to store the file. It should be somewhere central since it's not really related to your project.</p>
  
  <p>Set a protection password for the file and confirm it.</p>
  
  <p>Select "Create a new key" from the "Key Alias" dropdown.</p>
  
  <p>A window should open which you have to fill with your personal data about your organisation / person. The alias at the top is just a name of the keystore. If you have multiple identities make sure you choose a meaningful name. You need to set a keystore password. Note this is not the same as the protection password above. As far as i know they can be the same, but for security you should use two different. If you haven't write the passwords onto a sheet of paper ;)</p>
  
  <p>Click "Create Key" to generate your keystore file.</p>
  
  <p>To use a keystore for signing you have to:</p>
  
  <p>Check the "Use Existing Keystore" box.</p>
  
  <p>Click browse and select your keystore file.</p>
  
  <p>enter your protection key.</p>
  
  <p>select your desired identity from the alias dropdown.</p>
  
  <p>enter the alias password in the field below</p>
  
  <p>Make sure you have set your Android Market Licensing RSA Public Key at the bottom of the publishing settings. The public key has to be acquired from your Google market account.</p>
  
  <p>Now create your APK file and it will be signed with your identity.</p>
  
  <p>Method3 someone metioned these code is successful for them</p>
  
  <pre><code>PlayGamesClientConfiguration config = new  PlayGamesClientConfiguration.Builder().
      //.EnableSavedGames()     
      Build();
  </code></pre>
  
  <p>PlayGamesPlatform.InitializeInstance(config);</p>
  
  <p>or     </p>
  
  <pre><code> PlayGamesClientConfiguration config = new PlayGamesClientConfiguration.Builder().
          .EnableSavedGames()     
          Build();
   PlayGamesPlatform.InitializeInstance(config);
  </code></pre>
  
  <p>Method4 I also do these check </p>
  
  <p>1.Application ID in the "Android Setup" dialog matches the application ID in the Play Games Console (<a href="https://play.google.com/apps/publish" rel="noreferrer">https://play.google.com/apps/publish</a>)</p>
  
  <p>2.The linked application package name in the Play Games Console matches the bundle id in Player Settings / Other Settings/ Bundle Identifier</p>
  
  <p>3.The user that you are logging in as is added as a tester in the Play Games Console</p>
  
  <p>So I stuck here,I don't know why can't authenticate sucessfully.</p>