Android Google Play Games login fails. (Google Play services)

Discussion in 'Legacy GameMaker Community Tech Support' started by Schekhovtsov, Feb 10, 2019.

  1. Schekhovtsov

    Schekhovtsov Member

    Joined:
    Feb 8, 2019
    Posts:
    5
    Help please! The application is loaded into the developer console. The application is published in internal testing. The group with testers is activated. Settings published, services published.

    The SHA1 key from GMS was copied to the console when the application was loaded.

    In the game to check the authorization, the player's name is displayed on the screen (PlayerName = async_load [? "Name"]; the default is "Anon"). When you start the game, the Google Play Games splash screen is displayed. I choose my account. Loading (rotating circle). After loading, the player's name is changed to "Not logged in".

    I want to attach a full log, but I have no rights to attach a link

    Excerpt from the log:

    3221 8167 E SignInAuthenticator: **** APP NOT CORRECTLY CONFIGURED TO USE GOOGLE PLAY GAME SERVICES
    3221 8167 E SignInAuthenticator: **** This is usually caused by one of these reasons:
    3221 8167 E SignInAuthenticator: **** (1) Your package name and certificate fingerprint do not match
    3221 8167 E SignInAuthenticator: **** the client ID you registered in Developer Console.
    3221 8167 E SignInAuthenticator: **** (2) Your App ID was incorrectly entered.
    3221 8167 E SignInAuthenticator: **** (3) Your game settings have not been published and you are
    3221 8167 E SignInAuthenticator: **** trying to log in with an account that is not listed as
    3221 8167 E SignInAuthenticator: **** a test account.
    3221 8167 E SignInAuthenticator: ****
    3221 8167 E SignInAuthenticator: **** To help you debug, here is the information about this app
    3221 8167 E SignInAuthenticator: **** Package name : com.***.***
    3221 8167 E SignInAuthenticator: **** Cert SHA1 fingerprint: 4F********D0
    3221 8167 E SignInAuthenticator: **** App ID from manifest : 51*******38
    3221 8167 E SignInAuthenticator: ****
    3221 8167 E SignInAuthenticator: **** Check that the above information matches your setup in
    3221 8167 E SignInAuthenticator: **** Developer Console. Also, check that you're logging in with the
    3221 8167 E SignInAuthenticator: **** right account (it should be listed in the Testers section if
    3221 8167 E SignInAuthenticator: **** your project is not yet published).
    3221 8167 E SignInAuthenticator: ****
    3221 8167 E SignInAuthenticator: **** For more information, refer to the troubleshooting guide:


    In the beginning thought that the problem was SHA1. Later abandoned this idea. App ID is correct.

    P.S. In-app purchases are functioning successfully
     
    Last edited: Feb 10, 2019
  2. Schekhovtsov

    Schekhovtsov Member

    Joined:
    Feb 8, 2019
    Posts:
    5
    Replaced keys according to one guide (sha1 from log to api settings in console)

    The error from the log disappeared, but the overall situation in the game has not changed.
     
  3. Schekhovtsov

    Schekhovtsov Member

    Joined:
    Feb 8, 2019
    Posts:
    5
    The only thing that I discovered:

    02-13 19:36:45.722 13302 13302 I yoyo : Login failed! Exception: com.google.android.gms.common.api.ApiException: 8:
     
  4. Mert

    Mert Member

    Joined:
    Jul 20, 2016
    Posts:
    234
    Just a note, do not use this extension and wait for Yoyogames to update it. Currently, Google is removing Google+ and its APIs which the current extension uses and they'll all be completely shut down in March.
     
  5. Nocturne

    Nocturne Friendly Tyrant Forum Staff Admin

    Joined:
    Apr 13, 2016
    Posts:
    6,406
    What minimum API level are you targeting? You should have this set to at least 14, but iirc, 16 is the best. And build using API 28 as the target API.
     
  6. Schekhovtsov

    Schekhovtsov Member

    Joined:
    Feb 8, 2019
    Posts:
    5
    Apk was build with API 28
     
  7. Schekhovtsov

    Schekhovtsov Member

    Joined:
    Feb 8, 2019
    Posts:
    5

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice