Persistent Problem with Google Play Login on Android (Silent Failure)

Hi everyone,

I'm reaching out to the community and developers after spending several weeks trying to implement Google Sign-In on a native Android build using the official "Google Play" addon, without success. After exhausting every debugging avenue I know of, I'm hoping to find some help here.

Context and Configuration:

Construct 3 Version: r449.2 (Stable)

Target Platform: Android (exported as AAB and distributed via the "Internal Testing" track on Google Play).

Involved Addon: The official "Google Play" C3 addon.

The Problem: "Silent Failure" on Android Device

The issue is simple and baffling: when calling the Google Play -> Sign in action on a physical Android device, absolutely nothing happens.

The native Android account selection dialog does not appear.

The On sign in failed condition does not trigger.

The On sign in success condition does not trigger.

There are no relevant errors in the remote debugger console (chrome://inspect).

I have confirmed with a debug text object that the event containing the Sign in action is firing correctly. The action itself simply seems to fail silently.

Debugging Steps Performed (Without Success):

Based on official documentation and expert guides, I have meticulously verified the entire configuration chain:

Google Cloud & Play Console Configuration:

The OAuth Consent Screen is created and its status is "In Production".

The Play Games Services project is created and "Published".

I have created two separate Android Client IDs in the Google Cloud Console, as the UI does not allow me to add two SHA-1 fingerprints to a single client.

One client is configured with the Upload Key SHA-1 fingerprint.

The other client is configured with the

App Signing Key SHA-1 fingerprint from the Play Console.

I have also created a Web Application Client ID with authorized JavaScript origins (editor.construct.net, etc.).

In the Play Games Services configuration page, I have linked all three Client IDs (the two Android clients and the Web client) to the project.

Construct 3 Configuration:

I have configured the "Google Play" object's properties with the correct corresponding IDs (Application ID, Web Client ID, and the appropriate Android Client ID for the build type).

Build & Testing Process:

I have confirmed that testing in Preview mode does not work (due to CSP errors), so all testing is performed on a physical device.

The app is built as an AAB, uploaded to the "Internal Testing" track, and then downloaded and installed directly from the Play Store on a test device. This ensures the app is signed with the correct "App Signing Key."

I have verified that the Android Client ID used in the C3 properties is the one associated with the "App Signing Key" for these tests.

My Questions for the Community/Developers:

Has anyone experienced a similar "silent failure" with the Google Play addon, where the "Sign in" action does nothing on Android?

Is there a known incompatibility between the construct-play-games-v2 plugin and specific versions of Google Play Services or the Android OS that could cause this behavior?

Regarding the inability to add two SHA-1 fingerprints to a single client in the Google Cloud Console, is creating two separate clients and linking them both the correct workflow?

Thanks in advance for any help or insight you can provide. I'm completely stuck and would appreciate any ideas.

I recently added achievements from Google Play and login to the game.

Didn't encounter any significant problems.

The only inconvenience is that the authorization key is created for Android, and you have to test it on a smartphone; web testing doesn't work.

I know that for web testing services, you can create a separate key for the web, and I did that a long time ago, but this time I was too lazy to do it. I don't understand what could have gone wrong for you, because in the Construct 3 project, you only need to add one event to request login.

To create a key, you need to use the fingerprint of an already signed application, which is very easy to copy in the developer's account, where there is an “application integrity” menu.

There are no problems with plugin version incompatibility either; version 2 services work fine.

Thank igortyhon for your reply.

I don't know what could possibly be wrong with my config, I've been trying for weeks and it just does not work. I was hoping someone had a similar issue and could give me some tips on how to solve it, but to be honest, the main issue is that I get no error shown at all, so it's hard to find what's wrong.

I took screenshots of the main authorization settings.

Please note that I marked in blue where to get the fingerprint for the key.

I marked in green which key data needs to be entered into Construct 3 for authorization. After assembly, it will only work on smartphones. And if you take the fingerprint of an already signed application, then you need to download the already signed APK for testing, which Google will distribute through its market. It can be downloaded in your personal account in the “All App Bundles” section.

I marked it in yellow.

Thank you!! I'll try it right now and let you know if it works.

Nothing, my config was already exactly like you described, and it does absolutely nothing.

I exported the app bundle, uploaded to play console, downloaded the version from the playstore and it just does nothing, no console errors, no new text on my debug object, nothing.

Thanks for your response anyway and for taking the time to help me.

And did you configure everything in Google's game services themselves? Everything should be configured there as well.

Everything is configured. I even used google gemini to help me configure everything, double and triple checked every possible thing. That's why I posted, because I thought someone else might be having the same problem.