There is no linked app associated with this client

Question

I'm becoming crazy with this one. I just published a game on Google Play Store and the game uses the Google Play Games services.

Sign-in and leaderboards / achievements worked fined with the application signed with the debug key, but since I built and published my app using my release key, Google+ sign-on is impossible. I always get the infamous error "E/SignInIntentService(25004): There is no linked app associated with this client ID."

I double- and triple-checked everything : my app is published, the package name and SHA1 fingerprint are correct and match what I extracted from the release APK, I unlinked and relinked the app in the Google Play Console multiple times, but nothing works.

Ideas, anyone ?

Thanks

Answer 1

I tried linking a new app and it didn't work and almost started the process of creating a new app again. However, I tried regenerating the API Key from the Google APIs Console and it worked!

Go to Credentials, select your API key and then click on "Regenerate Key".

Answer 2

I had the same issue. All you need to do is to make sure before creating a new game, you input the exact package name and the fingerprint certificate (SHA1) that matches your release keystore. My problem is that I put a default fingerprint in the game and decided to change it later. Somehow the google console developer can still detect your previous fingerprint even though you replace it with your final fingerprint. The solution was to delete the first game configuration and created a new one. No need to create or attach your debug certificate.

Answer 3

There is a bug in Google Play Service...

Don't try to login to the Game Service unless you upload first APK and link the game in Game Service (putting a proper package name is not enought, there must be an first APK uploaded, so during the linking process you can select the app from suggestion list)...

When you try to login before linking first, the services comes into "bad state" and even after you assign a game to the service, the Auth process still claims that it is not linked....

I have made 6 games and had this issue 2 times. The solution is to delete corrupted Game Service. Create new one (recreate whole CFG - sorry about that), reassign APP ID in a game, link the game to the Game Service (through the suggestion list) and then try to login in into service...

Be careful because there is also a lot of misunderstanding "false" notification in the logcat....

Answer 4

Actually, I did all that and everything was fine. However, I read and re-read some others posts here about the problem and found this comment. user2267794 nailed it for me.
Since I had just released my game, I had removed by debug OAuth Client Id, thinking it was no longer needed – for some time at least.

On the brink of giving up, out of desperation and having nothing to lose, I tried what user2267794 had done and linked my app a second time with my debug key SHA1. And it magically worked immediately. Using the release key without the debug one doesn't seem to work for me, for whatever reason.
If it's not a bug, I don't know what is.

Answer 5

Just To Help Others-

Please keep this in mind while implementing Google Play Services:

Warning: Do not create new client IDs for your game from the Google API Console. If you do so, Google Play games services will not associate your game settings with the client ID, and this could cause errors during gameplay.

Answer 6

Is Game Services published in the Google Developer Console? That's a separate step.

If your app itself isn't published (i.e. in beta), only those google accounts associated with a specified google+ or google groups account designated to be your pool of testers will be able to connect.

You also need to verify that the app_id compiled into your app (often in /res/strings.xml) matches the google api console ID. For example there should be a line like:

<string name="app_id">123456789123</string>

And don't get it confused with your facebook application_id!

Beyond that you'll need to check the Google Cloud Console under Overview -> APIs & auth -> Registered apps and verify that the prefix for CLIENT ID matches, that the PACKAGE NAME is correct, and the CERTIFICATE FINGERPRINT (SHA1) matches.

If it doesn't work after all that, you'll be roughly where I find myself currently-- having done all that and still stuck.