title: How to "Link App" to existing Client ID and prodcution SHA1 when publishing Alpha new Android Game
body: <p>I have completed the development and testing of my new Android Game that uses google-play services. such as AppState, Google Plus sign in, achievements, &amp; leaderboards. I have been testing on numerous devices with numerous tester accounts all set up correctly within the Google Play Developer and Google API console.</p>
  
  <p>My testing APK was signed with my standard eclipse debug keystore.</p>
  
  <p>I am now ready to start Alpha testing. i have signed my APK with my production keystore and uploaded it successfully.</p>
  
  <p>I have set up a google community for my Alpha testers, however none of my testers can sign into my published Alpha game.</p>
  
  <p>they receive a pop up message saying "The application is incorrectly configured. Check that the package name and signing certificate match the client ID created in Developer Console. Also, if the application is not yet published, check that the account you are trying to sign in with is listed as a tester account. See logs for more information"</p>
  
  <p>How do i link the Alpha APK with the production SHA1 key?</p>
  
  <p>Do i have to delete the current linked game and re add it using my production SHA1?</p>
  
  <p>or can i have duplicate linked apps for the same game, one linked to me test debug SHA1, the other linked to my production SHA1?</p>