search

googlesamples / google-signin-unity

Google Sign-In API plugin for Unity game engine. Works with Android and iOS.
Other
424 stars 229 forks source link

I got "Got Error: DeveloperError Exception of type 'Google.GoogleSignIn+SignInException' was thrown." with right ClientID #173

Open lunargameskr opened 3 years ago

lunargameskr commented 3 years ago

I'm using Unity 2019.4.12f1

First, I checked my ClientID so much, at firebase console, Google API Credentials , and SigninSampleScript.cs

all same. I know there is coufusing OAuth IDs at Google APIs, but I choose right one. (that (Auto-created for google Sign-in) one , and client_type =3 at google-service.json from firebase.)

and my package name is 'com.DefaultCompany.MNGLogintest' also right at firebase console, and I got SHA1 fingerprint from my private keystore. which is named 'user.keystore'

I checked all package name, clientID, client secret , SHA1 fingerprint, and they are all same.

I can't find any other reason that I always get that 'DeveloperError'

why

rcstamp commented 3 years ago

Make sure your PlayServicesResolver has got all dependancies

KajG commented 3 years ago

I had the same thing, make sure when you hardcode your webclient id code to make the variable private, or put the string in the editor inspector window, because when it's public it's going to overwrite your hardcoded web client id to the one in the inspector.

geoseong commented 3 years ago

for my case, the value of webClientId had empty space at the end of the endpoint 😅. after I remove the empty space, the error disappears.

tdx110 commented 1 year ago

You have Error like: "got error developer error exception of type 'google.googlesignin+signin exception' was thrown"? Problem solved. I wrote everywhere I can about the solution. APK and AAB file have different SHA1 and SHA256. In Firebase, it's best to add SHA for both applications. You can check the SHA from the AAB file in Google Play Console -> Your application -> Configuration -> Application integrity -> Application signing. I added these SHA keys to Firebase and the problem was gone.

32nguyen commented 4 days ago

For future me, hope someone finds this useful.

I could not add SHA1 for both firebase app and OAuth Client 2.0 on google cloud console (some tutorial made make confused if I had to need both) since it will be conflict (this may be a new update, idk), adding 2 different SHA1s will lead to 2 different WebClientID for OAuth Client 2.0 on google cloud console and firebase Auth.

Confirm that the firebase Authentication will generate OAuth Client 2.0 for it owns and the WebClientID firebase Auth is enough.