Google Play Sign In

1 favourites
  • 7 posts
From the Asset Store
Game with complete Source-Code (Construct 3 / .c3p) + HTML5 Exported
  • So I have integrated google play into my game, and I use "Sign in" at the start of my game, then I request the player details. It works fine on my debug APK.

    The second time I start the game... I'm already signed in.. so if I request the player details... it doesn't work. I have to manually sign out the player and sign in again which is a bad practice since the google play menu will appear every time I start the game.

    How can I request the player details successfully if it's already signed in? Does anyone have an idea?

    Weird that it's working fine on some devices, while on others it's not

  • You can't just ask for player data like that.

    There is a trigger event when a player logged in after triggering it, you can ask for it.

    -There is an additional condition when a player entered after the check you can also ask for data.

    Everything is written there, you just need to read the description of the events.

  • igortyhon

    I think I did set it the correct way.

    Kindly bear with me... so I have 2 texts, T1 and T2

    T1 will update its text from "Awaiting sign in" to "Signed in SUCCESS, requesting..." then to "Player data received" upon the trigger "On signed in" from google play.

    T2 only updates whether the user is currently signed in or not.

    But now even tho the player is signed in (after the second launch of the APK), T2 does detect that the user is signed in.

    But T1 is never updated, meaning the "On signed in" is never triggered...

  • To make it simple.

    If the player is already signed in on start of the game, "On signed in" is never triggered.

    After waiting a bit... even if I manually request player details, it won't work.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads
  • But T1 is never updated, meaning the "On signed in" is never triggered...

    The second time with a good internet connection, the plugin input may occur before the sheet is loaded. That is why the input trigger does not work.

    Try this optimized variant. You will have a group after triggering of which it disables itself for optimization.

  • igortyhon

    Hey, I added that but it still didn't work, thanks anyway.

    I found the issue tho,

    The solution is on my next reply.

  • igortyhon

    Issue happened again but I got to know the real problem

    I was dumb so I didn't know I had to re-create a new OAuth Client ID using the SHA-1 certificate fingerprint (from App Integrity tab) after uploading as an app bundle. It was working before on the debug APK because of the initial SHA-1 provided by the engine.

    (I might have wrongly described my issue on top, since I was confused)

    (╯°□°)╯︵ ┻━┻

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)