The application is not properly configured to use the services of the google game

Question

I am using the BaseGameActivity class to connect to Google gaming services. The problem is that some authentication does not work. I have been searching for solutions on the Internet for several hours but have not found anything that helped me solve the problem.

When I run BaseGameActivity, I get the following output in LogCat:

 03-19 14:22:36.126: W/GameHelper(15312): **** 03-19 14:22:36.126: W/GameHelper(15312): **** 03-19 14:22:36.126: W/GameHelper(15312): **** APP NOT CORRECTLY CONFIGURED TO USE GOOGLE PLAY GAME SERVICES 03-19 14:22:36.126: W/GameHelper(15312): **** This is usually caused by one of these reasons: 03-19 14:22:36.126: W/GameHelper(15312): **** (1) Your package name and certificate fingerprint do not match 03-19 14:22:36.126: W/GameHelper(15312): **** the client ID you registered in Developer Console. 03-19 14:22:36.126: W/GameHelper(15312): **** (2) Your App ID was incorrectly entered. 03-19 14:22:36.126: W/GameHelper(15312): **** (3) Your game settings have not been published and you are 03-19 14:22:36.126: W/GameHelper(15312): **** trying to log in with an account that is not listed as 03-19 14:22:36.126: W/GameHelper(15312): **** a test account. 03-19 14:22:36.126: W/GameHelper(15312): **** 03-19 14:22:36.126: W/GameHelper(15312): **** To help you debug, here is the information about this app 03-19 14:22:36.126: W/GameHelper(15312): **** Package name : ***** 03-19 14:22:36.126: W/GameHelper(15312): **** Cert SHA1 fingerprint: ***** 03-19 14:22:36.126: W/GameHelper(15312): **** App ID from : ***** 03-19 14:22:36.126: W/GameHelper(15312): **** 03-19 14:22:36.126: W/GameHelper(15312): **** Check that the above information matches your setup in 03-19 14:22:36.126: W/GameHelper(15312): **** Developer Console. Also, check that you're logging in with the 03-19 14:22:36.126: W/GameHelper(15312): **** right account (it should be listed in the Testers section if 03-19 14:22:36.126: W/GameHelper(15312): **** your project is not yet published). 03-19 14:22:36.126: W/GameHelper(15312): **** 03-19 14:22:36.126: W/GameHelper(15312): **** For more information, refer to the troubleshooting guide: 03-19 14:22:36.126: W/GameHelper(15312): **** http://developers.google.com/games/services/android/troubleshooting 

I have verified more than ten times that the package name, Cert SHA1 fingerprint and application ID (which I took here) are really identical to those listed in https://console.developers.google.com/project/my-app-id/apiui / credential

I also deleted the customer IDs provided there several times and updated them. But nothing helps. Can you help me?

Answer 1

The registered user on the device must be a valid tester account. Verify that the registered user on the device is configured as a valid test user. if not, add the email from which you are logged in to the tester accounts in the Google Play game developer console

Answer 2

When you install and run the game / application on your device from eclipse itself, it will not log into the system and connect to google services. Follow the instructions below.
I am. You must first export the game / application (Build Project before exporting) II. and download the app.apk file to device III. Install and run the game / application, you will see a google login window.

Answer 3

Have you tried this? The fingerprint Cert SHA1 generated during debugging does not match the keystore used. In my case, I tested the application in debugging, and this certificate was different from the authorized one.

Answer 4

Be sure to use the correct SHA1. In my case, I had two different debug.keystore on my PC.

One of them was located in C:\User\myUser\.android , and the other was located in my android-sdk\.android

I used Eclipse, and in my case, debug.keystore used from the android-sdk directory.

If you use Eclipse, you can check the location of debug.keystore at Window/Preferences/Android/Build/ .

Answer 5

In my case, the fingerprint of SHA1 was wrong.

• Go to the Google Play Developer Console and find your game
• Click on the "Game Details" tab on the left.
• Scroll down to "Project Console Project" and click on "Project Name"
• Now in the Google Developer Console ( Miscellaneous Console ) go to the API Manager
• Go to credentials tab
• Under OAuth 2.0 Client IDs, click the name of your project.
• And now, finally, you can change your SHA1 fingerprint and / or package name, which should be.