CodetrixStudio / CapacitorGoogleAuth

Capacitor plugin for Google Auth. Lightweight & no dependencies.
MIT License
284 stars 158 forks source link

Getting error Something went wrong, code: 10 #291

Open mohamednagy opened 1 year ago

mohamednagy commented 1 year ago

I'm trying to use this package for google sign in. I'm always getting this error

{"save":false,"callbackId":"40115251","pluginId":"GoogleAuth","methodName":"signIn","success":false,"error":{"message":"Something went wrong","code":"10"}}

I tried to follow the documentation as is, here is my configurations:

capacitor.config.json

{
  "appId": "io.ionic.nostashteeb",
  "appName": "Nos Tashteeb",
  "webDir": "dist",
  "bundledWebRuntime": false,
  "plugins": {
    "GoogleAuth": {
      "scopes": ["profile", "email"],
      "iosClientId": "",
      "clientId": "CLIENT_ID.apps.googleusercontent.com",
      "androidClientId": "CLIENT_ID.apps.googleusercontent.com",
      "serverClientId": "CLIENT_ID.apps.googleusercontent.com",
      "forceCodeForRefreshToken": true
    }
  }
}

strings.xml

<string name="server_client_id">CLIENT_ID.apps.googleusercontent.com</string>

MainActivity

registerPlugin(
                com.codetrixstudio.capacitor.GoogleAuth.GoogleAuth.class
        );

and then within my vue application using as

try {
const response = await GoogleAuth.signIn();
} catch (error) {

}

I created my client_id from the google cloud console and copied my SHA1 to the google cloud console but still always getting this error.

capacitor: ^5.1.0 @codetrix-studio/capacitor-google-auth: ^3.3.2

sunda-amami commented 1 year ago

I'm facing same issue.

sunda-amami commented 1 year ago

This error is the same as error #87.

This error code indicates an issue caused by the developer. Check if your client_id is valid. Verify that the fingerprint of the debug.keystore has been registered in the Firebase project settings. If it is not, redownload and replace the google-services.json file.

Diog0-0 commented 1 year ago

i have the same problem, i really try so many things, can help me ?

my config.json :

 "plugins": {
    "GoogleAuth": {
      "scopes": ["profile", "email"],
      "androidClientId": "ANDROID_APP_clientid",
      "forceCodeForRefreshToken": true
    }
  },

strings.xml

<string name="server_client_id">CLIENT_ID.apps.googleusercontent.com</string>

i don't know if i need a other cliendID, i see some peoples say for use the web_client_id and not the android_app_client_id, but don't work too :/.

What i can do ?

stevegtdbz commented 1 year ago

I have exactly the same issue. It seems that google deprecated a module that this repo built on and cannot work anymore.

https://developers.google.com/identity/gsi/web/guides/migration

Diog0-0 commented 1 year ago

in this case i think, dont have other manner to use in a hibryd app(capacitor with ionic) ? In this guide i only see java codes in gradle. Maybe exists some plugin ? like capacitors plugins or ionics components ?

OnlinePage commented 1 year ago

same issue here as well😔, @reslear

sajjadalis commented 1 year ago

Same issue. banging my head against the wall for the last few hours. Thought I was doing something wrong.

Diog0-0 commented 1 year ago

i think we can use the basic method maybe ? instead of using a plugin we can using the firebase method open in browser of phone ? I try to use the browser for this but the browser can't back to the app after the authentication, someboy know something about this ?

OnlinePage commented 1 year ago

finally after 43 hrs continuous real struggle, me fixed it😃🥳👯🎈🎉🎊

stevegtdbz commented 1 year ago

How? You managed to make it work on android device too?

Please share the solution, big headaches here too..

OnlinePage commented 1 year ago

@stevegtdbz ya ya in understand pal, my issue was my sha1 key was different than that i added on firebase for google auth. I am using google auth. Also ensure you have added androidClientId specifcally for android in your capacitor config file. I m pretty sure this will work for you!! See bascially what i understood is code error 10is totally related developer side issue, I have seen number of people already using this and succeed using the this google auth. Also google identiy is diffrerent and current auth is still supported , so currently we don't need worry about migration!

sajjadalis commented 1 year ago

Has anyone else got it working with the purposed solution? This GoogleAuth plugin should work independently if I'm not mistaken. How Firebase SHA1 is related to this. I tried with Firebase, provided SHA1, but still the same error.

stevegtdbz commented 1 year ago

@stevegtdbz ya ya in understand pal, my issue was my sha1 key was different than that i added on firebase for google auth. I am using google auth. Also ensure you have added androidClientId specifcally for android in your capacitor config file. I m pretty sure this will work for you!! See bascially what i understood is code error 10is totally related developer side issue, I have seen number of people already using this and succeed using the this google auth. Also google identiy is diffrerent and current auth is still supported , so currently we don't need worry about migration!

Thanks for the response. The old google api seems to work only for api keys that generated before of july 22.

Check the warning message here https://developers.google.com/identity/sign-in/web/sign-in

For new keys, as far as i understand, it requires to implement gis.

OnlinePage commented 1 year ago

@stevegtdbz ya ya in understand pal, my issue was my sha1 key was different than that i added on firebase for google auth. I am using google auth. Also ensure you have added androidClientId specifcally for android in your capacitor config file. I m pretty sure this will work for you!! See bascially what i understood is code error 10is totally related developer side issue, I have seen number of people already using this and succeed using the this google auth. Also google identiy is diffrerent and current auth is still supported , so currently we don't need worry about migration!

Thanks for the response. The old google api seems to work only for api keys that generated before of july 22.

Check the warning message here https://developers.google.com/identity/sign-in/web/sign-in

For new keys, as far as i understand, it requires to implement gis.

But my api keys are created a week agao🤔 and it's working.

OnlinePage commented 1 year ago

But yeah, the google is upgarding it's policy and auth process , so @reslear , we need to also upgrade with it in near future! Who knows when it completly stops working!!

Diog0-0 commented 1 year ago

@OnlinePage can you send an example of code ? i tried all this things and dont work for me :/. I will try to see the keys again, but I already add my SHA1 in app, which key i need put in androidClientId ? You catch the key from google-services.json ? in this file have client_type 1 and client_type 3 i think...

reslear commented 1 year ago

@OnlinePage please answer https://github.com/CodetrixStudio/CapacitorGoogleAuth/issues/202#issuecomment-1666532128

riderx commented 1 year ago

Make it work on my side by using serverClientId with "client_type": 3 client_id ( the web one, not native one WTF)

stevegtdbz commented 1 year ago

After many days of searching & troubleshooting, it finally worked for me too!

In my case, firebase is no needed.. i am just getting the "id_token" and sending it to my backend.. then i verify the token and grand access to my user.. so here is what followed:

1) Google console setup Create a web application

Create an android application (i know make no sense)

2) capacitor.config.ts

plugins: {
    GoogleAuth: {
      scopes: ['profile', 'email'],
      clientId: config.GOOGLE_CLIENT_ID,
      androidClientId: config.GOOGLE_CLIENT_ID,
      serverClientId: config.GOOGLE_CLIENT_ID,
    },
  },

3) Angular component

GoogleAuth.initialize({
      clientId: config.GOOGLE_CLIENT_ID,
      scopes: ['profile', 'email'],
})
async googleSignIn() {
    let googleUser = await GoogleAuth.signIn();
    //todo
}

** On android project have only registered the plugin, nothing else registerPlugin(com.codetrixstudio.capacitor.GoogleAuth.GoogleAuth.class);

@OnlinePage You had right! I also used a new key and worked fine! but i also found another one from an old project in case google decides to shut down the new ones (as per their warnings) :p

OnlinePage commented 1 year ago

After many days of searching & troubleshooting, it finally worked for me too!

In my case, firebase is no needed.. i am just getting the "id_token" and sending it to my backend.. then i verify the token and grand access to my user.. so here is what followed:

1) Google console setup Create a web application

  • Set into "Authorized JavaScript origins" & "Authorized redirect URIs" -> http://localhost to be able to test from your browser too, just add your serve port like http://localhost:4200
  • On "Publishing status" set "in production"
  • Now get the web_cllient_id and use it below on each config.GOOGLE_CLIENT_ID reference below

Create an android application (i know make no sense)

  • Set Name & Package name.
  • For the SHA1 go to android studio and use this one keytool -list -v -keystore ~/.android/debug.keystore -alias androiddebugkey -storepass android -keypass android

2) capacitor.config.ts

plugins: {
    GoogleAuth: {
      scopes: ['profile', 'email'],
      clientId: conf.GOOGLE_CLIENT_ID,
      androidClientId: conf.GOOGLE_CLIENT_ID,
      serverClientId: conf.GOOGLE_CLIENT_ID,
    },
  },

3) Angular component

GoogleAuth.initialize({
      clientId: config.GOOGLE_CLIENT_ID,
      scopes: ['profile', 'email'],
})
async googleSignIn() {
    let googleUser = await GoogleAuth.signIn();
    //todo
}

** On android project have only registered the plugin, nothing else registerPlugin(com.codetrixstudio.capacitor.GoogleAuth.GoogleAuth.class);

@OnlinePage You had right! I also used a new key and worked fine! but i also found another one from an old project in case google decides to shut down the new ones (as their warnings) :p

Glad it worked !! 🥳. Ahhh... Google and it's policies😔

OnlinePage commented 1 year ago

@OnlinePage can you send an example of code ? i tried all this things and dont work for me :/. I will try to see the keys again, but I already add my SHA1 in app, which key i need put in androidClientId ? You catch the key from google-services.json ? in this file have client_type 1 and client_type 3 i think...

i guess @stevegtdbz answer is guide for you

SourabhKardile commented 1 year ago

ERROR Error: Uncaught (in promise): Error: Something went wrong Error: Something went wrong at returnResult (VM3:849) at Object.win.androidBridge.onmessage (VM3:824) at q (polyfills.ea3cb635cad86c66.js:1) at polyfills.ea3cb635cad86c66.js:1 at polyfills.ea3cb635cad86c66.js:1 at y (main.589666d56b13e81b.js:1) at ve (main.589666d56b13e81b.js:1) at v.invoke (polyfills.ea3cb635cad86c66.js:1) at Object.onInvoke (main.589666d56b13e81b.js:1) at v.invoke (polyfills.ea3cb635cad86c66.js:1) at M.run (polyfills.ea3cb635cad86c66.js:1) at polyfills.ea3cb635cad86c66.js:1

I tried everything still nothing is happening plz help me:)

matbravob commented 1 year ago

I solved it by using the SHA1 from the Android Studio Terminal when running this command "./gradlew signingReport" I got it from the google docs: https://developers.google.com/android/guides/client-auth

viktorisacenko commented 1 year ago

For me, the problem solved by using all 3:

clientId: google_web_client_id,
androidClientId: google_web_client_id,
serverClientId: google_web_client_id,

....

itsalb3rt commented 1 year ago

After many days of searching & troubleshooting, it finally worked for me too!

In my case, firebase is no needed.. i am just getting the "id_token" and sending it to my backend.. then i verify the token and grand access to my user.. so here is what followed:

1) Google console setup Create a web application

  • Set into "Authorized JavaScript origins" & "Authorized redirect URIs" -> http://localhost ( to be able to test from your browser too, just add your serve port like http://localhost:4200 )
  • On "Publishing status" set "in production"
  • Now get the web_cllient_id and use it below on each config.GOOGLE_CLIENT_ID reference below

Create an android application (i know make no sense)

  • Set Name & Package name.
  • For the SHA1 go to android studio and use this one keytool -list -v -keystore ~/.android/debug.keystore -alias androiddebugkey -storepass android -keypass android

2) capacitor.config.ts

plugins: {
    GoogleAuth: {
      scopes: ['profile', 'email'],
      clientId: config.GOOGLE_CLIENT_ID,
      androidClientId: config.GOOGLE_CLIENT_ID,
      serverClientId: config.GOOGLE_CLIENT_ID,
    },
  },

3) Angular component

