I’ve followed the checklist step by step, but it was all right.
I do not find any useful information in the troubleshoot for my problem.
I’ve added my manifest to the main post
Has the Sign-in UI displayed?
Have you upload the release-build APK to google console and make Alpha/Beta test AFTER added SDKBoxPlay?
this is play console Create new poject savegame issue.
StateManager.cpp -> remove .EnableSnapshots()
and then sign success
this is new Project savegame issue.
in play console
this is create new poject savegame isuue.
StateManger.cpp —> remove .EnableSnapshots()
and then sign in success.
I’ll try this!
I’m sorry but i do not understand, can you explain it better? Thanks
The sign in UI does not display, but my game stops and becomes darker while a loading circle appears (i guess that’s part of the sign in ui).
I uploaded the release-build to google play in alpha test AFTER SDKBoxPlay integration, but the error persists.
Maybe it has something to do with this:
I’ve also integrated firebase in my project, and firebase uses
<string name="google_app_id" translatable="false">1:795086958816:android:XXXXXXXXXXX</string>
So I had to change the google play games app id attribute name in
Of course changed also in the AndroidManifest.
Is this attribute used somewhere else? (Maybe in the SDKBoxPlay sources)
here is a google id conflict soulation. same as your’s.
Thank you for your answer!
If you read carefully that’s exactly what I did!
I’m still stuck then…
this should be something wrong in app config or google web config.
- can you double check keystore’s SHA (http://docs.sdkbox.com/en/qa/sdkboxplay_troubleshoot/#keystore)
- compare this sample project, to check project config. https://github.com/sdkbox/sdkbox-sample-cpp317/tree/sdkboxplay
Hello, thanks for your answer,
This is my signing configuration:
I’ve joined two apps to the google play games console:
- The one for production, with the google play signing key
- The one for test, with my upload certificate, so that i don’t have to upload my app every time i want to test something about google play games
Here you can see the sha1:
Lost in the Web:
Lost int the Web - Debug:
Impronte digitali certificato: SHA1: 8F:7F:55:58:75:9D:A1:48:15:80:7A:7F:D3:A7:XX:XX:XX:XX:XX:XX SHA256: 91:A3:59:F9:29:B1:B6:5E:3E:EC:B0:A2:76:DE:61:29:D4:63:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX Nome algoritmo firma: SHA256withRSA Algoritmo di chiave pubblica oggetto: Chiave RSA a 2048 bit
Both versions (downloaded from the google play store and installed directly) give me the same problem
two apps in google play games console, which one are you use?
use your app config on the sample project is another way.
Both apps on the google play games console are linked to the same google play app (same package name), the only thing that changes is the key (one for debug and one for production) but both ones don’t work.
(I’ve tried with one app linked but it does give me the same problem!)
I do not understand point nr. 2
Did you manage to fix this!? I’m experiencing the same issue
Hoping that someone can help us!
Created a clean 3.17.1 project just with a single signin(). Also repeated all steps in google console… yet again… error 8
SdkboxGPGAuthentication W sign in failed:8 null and solved by bellow steps:
Google Play Console
- Check game published on
- Check game Alpha/Beta Test published
- Check API Console project SHA1
- Double check your APK [SHA1]
- Set your
"cloud_save": false,with sdkbox-sample-ccc200/build/jsb-link/res/sdkbox_config.json
"cloud_save": false, with sdkbox_config.json file.