Sign in doesn't seem to be working in custom Expo Dev Client

[PiotrSzlagura]

Hi!

I have followed all the steps here: https://react-native-google-signin.github.io/docs/setting-up/get-config-file#2-enter-required-information-and-download-the-config-file and here: https://react-native-google-signin.github.io/docs/troubleshooting#troubleshooting-for-non-firebase-users.

Despite all that, I'm still getting DEVELOPER_ERROR (code 10).

I triple-checked and verified, that:

• I have uploaded valid SHA-1 fingerprints to Firebase and re-downloaded google-services.json file afterwards
• I am using above mentioned google-services.json file for my development builds
• During build, I checked which keystore is being used, and verified that it matches the one I used for SHA-1 key
• I use webClientId for WEB (not Android), though this doesn't seem to matter that much (I get this error with or without it)
• In my Firebase Console, I have uploaded Google Play Signing SHA-1 key (and re-verified that it matches)
• My dev client's bundle identifier matches the one used in Firebase (I'm using the same bundle identifier as my production app)

I'm hitting a wall here, and therefore I have two questions:

• Does this auth work with Expo Dev Client?
• Does this package expect google-services.json file to be in any specific spot in app's files tree?

Additionally: is there any way to get some more explanatory error information? It would be super helpful to pinpoint specific error in my configuration.

Thanks in advance!

[PiotrSzlagura]

I managed to get it working!

For future reference - My issue was that my OAuth Agreement Screen (I'm not 100% sure how this is called in english) was not configured, therefore blocking me from accessing Google OAuth.

[frizurd]

I managed to get it working!

For future reference - My issue was that my OAuth Agreement Screen (I'm not 100% sure how this is called in english) was not configured, therefore blocking me from accessing Google OAuth.

Im facing the same issue now, how did you configure the agreement screen and how do you know that it is not configured?

Also, before you configured the screen, were you able to successfully get the popup, and fill in your email and password? The DEVELOPER_ERROR pops up after I input and submit my credentials.

[PiotrSzlagura]

I actually found out about missing agreement screen configuration by accident - I wanted to add new Android token but Google Cloud panel wouldn't allow me to do that without agreement page configured.

Also when I posted my update I forgot about one super important thing - you need to have an Android token existing in your OAuth configuration. This token needs to be signed with SHA-1 key of your app. I didn't find this information anywhere in documentation (or I have misunderstood that information if it's there), and I think this was the most important thing that was blocking me (because I already had an Android OAuth token, which was signed with different SHA-1).

[PiotrSzlagura]

And yes - I was able to see the Google popup, select account etc, the DEVELOPER_ERROR was only visible after returning to app