StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<ol> <li>Google have a nice quick start of this, you find it here: <a href="https://developers.google.com/games/services/android/quickstart" rel="nofollow noreferrer">https://developers.google.com/games/services/android/quickstart</a></li> <li>You have to upload your APK and setup the game service to the developer console.</li> <li>Make sure your game service has the status "Ready for test".</li> <li>It's not needed to publish the APK unless you want to distribute it (even beta versions need to be published).</li> <li>In the game service you need to setup which accounts that should be able to test the service. How to do it: <a href="https://developers.google.com/games/services/console/testpub#enabling_accounts_for_testing" rel="nofollow noreferrer">https://developers.google.com/games/services/console/testpub#enabling_accounts_for_testing</a></li> <li>When you make changes in Developer Console, some (or all) changes takes a while before they are activated. This could take a couple of hours.</li> <li>When linking your app to the game service you need to authorize the application. You you do this by specifying the SHA1 fingerprint of the certificate. You probably want to use the debug certificate, you find the key in Eclipse in Window-Preferences-Android-Build. You may also want to use your public certificate, you find this in the Export wizard in Eclipse. It's fine to setup two applications, one with debug and another with release certificate. If you don't do this properly you will get an "Unknown error" when you run the example applications. More information: <a href="https://developers.google.com/games/services/console/enabling" rel="nofollow noreferrer">https://developers.google.com/games/services/console/enabling</a></li> <li>(7B) In the previous step I first only used my release certificate. To make it easy to debug I then make by release certificate to a debug certificate. This works, but it's better to setup a client with the debug certificate. If you still want to go this path, here is how you do it: <a href="https://stackoverflow.com/a/14018541/1883479">https://stackoverflow.com/a/14018541/1883479</a></li> </ol> <p>EDIT:</p> <ol> <li>If you get a white screen in the events above, go to <a href="https://cloud.google.com/console" rel="nofollow noreferrer">https://cloud.google.com/console</a> and accept terms of service (only once pr Google-account).</li> <li>After creation the OATH client IDs can be seen and deleted in the API console: <a href="https://console.developers.google.com/" rel="nofollow noreferrer">https://console.developers.google.com/</a>. The client IDs may stop working if a different certificate or multiple certificates are created for the same package name. Note that removal from GameServicesConsole does NOT remove OAUTH client ids from 'backend' (API Console). If the Games Services console does not permit entering a SHA-1 key its because there are keys in the API console you should delete. (The Google Game Services documentation in 7. does not mention this console expect as a means to fix the white screen problem).</li> </ol>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload