Android google sign in developer error

DeveloperError Exception of type ‘Google.GoogleSignIn+SignInException’ was thrown. #51

Comments

Ryu17 commented Jul 10, 2018

I was following the guide and found something different.

«This file contains the client-side information needed to use Google Sign-in. The details on how to do this are documented on the Developer website.»

I entered SHA1 and the package and created a json file by clicking ‘Configure a Project’ through the developer website link, but the file looks different from the guide.

Is it wrong to choose Android from the image above?

The text was updated successfully, but these errors were encountered:

Ryu17 commented Jul 10, 2018

OK, I tried to solve this problem all day and finally solved it.

The above question was not wrong. The ‘Google Sign-In configuration file’ section in README.md is probably a file obtained through firebase. It looks different, but it is not wrong.

https://developers.google.com/identity/sign-in/android/start
Click the CONFIGURE A PROJECT button on this link, select the project, set it to Android, and enter the Package Name and SHA1.
(You need to get into the Player Settings in the Unity Editor, set the Keystore in the Publishing Settings and get the SHA1 value.)

Next, when you click the GOOGLE API CONSOLE button in the above link, there will be two kinds of OAUTH 2.0 CLIENT IDs in the project.

The CLIENT ID we need is ‘Web client (Auto-created for Google Sign-in)’. Enter this CLIENT ID into the webClientId of SigninSampleScript.cs.

Finally, browse keystore in Publishing Settings and build with release. (You should never do Developer Build, I spent a lot of time here.)

I hope this will help you .

toom1984 commented Jul 13, 2018

thanks! helped to clear up stuff for me

torresalmonte commented Oct 12, 2018

Thank you!, you saved the day! This was a very tricky situation.

nphau commented Jan 3, 2019

Agree with Toom, if you need an official guideline, please check here
https://github.com/googlesamples/google-signin-unity

bipinGosain commented Jul 20, 2019 •

Still getting this issue. I’ve cross-checked all of the above. Any other suggestion?

I’m using: a. Unity 2018.1.5f1 b. firebase_unity_sdk_6.2.0 c. google-signin-plugin-1.0.4

Setup a Unity App on Firebase.

Imported both the plugin along with Sample Google Script.

I’m using Google Sample’s Sign In script.

Added a SHA-1 fingerprint from C:\Users\user.android\debug.keystore, to Firebase console.

Downloaded and added googleservices.json to root of the Assets folder.

Used the id from google-services.json OAuth client type 3 to the WebClient ID.

Always getting Google Sign In Exception
NOTE: No third part modules added, just Unity Ads.

Mukikaizoku commented Aug 31, 2019

@Ryu17 Thank you, that information was helpful! I wish that was in the ReadMe

@bipinGosain I’m not 100% certain, but it seems that using a debug.keystore doesn’t work. I had to use the release keystore that I use for my app.

Also, it if you can check if that SignInException has Status=Error vs DeveloperError, that may help figure out what is wrong.

bitCoder0 commented Feb 22, 2020 •

I had this problem recently, hope this note helps someone!
before telling my problem solution, something that you should check are steps mentioned in the @bipinGosain answer:

Still getting this issue. I’ve cross-checked all of the above. Any other suggestions?

I’m using: a. Unity 2018.1.5f1 b. firebase_unity_sdk_6.2.0 c. google-signin-plugin-1.0.4

1. Setup a Unity App on Firebase.
2. Imported both the plugin along with Sample Google Script.
3. I’m using Google Sample’s Sign In script.
4. Added a SHA-1 fingerprint from C:\Users\user.android\debug.keystore, to Firebase console.
5. Downloaded and added googleservices.json to the root of the Assets folder.
6. Used the id from google-services.json OAuth client type 3 to the WebClient ID.
7. Always getting Google Sign In Exception
   NOTE: No third part modules added, just Unity Ads.

and remember to do a release build not debug(just in case)
the key in the json file works but for me id of key type 3 is the secound part of «oauth_client» part in google-services.json
for example:
you should copy bbbbYOURID.apps.googleusercontent.com part of json file not aaaaYOURID.app.. :
my mistake was copying the client id of type 1 not 3

except json file,you can access that id by this way:
go to firebase console>authentication>secound tab(sign in method)>expand the google section>expand the «Web SDK configuration» part>copy the WebClient id
the key worked for me, without making a new key in firebase cloud page or without using the oauth key in the JSON file

Источник

Google Sign in not working on android M #272

Comments

dab13491 commented Oct 26, 2016

Step 1: Are you in the right place?

Google sign in working perfect for pre-android M version.However, It shows following status on android M device.

It is giving an error

Step 2: Describe your environment

• Device: Intex Aqua Power 4G
• OS version: 6.0
• SDK version: Android studio 2.1.1
• [Android] Google Play Services version: 9.0.0

Step 3: Describe the problem:

Using repository I am not able to login on android M device. It is working perfect on pre-M device but on android M device, it is creating a problem.

Relevant Code:

