You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 19, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Apr 19, 2026. It is now read-only.
Using sdk 1.3 or 1.4, if I open the achievements UI (the default one), I'm not seeing the XP associated with the achievements (I have a "0 XP" string instead).
The same code on android works fine and I see the correct XP value.
Got the same "bug" from the toasts on iOS (if it helps).
Thanks
I forgot to mention this is from an alpha version of the game (PlayGames store listing is still in draft mode).
But well, since it works fine on android, maybe it's not related to being unpublished.
@dakikifr since this is an iOS bug, could you re-open the issue on cpp-ios-basic-samples? Also could you post a screenshot of what you are seeing on Android and what you are seeing on iOS so I can better understand the issue?
I believe this issue is now resolved; until published, the HTTP responses from the server will return "0 XP". After publishing, this issue should go away.
Activity
dakikifr commentedon Apr 13, 2015
I forgot to mention this is from an alpha version of the game (PlayGames store listing is still in draft mode).
But well, since it works fine on android, maybe it's not related to being unpublished.
samtstern commentedon Apr 13, 2015
@dakikifr since this is an iOS bug, could you re-open the issue on cpp-ios-basic-samples? Also could you post a screenshot of what you are seeing on Android and what you are seeing on iOS so I can better understand the issue?
dakikifr commentedon May 14, 2015
Hi, I did, but never get any answer.
tyrmullen commentedon Sep 14, 2015
I believe this issue is now resolved; until published, the HTTP responses from the server will return "0 XP". After publishing, this issue should go away.
dakikifr commentedon Sep 14, 2015
You are right that this one can be solved since the issue is iOS only.