Hello everyone, I have a game that it was published a year ago, it is working perfect with Game Services, Today I'm making some updates with BB 2.3.4 and Android Studio 3.1 (MAC) The first thing was to compile and test without modifying anything and I got Sign in Error on the app start, does this have to do with Google Play Services version or something? Everything on the Google Play console is the same way and the current app works fine with Game Services, I have no idea what could be the problem here, if anyone knows what could be the problem please help, thanks!
What should we enter in SHA1 fingerprint? I uploaded an apk for alpha release. In google console>game services, I created a new game and I am trying to add a linked android app. When I clicked Authorize your app, this window popped up. But this SHA1 appears to be different from the SHA1 from the android studio project. Should I enter the SHA1 from my android studio project or just go with this? Can you tell which I should go with? SHA1 from google console: B9:30:EA:AF:CE:E8:7B:F9:24:4B:21:F6:E6:55:03:79:77:C1:8F:39 SHA1 from android studio: 89:B2:5E:B6:3D:6C:E0:48:70:C3:33:CB:97:E9:C1:4E:CE:A1:92:17 Where should I ad testers who can test game services?
Hi, There is a two SHA1, one for Release and another one for Debug. If you test your play service means use debug SHA1 with Debug APK. If you go live means you done with Release SHA1 with release APK. if you misconfigured, for debug APK with Release SHA1 in play services, it will indicates this error : "Google Play Services : signin error" @Forgive @pelloempire @dyan123