// Build a GoogleApiClient with access to GoogleSignIn.API and the options above.
mGoogleApiClient = new GoogleApiClient.Builder(this)
.enableAutoManage(this, new GoogleApiClient.OnConnectionFailedListener() <
@OverRide
public void onConnectionFailed(@nonnull ConnectionResult connectionResult) <

@OverRide public void onActivityResult(int requestCode, int resultCode, Intent data) <
super.onActivityResult(requestCode, resultCode, data);

The text was updated successfully, but these errors were encountered:

ianbarber commented Nov 14, 2016

DEVELOPER_ERROR usually means it can’t look up the SHA1/Package Name combination — are you using precisely the same APK on those two devices, or is there a chance they could be built separately?

dab13491 commented Nov 15, 2016

Problem solved mate! Yes problem was the method of SHA key generation.

On Mon, Nov 14, 2016 at 10:25 PM, Ian Barber notifications@github.com
wrote:

DEVELOPER_ERROR usually means it can’t look up the SHA1/Package Name
combination — are you using precisely the same APK on those two devices, or
is there a chance they could be built separately?

Darshan Bhatt
Android Developer
Phone: +919033823578 | Skype: darshan.pardypanda

This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed. Any
views or opinions expressed are solely those of the sender and do not
necessarily represent those of Pardy Panda Studios. If you have received
this email in error please notify the sender.

Источник

Getting Developer Error even after putting everything in place in release mode (Android) #905

Comments

Ragnar-23 commented Jul 13, 2020

React native google signIn is working fine in debug mode.
But google siginIn is not working in release mode, its giving DEVELOPER_ERROR code 10.
I have added both debug and release certificates on firebase console, everything is checked.

But still I am getting DEVELOPER_ERROR. Do we need to add SHA1 from playstore also for release mode (apk generated using ./gradlew assembleRelease)?

Expected Behavior

Actual Behavior

Environment

The text was updated successfully, but these errors were encountered:

radetsky commented Jul 16, 2020

Maybe you turned on Google Play Signature in Play Market. This feature replaces your certificate by auto-generated by Google.
You can find it at the Play Console on the page ‘App signature’. You can download deployment certificate or just copy-paste fingerprints MD5, SHA1, etc.
Copy SHA1 to Firebase Console App settings Android app.

PS. Also, it works for Facebook sign in. Download the certificate and do something like this:

to get hash to use with Facebook application settings

PS. I’m not a contributor. I’m also dev. 🙂

rogerdribeiro commented Jul 16, 2020

I’m having the same problem

Kailash23 commented Jul 16, 2020

hoanganhnh2009 commented Jul 30, 2020

I’m having same problem.

abhilashfancy commented Jul 31, 2020

I have used a webClientId which I put to the whitelisted client ids in firebase console inside google login. But still it gives me DEVELOPER_ERROR. If I use my debug keystore, the login works because I have added the SHA1 of debug keystore in firebase console. But I cannot add the SHA1 of release keystore because it is already used in another project which I have lost access to. So I have created a new web client and added its id to the firebase google login whitelist and using the same inside the app. But still getting DEVELOPER_ERROR

usmansbk commented Jul 31, 2020 •

I use this package every year and every year I have to come back here. Lol

usmansbk commented Jul 31, 2020

If you’re still having this problem try this solution #706 (comment)

abhilashfancy commented Jul 31, 2020

@usmansbk your solution did not help. I have already added the correct SHA1 to firebase. I am not using the default debug keystore. I have created my own and added the SHA1 to firebase. When I build the app using this keystore it works fine. But when I do the same with another keystore it does not work even after whitelisting the web client id

stanica commented Sep 1, 2020

Just started getting this problem too. Everything seems to be configured correctly, including SHA1.

rnnyrk commented Sep 3, 2020

Can’t seem to solve this issue. I have two custom keystores setup.
What I did:

1. Exported the SHA-1 with keytool -exportcert -alias KEYSTORE_ALIAS -keystore KEYSTORE_PATH and inserted this to my dev and prod app in Firebase
2. Also on https://console.developers.google.com/ I have two OAuth 2.0-client-ID’s with the correct package names and SHA-1 fingerprints
3. Copied the webClientId from Firebase Console > Authentication > GoogleSignIn and added it before the signin with Google.Configure
4. My Android build buildTypes are as following:

1. Downloaded my latest google-services.json
2. Ran ./gradlew clean and adb uninstall com.packagename
3. npm run android

Still the same DEVELOPER_ERROR .
I’m really out of options.. Anyone suggestions?

usmansbk commented Sep 3, 2020

Always check the version to debug-keystore SHA you generated. I think there’s one in the android/ folder of the project and there’s

/android of the whole system.

kushavi2509 commented Sep 9, 2020

No matters weather you are using a firebase or NOT you have to have both the configurations (Android as well as Web client )

Click on Configure a prioject
Select the project.
Fille the required fields.
Voylla, you are good to go.

SanjanaTailor commented Oct 21, 2020 •

I am facing same developer_error since I am using android React native app to complete google singin.
Also, I am not using Firebase to login
I created both OauthCilent android and Web client 2 and giving same id here to signin

also to create SHA-1 for android used this command to C:\Users\satailor\Documents\ReactNative_workspace\App>keytool -list -v -alias androiddebugkey -keystore C:\Users\satailor\Documents\ReactNative_workspace\app\android\app\debug.keystore
and copied SHA-1 and added in google cloud console for same.

Inside Android folder following changes are added:
settings.gradle file
include ‘:react-native-google-signin’, ‘:app’

android/build.gradle file included following lines:

Help me to resolve an issue. Let me know any other information required.

Источник