GoogleAuth.initialize({
      clientId: config.GOOGLE_CLIENT_ID,
      scopes: ['profile', 'email'],
})
async googleSignIn() {
    let googleUser = await GoogleAuth.signIn();
    //todo
}

** On android project have only registered the plugin, nothing else registerPlugin(com.codetrixstudio.capacitor.GoogleAuth.GoogleAuth.class);

@OnlinePage You had right! I also used a new key and worked fine! but i also found another one from an old project in case google decides to shut down the new ones (as per their warnings) :p

Work for me thanks! in my case I see I put the IOS client id on the serverClientId lol

OnlinePage commented 1 year ago

After many days of searching & troubleshooting, it finally worked for me too!

In my case, firebase is no needed.. i am just getting the "id_token" and sending it to my backend.. then i verify the token and grand access to my user.. so here is what followed:

1) Google console setup Create a web application

  • Set into "Authorized JavaScript origins" & "Authorized redirect URIs" -> http://localhost ( to be able to test from your browser too, just add your serve port like http://localhost:4200 )
  • On "Publishing status" set "in production"
  • Now get the web_cllient_id and use it below on each config.GOOGLE_CLIENT_ID reference below

Create an android application (i know make no sense)

  • Set Name & Package name.
  • For the SHA1 go to android studio and use this one keytool -list -v -keystore ~/.android/debug.keystore -alias androiddebugkey -storepass android -keypass android

2) capacitor.config.ts

plugins: {
    GoogleAuth: {
      scopes: ['profile', 'email'],
      clientId: config.GOOGLE_CLIENT_ID,
      androidClientId: config.GOOGLE_CLIENT_ID,
      serverClientId: config.GOOGLE_CLIENT_ID,
    },
  },

3) Angular component

GoogleAuth.initialize({
      clientId: config.GOOGLE_CLIENT_ID,
      scopes: ['profile', 'email'],
})
async googleSignIn() {
    let googleUser = await GoogleAuth.signIn();
    //todo
}

** On android project have only registered the plugin, nothing else registerPlugin(com.codetrixstudio.capacitor.GoogleAuth.GoogleAuth.class);

@OnlinePage You had right! I also used a new key and worked fine! but i also found another one from an old project in case google decides to shut down the new ones (as per their warnings) :p

Work for me thanks! in my case I see I put the IOS client id on the serverClientId lol

Glad 😊 you got it worked!! Ahhhh! this Google playing with us developers 😢.

srivas-wrr commented 10 months ago

After many days of searching & troubleshooting, it finally worked for me too!

In my case, firebase is no needed.. i am just getting the "id_token" and sending it to my backend.. then i verify the token and grand access to my user.. so here is what followed:

1) Google console setup Create a web application

  • Set into "Authorized JavaScript origins" & "Authorized redirect URIs" -> http://localhost ( to be able to test from your browser too, just add your serve port like http://localhost:4200 )
  • On "Publishing status" set "in production"
  • Now get the web_cllient_id and use it below on each config.GOOGLE_CLIENT_ID reference below

Create an android application (i know make no sense)

  • Set Name & Package name.
  • For the SHA1 go to android studio and use this one keytool -list -v -keystore ~/.android/debug.keystore -alias androiddebugkey -storepass android -keypass android

2) capacitor.config.ts

plugins: {
    GoogleAuth: {
      scopes: ['profile', 'email'],
      clientId: config.GOOGLE_CLIENT_ID,
      androidClientId: config.GOOGLE_CLIENT_ID,
      serverClientId: config.GOOGLE_CLIENT_ID,
    },
  },

3) Angular component

GoogleAuth.initialize({
      clientId: config.GOOGLE_CLIENT_ID,
      scopes: ['profile', 'email'],
})
async googleSignIn() {
    let googleUser = await GoogleAuth.signIn();
    //todo
}

** On android project have only registered the plugin, nothing else registerPlugin(com.codetrixstudio.capacitor.GoogleAuth.GoogleAuth.class);

@OnlinePage You had right! I also used a new key and worked fine! but i also found another one from an old project in case google decides to shut down the new ones (as per their warnings) :p

Thankyou Bro

