[Android] Google Login says "activity is cancelled by the user"

[jcsilva94]

I am using the latest version of the library. I've followed the migration guide from the codetrix plugin. Web and iOS work just fine. In Android however, whenever I pick any of my configured Google accounts in the popup that appears, regardless whether it is on a physical device or an emulator, I get the below error code over and over again.

I tried different plugin configuration, even the most basic ones, but the error still persists.

What could it be?

Thanks in advance.

[sebastien-closs]

same here
Capacitor 7, Angular 19

[riderx]

do you have account set in the device?

[jcsilva94]

Yes, two accounts actually

[Antonyodu]

I'm having the same issue

[Antonyodu]

[riderx]

can you provide a reproduction repo to let us reproduce?

[tregouetkevin]

I have exactly the same probleme with google auth, capacitor 7 angular 18, but work on IOS.

[riderx]

We will look for it this week but please help but and create a reproduction repo

[tregouetkevin]

@riderx https://gitlab.com/kevin.tregouet/capgo-social-login-test/ i have setup a ionic app with the plugin, code is in /src/app/home directory

ps: si tu as besoin de plus d'informations je suis dispo

[jcsilva94]

Hello, I have extra information that might be helpful:

Today I was making some tests related to my app, and I created a blank emulator from scratch,, without a Google account set up. I opened my app, pressed the "Google SignIn" Button, and the plugin automatically threw this error:

On iOS I cannot reproduce this issue, when I click on Google SignIn and I don't have a Google Account set up, I get promted to add one:

Then the login flow continues as usual and I can login just fine.

Additionaly, on a physical device, it's even weirder. If I happen to have one or two accounts already set up, the login flow works just fine. However, if I add an extra google account, after that, the "activity cancelled by the user" error appears again and all subsequent attempts to sign in with Google will automatically fail, regardless of which account I pick.

[rostislavcz]

Hi guys, i found the solution and its probably not problem of this plugin, the only problem in plugin is, that the error response is not correct.

Note, that you have to create OAuth 2.0 Client in google cloud console first, and note, that you have to create Android Client there for each SHA build you create = if you install app form googlePlay, you will use SHA1 you can find in Google Play Console

But if you just making build via AndroidStudio and install it just with Run 'app' button

In that case you must create new OAuth 2.0 client in google cloud console for android and call in terminal
keytool -list -v -alias androiddebugkey -keystore ~/.android/debug.keystore

which would return you SHA1 fingerprint you have to use in google cloud console (androidstudio is using this debug.keystore by default if you just run the app in android studio). Also if you sign it and just create apk file and do not push it to google play, you have to get SHA1 fingerprint from that .jks file, you sign that app and put it also to google cloud console

keytool -list -v -alias mykey -keystore /path/to/my-release-key.jks

[riderx]

We tried to explain this in the doc for google but i agree it can be unclear, maybe @rostislavcz if you have time i would gladly have your explain added to our doc could do you PR?

[riderx]

please try latest to see if it's better on 7.4.5

[WcaleNieWolny]

Closing for now, it looks like the issue is resolved