Game On! Top 7 Play Games setup mistakes

Google for Developers · 13K views · 2013 · 27:04

Open on YouTube

Game programming & enginesWeb developmentSoftware (other)talkdated

Why Stack Overflow recommends it

Stack Overflow users link it when answering Google Play Games Services sign-in and configuration errors, since it explains the usual setup mistakes like mismatched OAuth client IDs, wrong app IDs and SHA1 problems.

Recommended by 3 people across 3 different months, 2013 to 2020.

What it is

A 2013 Google Developers talk in which Bruno Oliveira, Dan Galpin and Todd Kerpelman walk through the seven most common mistakes developers make when integrating Google Play game services into mobile or web games. It covers setup issues such as app IDs, OAuth client IDs, SHA1 fingerprints and console configuration.

What people said

Recommends Teyam · 2016-10 · Stack Overflow · on “Error in setting up Google play services in unity”

If we refer to the actual error as shown in your log output, the problem is caused by the application ID declared in your Manifest which is actually one of the top setup mistakes committed by developers as shown in this video [this video] . To troubleshoot this kind of error, please check the following: For Android: please verify that the value of the @string/app_id resource matches your application's numeric ID. The value of this resource should only contain digits. For example: <string name="app_id">123456789012</string> Warning : Do not use the full client ID ( 1233456789012.apps.googleusercontent.com ) as your app ID. This will result in errors. For iOS: The application_ID is the number that

Recommends Totoro · 2017-04 · Stack Overflow · on “Achievements not showing in Google Play Games App”

We found the answer ourselves. We messed up the configuration in the Google Play Developer console and in the Google API console . Observations: We noticed that our app had different OAuth2 Client IDs, e.g.: Google Play Developer Console, Linked apps detail view 121212121212-4k97si3bnwertwertwet78oj571nl81ce3.apps.googleusercontent.com Google API Console, Credentials, OAuth 2.0 client IDs 121212121212-h25jh8qrps8awertwetertwetweagp3n3t.apps.googleusercontent.com We also saw that we had a lot of errors coming from the Google Play Games Services when we looked in the Dashboard of the Google API console . [LINK] At a closer look, we saw that nearly all of them were client errors (4xx), but we c

Recommends Lolo06 · 2020-02 · Stack Overflow · on “Unable to link App to Google games services, SHA1 already linked to packagename”

Hello, this troubleshooting video from Google helped me for a similar issue. [this video] . explanations for SHA1 and package start at 18 min 40s. Hope it helps

Cites user2557261 · 2013-07 · Stack Overflow · on “Google Play Services Android won't sign in Adobe Air”

Now I can answer my question officially: I fixed it. Apparently if you go to the API console and change the Oauth from there the game services doesn't detect it. I originally put in the wrong SHA1 and fixed it through the API and not the google services developer console. [this video] (it's problem #6 which is really n)

Cites Totoro · 2017-04 · Stack Overflow · on “Google Play Games Service - Login Failed (OAUTH2: UNREGISTERED_ON_API_CONSOLE)”

Where did you create the OAuth 2.0 client for your app? From your screenshot it seems that this is the entry in the Google API console . Did you also create an entry in the Game services section in the Google Play Developer console (see step 2 in the Google documentation [LINK] )? I had big problems with my current game, because I created the OAuth 2.0 client manually in the Google API console and not in the Google Play Developer console and the OAuth 2.0 IDs in both consoles didn't match. According to a video [this video] from Google Developers OAuth 2.0 clients should only be created in the Google Play Developer console . I wrote more about what I did wrong in this post [LINK] .

Cites Teyam · 2017-10 · Stack Overflow · on “I cannot set up Google Play Games Services”

You mentioned that you published your app. Note that game settings should also be published. If you haven't done yet, follow these recommendations when setting up your game [LINK] to use the Google Play games services. Set up your game with the Google Play Console If you created an Oauth 2.0 client ID for your app in the Google Play Console, Google Play games services will not know about the association between the game’s achievement and leaderboards and the client ID. To create this association, you should first link your app with the game as described in Create a linked application [LINK] . Use the correct application ID in Android The application ID is a required string resource that you