GPGS V2 not logging in

Solar2D Android
#1

Hi so I am trying to add GPGS Leaderboards to my game. I already have the licensing and and app ID in the build.settings and config.lua.

I am trying to login using this code

local function gpgsInitListener( event ) if not event.isError then if ( event.name == "login" ) then -- Successful login event print( json.prettify(event) ) gpgs.leaderboards.show( "CgkI5vqAkuMSEAIQAQ" ) end end end //inside of my scene create function gpgs.login( { userInitiated=true, listener=gpgsInitListener } )

but it does not successfully login so the leaderboard does not show. I have also tried settting up a button to show the leaderboard but that doesnt work either even if the function is called.

When I used ADB everytime i pressed the button the output would show “not logged in”.

I also read through the debug and saw that it said something about the build id or api key not being right, or the leaderboard isnt live yet. I waited a few days to make sure the leaderboard is live and I set my api key SHA-1 to the SHA-1 i get from my keystore I use to sign with corona. I dont know what else to try please help.

#2

I and some more people seem to have similar issues, there’s a thread in the game networking part of the forum about this as well. From what I can see all requests to the drive api results in errors. Not sure why.

#3

Yeah I’m having the same issue but my Google Play Games Services API is throwing all of the errors and not my Google Drive API. My GPGS API says it has 43 requests and the error(%) is at 100.

#4

Also I get this in the console

02-26 16:56:27.499 4982 9551 E SignInAuthenticator: \*\*\*\* 02-26 16:56:27.500 4982 9551 E SignInAuthenticator: \*\*\*\* APP NOT CORRECTLY CONFIGURED TO USE GOOGLE PLAY GAME SERVICES 02-26 16:56:27.500 4982 9551 E SignInAuthenticator: \*\*\*\* This is usually caused by one of these reasons: 02-26 16:56:27.500 4982 9551 E SignInAuthenticator: \*\*\*\* (1) Your package name and certificate fingerprint do not match 02-26 16:56:27.500 4982 9551 E SignInAuthenticator: \*\*\*\* the client ID you registered in Developer Console. 02-26 16:56:27.500 4982 9551 E SignInAuthenticator: \*\*\*\* (2) Your App ID was incorrectly entered. 02-26 16:56:27.500 4982 9551 E SignInAuthenticator: \*\*\*\* (3) Your game settings have not been published and you are 02-26 16:56:27.500 4982 9551 E SignInAuthenticator: \*\*\*\* trying to log in with an account that is not listed as 02-26 16:56:27.500 4982 9551 E SignInAuthenticator: \*\*\*\* a test account.

with adb logcat. My SHA-1 is entered correctly. The package name is right and the app ID. Also my account in a beta tester (don’t think that would matter as this is already published , I’m just trying to add leaderboards in in an update)

#5

I and some more people seem to have similar issues, there’s a thread in the game networking part of the forum about this as well. From what I can see all requests to the drive api results in errors. Not sure why.

#6

Yeah I’m having the same issue but my Google Play Games Services API is throwing all of the errors and not my Google Drive API. My GPGS API says it has 43 requests and the error(%) is at 100.

#7

Also I get this in the console

02-26 16:56:27.499 4982 9551 E SignInAuthenticator: \*\*\*\* 02-26 16:56:27.500 4982 9551 E SignInAuthenticator: \*\*\*\* APP NOT CORRECTLY CONFIGURED TO USE GOOGLE PLAY GAME SERVICES 02-26 16:56:27.500 4982 9551 E SignInAuthenticator: \*\*\*\* This is usually caused by one of these reasons: 02-26 16:56:27.500 4982 9551 E SignInAuthenticator: \*\*\*\* (1) Your package name and certificate fingerprint do not match 02-26 16:56:27.500 4982 9551 E SignInAuthenticator: \*\*\*\* the client ID you registered in Developer Console. 02-26 16:56:27.500 4982 9551 E SignInAuthenticator: \*\*\*\* (2) Your App ID was incorrectly entered. 02-26 16:56:27.500 4982 9551 E SignInAuthenticator: \*\*\*\* (3) Your game settings have not been published and you are 02-26 16:56:27.500 4982 9551 E SignInAuthenticator: \*\*\*\* trying to log in with an account that is not listed as 02-26 16:56:27.500 4982 9551 E SignInAuthenticator: \*\*\*\* a test account.

with adb logcat. My SHA-1 is entered correctly. The package name is right and the app ID. Also my account in a beta tester (don’t think that would matter as this is already published , I’m just trying to add leaderboards in in an update)