"DEVELOPER_ERROR" (Code 10) on Google Login -- have tried everything!

[asindhu]

I can't get Google login working with Supabase for a react-native (Expo) app, at least in production. I have looked at the following:

1. Supabase guide on Google login
2. react-native-google-signin docs and FAQ
3. This YouTube video that's Flutter-specific but has applicable info in the first half or so
4. Dozens of StackOverflow questions

Here's the steps I've tried and the analysis so far.

I actually have been able to get it working on an Expo development build. However, it was not by following the Supabase docs (item 1 above), which says to create an Android OAuth token into Google Cloud with a SHA-1 key and input this into Supabase. It was by following some of the steps in the YT video (item 3 above) which tells you to configure a web client OAuth token into Google Cloud and then input the Client ID and Client Secret into Supabase. This actually works in a debug/development build.

However, when I create a production build with this config in the Google Play store, I get the DEVELOPER_ERROR (code 10) error.

Alternatively, I have tried following the Supabase instructions (item 1 above) to the exact letter and that doesn't work either, whether in development or release. These are the instructions that say to create an Android OAuth key and provide the SHA-1.

Supposedly, the DEVELOPER_ERROR comes when there is a SHA-1 mismatch. There are many many different instructions from different sources on how to get the right SHA-1 key for your Auth key, and I've tried all of them. I have tried:

• ./gradlew signingReport and taking the ":app:signingReport" SHA-1 key. It's the same for me for debug & release.
• eas credentials and taking "SHA-1 Fingerprint" in the development, preview, or production options (again all 3 are the same SHA-1 key, although different from the key above from gradle)
• keytool -list -v -keystore ~/.android/debug.keystore and taking the "SHA1 certificate fingerprint", again different from the other two
• Going to the Google Play developer console > App Signing > SHA-1 certificate fingerprint, again it's different

I have all four of these keys set up as Android OAuth keys in Google Cloud and added them to the Supabase authentication configuration. None of them work either in development or in a production build. I still just get the DEVELOPER_ERROR.

I am super stuck on this. I can't seem to find any information on how to move forward. The only way I can get sign-in to work is in a development build using the OAuth web client. I will say, one clear inconsistency I see is that from the react-native-google-signin FAQ (item 2 above) it says pretty clearly that if you are passing a "webClientId" into GoogleSignin.configure() that it must be of type web client, not Android.. Quoting it directly:

If you're passing webClientId in configuration object to GoogleSignin.configure() make sure it's correct and that it is of type web (NOT Android!).

Whereas, the Supabase instructions (item 1 above) tell you to create an Android OAuth key and then pass it in as the webClientId parameter. I would imagine that this inconsistency has something to do with the problem, but I'm not sure.

Any help would be greatly appreciated. I'm not sure I've seen evidence of anyone successfully getting this set up all way through and could really use some input on it. Thank you so much in advance!

[dshukertjr]

The error you are facing has nothing to do with Supabase but means that you have a misconfiguration in your Google sign-in setup.

Code 10 means that you have the wrong SHA 1 certificate fingerprint set on the client ID. For the production build, make sure you create a Android Client ID with the production SHA 1 certificate fingerprint.

[asindhu]

Thanks so much for your response. I've tried creating Android keys with all the SHA-1 keys described above, including the production one that I grabbed from the Google Play developer console, and it is still not working...

[0xifis]

I am getting the same error. Followed the same debug pattern as OP. What strikes me as suspicious is that the

GoogleSignin.configure({
    scopes: ['https://www.googleapis.com/auth/drive.readonly'],
    webClientId: "xxxx",
});

Where the plugin docs mention that it has to a client ID of android type but the property name seems to suggest it is web type.

[0xifis]

https://github.com/orgs/supabase/discussions/27618 seems to have hit a similar problem

[AhmedAlsudairy]

Lets stick to this post

I have same problem and I tried every possible sha-1 keys and the docs not clear

[dshukertjr]

The error is not related to Supabase-specific configuration and is just a general error from setting up Google sign-in. I would suggest going through how to setup Google sign-in, and make sure that you are able to perform Google sign-in on your app before jumping into any Supabase related settings.

[codebrain22]

I have the same issue in Flutter but only in prod. Both debug and release SHA keys are attached on my Firebase project. What's surprising is that it was giving 12500 error, now it's just says 10. I tried almost every possible solution I could find on the internet but I'm not winning.

[realfelixyu]

Any update on this?

[dshukertjr]

The error is not related to Supabase-specific configuration and is just a general error from setting up Google sign-in. I would suggest going through how to setup Google sign-in, and make sure that you are able to perform Google sign-in on your app before jumping into any Supabase related settings.

[ivanff]

I tried the same thing with all the sha1 that I could find, and there is nothing that does not fit

the documentation is terrible

for this reason, I used native script and there were no problems with authorization in Google