0

Ok, so basically I'm trying to run the Google Play Games sample "Type-a-number". I went through all the necessary steps. I set the game up in the Google Play Developer Console, connected my app with the right package name, checked that my account is set up as a tester and created to ClientIDs, one for release and one for debugging. To get to the good stuff: Everything works fine when I export the APK and install it on my device (so the prerequisites should be met) but when I run the app on my device through eclipse I get the "The application is incorrectly configured" error. So for me this seems like I got the debugkey wrong. I checked the SHA1 fingerprints with keytool and triple checked if they match the ones I setup in the ClientIDs. They do. I also deleted and recreated the debug ClientID several times now. package names are exactly the same between them and the project. I went through all the steps of Troubleshooting Google Play Game Services (though I think most of them arent necessary for me because it is 1. the sample and 2. I already have it working in release mode). I checked the eclipse setting again, if I'm using the right debug.keystore, which I did. I'm using the following keytool command to ask for the debugkey fingerprint :

keytool -exportcert -alias androiddebugkey -kestore debug.keystore -list -v

and I'm using the password android. The result is the same SHA1 fingerprint which I already found in the eclipse settings. I don't know what else to do. Does someone see what I am doing wrong? The only thing I can thing of is I'm either doing something wrong with the androiddebugkey or I'm doing something wrong with the debug release (don't you just click run on Eclipse? I also tried debug, which is right next to run, still no luck).

The exact message is : "The application is incorrectly configured. Check that the package name and signing certificate match the cliend ID created in the 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." the package name and certificate fingerprint match the client ID. My mail account is listed as a tester account. Logs say : "Unable to retrieve 1P application XXX from network Game ID (XXX) was not found on server" With XXX being my correct game ID for which I registered the ClientID in the DevConsole.

I would really appreciate any input anyone can give me to maybe solve this issue. Thanks in advance

Vadim Kotov
  • 7,766
  • 8
  • 46
  • 61
majohnny
  • 1
  • 2
  • This is the only thing I can think that could have gone wrong: [Configure Eclipse to use signed keystore](http://stackoverflow.com/a/14018541/1305745) – cavpollo Jun 19 '14 at 23:06
  • Thanks a lot for your suggestion. I tried the method suggested in your link and with high hopes even unpublished the game services for quick testing purposes, unfortunately I'm still getting the same message which i posted in detail above – majohnny Jun 22 '14 at 21:12
  • Sad to hear it didnt fix the problem. I too had some trouble setting up the game services functionality. I did everything I could but what seemed to fix my problem was unlinking and linkin the app again (this means I creating a new project on [google's api developer console](https://console.developers.google.com/project)). Cant remember exactly which error I had at the time, but it is something that is worth giving a try. – cavpollo Jun 23 '14 at 22:02
  • Sorry, wrote my first comment in a hurry. Because my project is published now I don't have those problems anymore, at least not for this project. I know the ClientID is the right one, because everything works fine when I export the APK and I set everything up so it uses the same key for debugging and releasing. I can't see any more possibilities then me doing something wrong while debugging. You don't have to set debug tags anymore, do you? Either way, thanks a lot for your help. – majohnny Jun 26 '14 at 13:07
  • I see, so when released it works just fine. What do you mean by debug tags? – cavpollo Jun 27 '14 at 05:46
  • The android:debuggable tag. It should get set automatically though. – majohnny Jul 03 '14 at 19:40

0 Answers0