OnlinePage commented 10 months ago

After many days of searching & troubleshooting, it finally worked for me too!

In my case, firebase is no needed.. i am just getting the "id_token" and sending it to my backend.. then i verify the token and grand access to my user.. so here is what followed:

1) Google console setup Create a web application

  • Set into "Authorized JavaScript origins" & "Authorized redirect URIs" -> http://localhost ( to be able to test from your browser too, just add your serve port like http://localhost:4200 )
  • On "Publishing status" set "in production"
  • Now get the web_cllient_id and use it below on each config.GOOGLE_CLIENT_ID reference below

Create an android application (i know make no sense)

  • Set Name & Package name.
  • For the SHA1 go to android studio and use this one keytool -list -v -keystore ~/.android/debug.keystore -alias androiddebugkey -storepass android -keypass android

2) capacitor.config.ts

plugins: {
    GoogleAuth: {
      scopes: ['profile', 'email'],
      clientId: config.GOOGLE_CLIENT_ID,
      androidClientId: config.GOOGLE_CLIENT_ID,
      serverClientId: config.GOOGLE_CLIENT_ID,
    },
  },

3) Angular component

GoogleAuth.initialize({
      clientId: config.GOOGLE_CLIENT_ID,
      scopes: ['profile', 'email'],
})
async googleSignIn() {
    let googleUser = await GoogleAuth.signIn();
    //todo
}

** On android project have only registered the plugin, nothing else registerPlugin(com.codetrixstudio.capacitor.GoogleAuth.GoogleAuth.class);

@OnlinePage You had right! I also used a new key and worked fine! but i also found another one from an old project in case google decides to shut down the new ones (as per their warnings) :p

Thankyou Bro 😎 Cool you figured it out .

elhombrej commented 9 months ago

I had this problem and followed all steps from @stevegtdbz but did not work until i specified a difrent port on the front end rather than http://localhost, i changed it for http://localhost:8100 and worked!

Saibotig commented 8 months ago

This error is the same as error #87.

This error code indicates an issue caused by the developer. Check if your client_id is valid. Verify that the fingerprint of the debug.keystore has been registered in the Firebase project settings. If it is not, redownload and replace the google-services.json file.

Signing the apk with the wrong fingerprint (keystore) resolved the issue for me. This error can have several reasons, check everything.

reslear commented 8 months ago

Maybe someone can add a PR faq section to the README with this problem?

mumair4462 commented 7 months ago

i solve this error using the following steps:

  1. create firebase project
  2. enable email authentications
  3. add android app with sh1 key setup
  4. add web app
  5. install firebase or @codetrix-studio/capacitor-google-auth plugin
  6. go to google cloud console and open your firebase project which you created
  7. in Credentials > OAuth 2.0 Client IDs - copy web client

your component.ts code:

plateform: any; constructor() { if (!isPlatform('capacitor')) { GoogleAuth.initialize({ clientId: '', scopes: ['profile', 'email'], }); } } ngOnInit() { }

initialize() { this.plateform.ready().then(() => { GoogleAuth.initialize() }) }

//call this ftn in html async login() {

try {
  const user = await GoogleAuth.signIn();
  if (user) {
    console.log(user);
    alert("Success")
  }

} catch (error: any) {
  console.log(error);
  alert(JSON.stringify(error))

}

capacitor.conflt.ts

plugins: { GoogleAuth: { scopes: ['profile', 'email'], clientId: "", androidClientId: "", serverClientId: "", },

MainActivity.Java (import all packages)

@Override protected void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); registerPlugin(GoogleAuth.class); }

string.xml: "string name="server_client_id"></string">

index.html: "meta name="google-signin-client_id" content="" />

past google-services file download form firebase in android/app directory

REMEMBER ME IN YOUR PRAYERS

dutypro commented 7 months ago

I was stuck on this issue for a couple of days but managed to fix it with the help of this tutorial: https://www.youtube.com/watch?v=GwtpoWZ_78E&ab_channel=SimonGrimm

