Google Sign In error 12500

Question

I am trying to integrate Google Sign In into my app. I don\'t have a back-end server, I am just getting the details of the logged on Google Account to my app.

I firs

Answer 1

Make sure you have following things set up properly:

1. Generate Client Id in your Google Project.
2. Provide proper SHA-1 key for that Client Id. (debug / release)
3. Provide proper package name for that Client Id.
4. Make sure you have generated Client Id in strings.xml, google-services.json or credentials.json file.

Answer 2

In my case, the issue was that my emulator did not have Play Store. I have made the emulator (named API 23) through Visual Studio, because I develop using Xamarin.Forms as well, and in Visual Studio's Android Device Manager you can select if your emulator should have Google Play Store.

Had to create an emulator through Android Studio's AVD and ensure that it had Play Store:

Answer 3

Seems your SHA1 is overwritten by Google play store. Check in your google play store, launch panel, under app signing, see if google play has an additional SHA1 added.

And copy that SHA1, add to your relevant place, would do the job.

Answer 4

I was stuck in the Google Login issue since 2 week, finally sorted it well .let me explain the reason. The issue was related with firebase. In firebase , they mentioned a field "support email " as optional . But once i added it (any of your personal email) ,the issue sorted and i got the response . If your getting an error as 12501 , then it is related to settings in your google account.

Answer 5

I think the error came from the Wrong SHA1. Please don't forget that the SHA1 is different between release and debug mode in the android studio. Instead of using keytool to get the SHA1, you can use Gradle project -> Task -> android -> signingReport in the android studio (can open it by menu View -> Toolwindow -> gradle ) to get release and debug SHA1. After that, for easy working, you need to create 2 separate credentials with two SHA1 on google cloud console (google just instruct to create 1 using release SHA1, when we develop it will not work since it uses the debug SHA1).

Answer 6

In my case I was working on a non-production app, the issue was that when creating a project in firebase console, there were issues synchronizing SHA-1 keys back and forth from Firebase & Google developer consoles. So, I decided to create the project first on the Google Developer console, and then select it when creating a new project on Firebase console.

I also made a tutorial for this, that may help you.