Search code examples
google-playgoogle-play-servicesgoogle-oauthgoogle-play-games

"The Application is incorrectly configured" on published game

I set up Google Play Games Services through the Google Play Developer Console by following the instructions here.

I went through the troulbeshooting guide here.

If i run my app through eclipse, it can connect fine to Play Games. However now the update is released and if I download it from the Play Store it cannot connect.

I verified that my SHA1 from the android export matches what is in the developer console. I even tried linking a new app with the SHA1 and it says: "This client ID is globally unique and is already in use."

I am now panicking because my game is live and can't connect. Help!

EDIT:

I added my client ID through the Google Play Developer Console, not the Google Developer Console. I removed the Client ID that was in the Google Developer Console.

enter image description here enter image description here enter image description here

enter image description here

from Google Play Developer Console

Edit:

I cannot add a new client in GDC, i get an error about "duplicate fingerprint": enter image description here

Solution

  • Before altering / adding new API clients, make sure that you have checked the following:

    • IS your play games project published?
    • Or, are the accounts you are using for testing included on the testers list?
    • Are you signing your app correctly? If you are using your debug keystore in a released game, the app will not correctly be able to authenticate.

    At any rate, deleting clients could fix working apps if you have already published and I'd hate to give you advice that breaks stuff. That said, if you're sure you need to create / recreate your client, move on.

    The reason you are encountering the "This client ID is globally unique and is already in use." issue is that there exists a client with the same package name and SHA-1 hash in any Google Developer console project (not necessarily a Google Play Games project, not necessarily the current project, and not necessarily a project for your account if you are working on teams). This is because the combination of package name and SHA-1 hash must be unique for authentication.

    At any rate, it's possible that the project still has a client (for Android) created that needs to be removed. This means that you must either remove the "bad" client from the developer console, re-sign your app with a new keystore, or use a different package name.

    Option 1 - Removing clients

    Although this is the most destructive option, it may be a good approach if you already removed clients from the Play Games Developer console and don't want to change your configuration.

    Access your project from https://console.developers.google.com because this will give you a superset of the clients created from the play games console and will have an according project. Select the APIs & Auth -> Credentials section. From here, remove any Android clients you intend to replace.

    Return to https://play.google.com/apps/publish and select your games project. You should now be able to add another client.

    Option 2 - Create a new keystore

    This is best covered in the Android documentation. After changing your keystore, you will be able to add another client using the new keystore signature.

    Option 3 - Change the package name

    You must update com.yourname.app with something other than com.yourname.app. This means renaming folders in your Android project, changing includes and package namespaces, and updating your project's AndroidManifest.xml.

    After changing any of these, you should be able to create a working Google API project and get your app ready.