Essentially it looks like the issue is somehow at Google's end. You need to have both Android and Web credentials set up but will use the Web credentials in your app. There's not really any reason for the issue but it would appear it needs the SHA1 information for the Web to work... bizarre situation I know!

Hope it helps.

shahidkarimi commented 7 months ago

Only for God this thing might work.

xbaldiq commented 6 months ago

in my case, because i still in development, i need to use variant: DEBUG for SHA-1, and set it in android native OAuth 2.0 Client ID

i'm check it with: cd android && ./gradlew signInReport

Raja-Malli-Dileep-Vadde commented 6 months ago

Actually, i am also totally confused about google signing in ionic app but, i got to know solution by several tries , i finally discovered that the debug keystore SHA1 only works in the emulator Here, https://github.com/CodetrixStudio/CapacitorGoogleAuth/issues/332#issuecomment-2098010545

Raja-Malli-Dileep-Vadde commented 6 months ago

Only for God this thing might work.

Actually, i am also totally confused about google signing in ionic app but, i got to know solution by several tries, i finally discovered that the debug keystore SHA1 only works in the emulator Here, https://github.com/CodetrixStudio/CapacitorGoogleAuth/issues/332#issuecomment-2098010545

Raja-Malli-Dileep-Vadde commented 6 months ago

Actually, i am also totally confused about google signing in ionic app but, i got to know solution by several tries , i finally discovered that the debug keystore SHA1 only works in the emulator Here, https://github.com/CodetrixStudio/CapacitorGoogleAuth/issues/332#issuecomment-2098010545

Raja-Malli-Dileep-Vadde commented 6 months ago

i'm check it with: cd android && ./gradlew signInReport

https://github.com/CodetrixStudio/CapacitorGoogleAuth/issues/332#issuecomment-2098010545

Raja-Malli-Dileep-Vadde commented 6 months ago

I was stuck on this issue for a couple of days but managed to fix it with the help of this tutorial: https://www.youtube.com/watch?v=GwtpoWZ_78E&ab_channel=SimonGrimm

Essentially it looks like the issue is somehow at Google's end. You need to have both Android and Web credentials set up but will use the Web credentials in your app. There's not really any reason for the issue but it would appear it needs the SHA1 information for the Web to work... bizarre situation I know!

Hope it helps.

https://github.com/CodetrixStudio/CapacitorGoogleAuth/issues/332#issuecomment-2098010545

Raja-Malli-Dileep-Vadde commented 6 months ago

This error is the same as error #87. This error code indicates an issue caused by the developer. Check if your client_id is valid. Verify that the fingerprint of the debug.keystore has been registered in the Firebase project settings. If it is not, redownload and replace the google-services.json file.

Signing the apk with the wrong fingerprint (keystore) resolved the issue for me. This error can have several reasons, check everything.

https://github.com/CodetrixStudio/CapacitorGoogleAuth/issues/332#issuecomment-2098010545

sertal70 commented 5 months ago

In my case, after having applied all suggestions collected here and in other related issue, the sign-in on android started to work when I used the web client id instead of android client id.

I can live with that, but... can anyone explain me why???

lsantaniello commented 5 months ago

I cant found my issue. Please help me {message: 'Something went wrong', code: '10'}

arielhasidim commented 5 months ago

@stevegtdbz ya ya in understand pal, my issue was my sha1 key was different than that i added on firebase for google auth. I am using google auth. Also ensure you have added androidClientId specifcally for android in your capacitor config file. I m pretty sure this will work for you!! See bascially what i understood is code error 10is totally related developer side issue, I have seen number of people already using this and succeed using the this google auth. Also google identiy is diffrerent and current auth is still supported , so currently we don't need worry about migration!

As @OnlinePage mentioned, this was the problem for me also. See here for another explanation and with screenshots: https://github.com/CodetrixStudio/CapacitorGoogleAuth/issues/332#issuecomment-2145794691

lsantaniello commented 5 months ago

I am very frustrated. I've read so many messages and I can't resolve the problem. can someone help me? I'm willing to pay

itsalb3rt commented 4 months ago

@lsantaniello 🤙

mumair4462 commented 4 months ago

I am experiencing considerable frustration as I have read numerous messages but have been unable to resolve my issue. I would appreciate any assistance, and I am willing to compensate for the help.

@isantaniello, could you please follow the steps outlined in this link:- https://github.com/CodetrixStudio/CapacitorGoogleAuth/issues/291#issuecomment-2031629502? Additionally, please verify your Capacitor version, as this issue might be related to a version mismatch. I encountered a similar problem, which was resolved after switching to Capacitor version 5 and following the specified steps.

pedroshift commented 4 months ago

For those getting problems about it, I recommend the mix between @OnlinePage solutions and this video: https://www.youtube.com/watch?v=GwtpoWZ_78E&ab_channel=SimonGrimm

It really makes understand what's going on in this process that for Android is quite weird!

In the end, my dev env works fine, but I am facing a problem only when sending it to PlayStore... I generated the signed APK using production fingerprint, and it runs smoothly on my device, but when generating the App bundle (.aab) using exactly same production fingerprint and sending it to PlayStore, my google login does not work anymore! :(

I can't really understand why .apk and .aab both signed with same production fingerprint work differently! Someone had experience of publishing an App using it and can help me?

pedroshift commented 4 months ago

For those getting problems about it, I recommend the mix between @OnlinePage solutions and this video: https://www.youtube.com/watch?v=GwtpoWZ_78E&ab_channel=SimonGrimm

It really makes understand what's going on in this process that for Android is quite weird!

In the end, my dev env works fine, but I am facing a problem only when sending it to PlayStore... I generated the signed APK using production fingerprint, and it runs smoothly on my device, but when generating the App bundle (.aab) using exactly same production fingerprint and sending it to PlayStore, my google login does not work anymore! :(

I can't really understand why .apk and .aab both signed with same production fingerprint work differently! Someone had experience of publishing an App using it and can help me?

PlayStore problem fixed!!! I created a new OAuth - Type Android, using Fingerprint of "App Signing Key Certificate" (SHA-1)

Summarizing: -> At Google Cloud Console, create OAuth type: Web Application and use it to everything in your code! (See video above to get all needed places... it's a lot)

-> Back to Google Cloud Console, create accordingly OAuth(s) type: Android, that won't be used anywhere by you but they need to be there, created and configured since Google needs it to proceed their validations and authorize Login. To make it work properly on every environment, follow:

MuscledGeek commented 3 months ago

After many days of searching & troubleshooting, it finally worked for me too! In my case, firebase is no needed.. i am just getting the "id_token" and sending it to my backend.. then i verify the token and grand access to my user.. so here is what followed: 1) Google console setup Create a web application

  • Set into "Authorized JavaScript origins" & "Authorized redirect URIs" -> http://localhost to be able to test from your browser too, just add your serve port like http://localhost:4200
  • On "Publishing status" set "in production"
  • Now get the web_cllient_id and use it below on each config.GOOGLE_CLIENT_ID reference below

Create an android application (i know make no sense)

  • Set Name & Package name.
  • For the SHA1 go to android studio and use this one keytool -list -v -keystore ~/.android/debug.keystore -alias androiddebugkey -storepass android -keypass android

2) capacitor.config.ts

plugins: {
    GoogleAuth: {
      scopes: ['profile', 'email'],
      clientId: conf.GOOGLE_CLIENT_ID,
      androidClientId: conf.GOOGLE_CLIENT_ID,
      serverClientId: conf.GOOGLE_CLIENT_ID,
    },
  },

3) Angular component

GoogleAuth.initialize({
      clientId: config.GOOGLE_CLIENT_ID,
      scopes: ['profile', 'email'],
})
async googleSignIn() {
    let googleUser = await GoogleAuth.signIn();
    //todo
}

** On android project have only registered the plugin, nothing else registerPlugin(com.codetrixstudio.capacitor.GoogleAuth.GoogleAuth.class); @OnlinePage You had right! I also used a new key and worked fine! but i also found another one from an old project in case google decides to shut down the new ones (as their warnings) :p

Glad it worked !! 🥳. Ahhh... Google and it's policies😔

Worked like a charm. Thank you. In my case adding android app did it.