Sorry your browser is not supported!

Made an large update to my game and hoping to push it to the app stores. So built it with the latest AppGameKit version as Android APK.

Google Play Application ID is set correctly. Lets say it is 8xxxxxxx. I checked in the AppGameKit export dialog vs the Google Play console. I even decompiled the generated APK to see that there is no wrong ID set there. AndroidManifest.xml has the correct ID of 8xxxxxxx.

Achievements work. If I open my achievements list in the game as installed from the APK, it shows correctly, progress is fine, all is fine.

Leaderboards crash the whole app/game. Phone shows error Google Play application has crashed. Logcat debug log shows the following:

E Volley : [8799] BasicNetwork.performRequest: Unexpected response code 403 for https://www.googleapis.com/games/v1/leaderboards/scores?language=en_GB
E GamesServer: Attempting to access a resource for another application. Check your resource IDs.
E MultiDataOperation: Attempt to access application 8xxxxxxx from application 900475732431.

So it seems that the game is giving Google Play ID of 900475732431 when I try to access the leaderboards. But Google correctly identifies the leaderboard ID as belonging to my app.

The code I use is simply this: GameCenterShowLeaderBoard(LEADERBOARDID)

Now, I believe I have GameCenter set up correct as it has worked before, I have not changed anything, and the achievements still work.

Now, if you slap the mystery ID of 900475732431 into Google, the only result you get is from this forum:

https://forum.thegamecreators.com/thread/219189

What is 900475732431 and why is it appearing in my app? Why is AppGameKit using it and not the ID I give in export dialog?

So any ideas to what am I doing wrong here and how to fix?

Please don't tell me someone hardcoded the GameCreators app id into AppGameKit for leaderboards.. And that there is no way to downgrade the Steam version to previous build and Paul is taking an extended vacation... And that iOS restore purchases is similarly broken, and I would like to release my game update on both...

OK. So a brief update on these issues.

The iOS RestorePurchases() functionality suddenly appears to be working on my app now. I changed practically nothing so perhaps it was something on Apple end of things. Did get some updates published from them so might be that, or maybe not. Maybe it will break suddenly again but who knows. Will inform if it happens.

But the Android Leaderboards issue still persists. Some added information from further testing:

I have two games I updated. Somewhat different results each:

Game 1:

No added leaderboards or any other real changes. Did enable Firebase and other than that only minor updates and made a new build with the latest AppGameKit .
Leaderboards do not open, the spinning wheel comes up and keeps spinning forever.
Running with the same Play Services but with previous version from Google Play, the Leaderboards work just fine.

Game 2:

Added a set of new leaderboards. Enabled Firebase. New build with latest AGK.
All the old leaderboards that used to work crash with this error. Except that with one user the old leaderboards also work? All the new leaderboards work for everyone.

Any ideas what to do to fix or debug this?

Time passes... Time passes... LeChuck arrives.

OK, a brief update again. After some internet wondering, I see some have had similar issues with their games and leaderboards. There is a thread on AppGameKit as well on Steam https://steamcommunity.com/app/325180/discussions/0/343788552534587944/.

Generally there does not seem to be any solution posted anywhere but to re-create your Game Services, leaderboards and whatever. But I did manage to find something that may be the cause. Some of my leaderboards work for all, and some for only a few/one of my test accounts, and people report getting their leaderboards linked to wrong projects if their games gives the wrong ID for Play Services in the beginning. It seems to me this link cannot happen on Google server side or it would affect everyone and not just some.

So I took my devices and accounts suffering from these issues and cleared the cache and all data on Google Play Services App on those devices/accounts. Now the leaderboards also work for those. For some users/games the leaderboards are still stuck in a long long loop of loading up. Some comments online seem to suggest this may happen due to lack of players, which surely is true for my awesomely non-popular games. But at least it does not crash. Let's get back to that when more issues arise.

But regarding AppGameKit, I believe this issue can occur if you set up leaderboards, run you app over the AppGameKit Player and end up submitting/querying your leaderboards from the game while running AppGameKit player. And you may need to do this before running the game from a pure APK file with the correct signature, or from one downloaded from Google Play. Which is of course very likely since everyone will likely test their game on the player before actually running it from the store/exported APK.

This is of course just speculation but would seem to fit my experiences so far. Maybe Paul or someone can just confirm whether 900475732431 is the Google Play service ID used by AppGameKit Player?

If this is so, I would suggest to fix this in future by not submitting anything to Gamecenter when running within the AppGameKit Player. And not querying the real leaderboards either. For achievements I see AppGameKit Player just displays "Test Achievements". So please do the same for the leaderboards or this will keep breaking all games forever.. If I am right that is.

T