Sign-in Failed - Android
See original GitHub issueWhile trying to sign-in, I keep getting the following error.
E/SignInActivity: Google Sign In failed. Status{statusCode=unknown status code: 12501, resolution=null}, null
I suspect it’s the GoogleSignInOptions requestIdToken()
method causing the issue. I changed the string passed as the default_web_client_id
to the credentials of server key auto generated in Google APIs credentials. That doesn’t seem to work either.
Am I missing something, or doing something wrong?
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:17 (3 by maintainers)
Top Results From Across the Web
Can't sign in to your Google Account - Android Help
If you can't sign in to your Google Account in Gmail, Google Drive, Google Play, or elsewhere, select the issue that most closely...
Read more >How To Fix Google Sign In Error On Android - velog
How to Fix Google login error on Android. Existing app cache / data issues - As someone suggested, this can be resolved by...
Read more >Can't sign in to your Google Account - Android Help
If you can't sign in to your Google Account in Gmail, Google Drive, Google Play, or elsewhere, select the issue that most closely...
Read more >Sign in failed on Android phone - Samsung email needs ...
We've seen that you are unable to log in to your Hotmail/Outlook.com account through your Android device. Based on your description, we agree ......
Read more >Why am I getting a message pop up sign-in failed for my email?
I have a galaxy S 5 and i had a pop up as a notification it reads; Sign-in Failed for my email, I'm...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Same error. Any headway?
EDIT: After several hours of looking for a solution, it turns out I had two debug.keystore files and I had tried with both SHA1 values but I dunno whether the app wasn’t updating each time I switched. Anywho, the easiest way to find your actual SHA1 is to do what this video says: https://www.youtube.com/watch?v=m_9tk7ME4ZU
[Basically, in Android Studio, open the Gradle menu on the far right, open android-start from the drop down (refresh if nothing is showing), open Tasks, open android, double click signingReport. ]
Get your SHA1 key from there, and go create a new Firebase project and in the console, use that SHA1 key after clicked “Add firebase to Android”… follow the tutorial from there. Restart your device, and tadaa.
At least for me, it worked, and I’d been at it for hours.
Well finally login , make a new project, after get the sha1 code in Gradle->Android-start->Tasks->singningReports, put the new google-services.json on src folder and uninstall app … Run the project! and voilà , happy coding!