-
Notifications
You must be signed in to change notification settings - Fork 158
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Google SignIn Error 12500 #47
Comments
You must update your base play service to 18 I think : #43 |
Its already using the play service 18. notice the line below highlighted one ( |
Other probable causes of error 12500 have to do with settings from OAuth screen but that's not the case because its working fine for iOS and web. So the issue is with android only. |
The plugin use the auth version 18, but seems that the base service is version 17 (check the first stack line) and maybe they're not compatibles. Maybe you have another plugin that use version 17 somewhere |
I think 17 is the latest base version we have.(?) Looking at this https://developers.google.com/android/guides/setup |
Yes, my bad. Maybe, you can try to update to 17.2.1 ? |
It could be a problem with your project support email address or sha-1 you used that is not register in google play console : |
the client ID was generated from developers' console not firebase, so didn't really have to insert any support email there, nor should sha-1 be the issue since we're using web client ID for android, no? |
You must create an android credential with your sha1 despite you use web credential (I already had this problem). |
Got it. What location and filename should I put that in? Asking since that's not mentioned in documentation. |
Don't use it, just create it on the console, and try it. |
this works now. creating the android key in console helped. |
Something has changed over the past 2-3 days that's now causing this problem. Last week this was working fine for me. I've updated to version 2.0.1 (though I was already on version 2.0.0) but to no avail.
The text was updated successfully, but these errors were encountered: