Google Auth/Signin in React Native without Firebase.

Google auth is one of the most commonly used Authentication methods in Mobile and web apps. Well, it is also a tricky one as compared to normal user email and password auth.

In this post, we will learn how to integrate Fully working Google auth with React Native (Without Firebase).

1. Creating you React Native app

Let's start by creating our react-native project.

npx react-native init myapp

Now install the @react-native-google-signin/google-signin module using npm i @react-native-google-signin/google-signin in your project folder.

``

2. Setting up Android environment

After installing the required module, let's set up some android files to make it work properly.

1. Update android/build.gradle with the following configuration:

Add classpath 'com.google.gms:google-services:4.3.10' into your dependencies in buildscript.

1. Update android/app/build.gradle with the following configuration:

• Add apply plugin: 'com.android.application' at the top of your build gradle (android/app).

• Add
  implementation 'com.google.android.gms:play-services-auth:20.0.0'
implementation "androidx.browser:browser:1.2.0" in dependencies in the same.
  `

3. Importing module in our App

Now import the installed module like this

import { GoogleSignin, statusCodes } from '@react-native-google-signin/google-signin';

then after importing the module let's set up a configuration code for our sign-up.

React.useEffect(() => {
    GoogleSignin.configure({
      webClientId: "Your-web-client-id", 
      offlineAccess: true
    });
  }, [])

Let's not worry about the client Id, for now, we will generate it later on in this tutorial.

Now after configuration is done, it's time to make our sign-up function using the Google Auth module we just imported.

const GoogleSingUp = async () => {
    try {
      await GoogleSignin.hasPlayServices();
      await GoogleSignin.signIn().then(result => { console.log(result) });
    } catch (error) {
      if (error.code === statusCodes.SIGN_IN_CANCELLED) {
        // user cancelled the login flow
        alert('User cancelled the login flow !');
      } else if (error.code === statusCodes.IN_PROGRESS) {
        alert('Signin in progress');
        // operation (f.e. sign in) is in progress already
      } else if (error.code === statusCodes.PLAY_SERVICES_NOT_AVAILABLE) {
        alert('Google play services not available or outdated !');
        // play services not available or outdated
      } else {
        console.log(error)
      }
    }
  };

Now Connect this function to your button with onPress={GoogleSingUp} prop
``

4. Generating Web client ID and SHA1 key for Sign up

Now, this is the main part where most of the developer gets stuck or get a pretty common and irritating error -

Error: Status{statusCode=DEVELOPER_ERROR}

But what is causing this error?. It is quite simple, the SHA1 key of Debug Keystore. Yeah, according to google, you have to put your Release Keystore key in Google Console. But most blogs and articles forget to mention this point which is very important no matter which module you are using.

1) Generate Release keystore and it's SHA

Now assuming you have already installed JDK in your system, let's move to generating the Release key. In your android/app run this command in cmd -

 keytool -genkey -v -keystore my_release_key.keystore -alias my_key_alias -keyalg RSA -keysize 2048 -validity 10000 

It will ask for some detail so fill them in carefully and remember the password you entered in it.

This command will generate a release key in your android/app directory.

• Now in your android/gradle.properties add

  MYAPP_UPLOAD_STORE_FILE=my_release_key.keystore
  MYAPP_UPLOAD_KEY_ALIAS= my_key_alias
  MYAPP_UPLOAD_STORE_PASSWORD=yourPassword
  MYAPP_UPLOAD_KEY_PASSWORD=yourPassword
  

• And this in your android/app/build.gradle

  signingConfigs {
      debug {
          // storeFile file('debug.keystore')
          // storePassword 'android'
          // keyAlias 'androiddebugkey'
          // keyPassword 'android'
  
           storeFile file(MYAPP_UPLOAD_STORE_FILE)
           storePassword MYAPP_UPLOAD_STORE_PASSWORD
           keyAlias MYAPP_UPLOAD_KEY_ALIAS
           keyPassword MYAPP_UPLOAD_KEY_PASSWORD
      }
  
      release {
          if (project.hasProperty('MYAPP_UPLOAD_STORE_FILE')) {
              storeFile file(MYAPP_UPLOAD_STORE_FILE)
              storePassword MYAPP_UPLOAD_STORE_PASSWORD
              keyAlias MYAPP_UPLOAD_KEY_ALIAS
              keyPassword MYAPP_UPLOAD_KEY_PASSWORD
          }
      }
  }
  

Now this will generate release SHA as your debug keystore SHA, so you don't have to worry about that error

Now generate release SHA1 using this command in android/app

keytool -list -v -keystore app/my_release_key.keystore -alias my_key_alias

Copy that SHA1 key and paste it somewhere for the next step.
``

2) Inserting SHA1 key in Google Developer Console.

Now, after doing that much hard work, let's do this final part. We have to paste this key into the Google Developer console to tell google about our app and its authentication.

• After signing up in the Google Developer console or Google cloud platform, head over to the Credential tab. There you will find a button saying "Create Credential", choose OAth Client ID.

• Then choose Application type- Android and enter the package name and then the SHA1 key you copied in the previous step. Hit create and your Android API is ready.

• Now Similarly create an OathID for Web client instead of Android and leave all other fields as it is.

• Now copy the Web client ID from the Oath you just created.

That's it we got the Web client ID we needed for Step 3 above.



5. Finalizing

Now paste this Web Client ID into your Google config object in Step 3 above and run the app.

After pressing the Sign-in Button, A pop-up should appear. Select the account you want to login with and after selecting the account it will return an object containing IdToken and some other stuff.

If you did everything exactly the same and didn't mess up anywhere, we should see some results like this

{
    "idToken": "Your-google-auth-token",
    "scopes": [
        "https://www.googleapis.com/auth/userinfo.email",
        "https://www.googleapis.com/auth/userinfo.profile"
    ],
    "serverAuthCode": "your-server-auth-code",
    "user": {
        "email": "[e-mail]",
        "familyName": "your-last-name",
        "givenName": "your-first-name",
        "id": "some-id",
        "name": "your-full-name",
        "photo": "a-url-for-profile-photo"
    }
}

And with that, we successfully integrated the Google auth into our React Native app.

Please leave a comment if you liked the post or just want to add something valuable.

Comments

[Abdul Rehman]

after run this cmd keytool -list -v -keystore app/my_release_key.keystore -alias my_key_alias in my android/app. I'm getting this error

keytool -list -v -keystore app/my_release_key.keystore -alias my_key_alias
keytool error: java.lang.Exception: Keystore file does not exist: app/my_release_key.keystore
java.lang.Exception: Keystore file does not exist: app/my_release_key.keystore

[Suyash Vashishtha]

Yeah bcz you have to first generate it using keytool -genkey -v -keystore my_release_key.keystore -alias my_key_alias -keyalg RSA -keysize 2048 -validity 10000 , then make sure you put right path in list command ( mine was app/name ).

[Abdul Rehman]

Hey, after solving this I'm getting

[Error: DEVELOPER_ERROR]

when i clicked signin with google button

[Suyash Vashishtha]

"Yeah, according to google, you have to put your Release Keystore key in Google Console "

4rth heading point in the blog 😅

[Karthi Keyan]

put this instead this assumes you are inside app folder

keytool -list -v -keystore ./my_release_key.keys
tore -alias my_key_alias```

[raj7seasol]

Thanks man it worked for me

[Afonso-Jorge]

Man I did everything I mean every line and im still getting LOG [Error:DEVELOPER_ERROR] ive been trying to fix this without exporting everything Ive done to firebase in the hopes that doind so would make it work. Do you have any other ideas as to why the error would still show up even after following everything you said down to the line?

[Suyash Vashishtha]

This error basically comes due to Release SHA Key... make sure you paste the same release key in console which your building app with...

Make sure you did 4.1 step correctly (replace debug SHA keystore with release )

[Afonso-Jorge]

Ended up adding the google-services.json from firebase which allows you to input both the SHA Key from debug.keystore in User/.android/bin and the one in the project directory android/app folder so now it works.

Cheers anyways and for release I´ll just follow what you did except I´ll put the generated SHA Key on firebase and redownload the google-services.json.

[Diego Santa Cruz]

I got an error with code 10, It was because I had generated the sha-1 with the keystore of the root of my computer; generate with the keystore of the react native project that comes inside the android / app / debug.keystore folder and copy console google oauth android and works.
keytool -keystore android/app/debug.keystore -list -v

[Suyash Vashishtha]

Yeah I clearly mentioned that. Although thanks for pointing it, might help someone with similar case :)

[felixkrautschuk]

My Google SignIn works when running a debug build on device/emulator and even when running a release build with our release keystore on device/emulator.

But when I upload our release aab to Google Play and download it via internal test, I always get Error Code 10 after I tapped the SignIn Button and choose the account.

I double-checked that the app package name in the OAuth Client in Google Cloud Console is correct and I already added the SHA1-fingerprint from the App Signing section in Google Play Console.

Can anyone help? Thanks in advance!

[felixkrautschuk]

never mind, I just found out that there is a separate SHA-fingerprint section for internal testing in Google Play Console, so I had to add another OAuth client ID in cloud console, now it is working

[Yue Wang]

This is the only guide that works after researching everywhere else.

For those who followed the post and still get an error, remember to also create 2 more android credentials with the SHA-1 you find from google play console. The URL is here:

play.google.com/console/u/0/develo...

I created a dev.to account just to comment on this post. hanks so much for the guide!

[Mudit Kashyap]

I am getting this error [Error: A non-recoverable sign in failure occurred]

[karimgh]

Any solution for this error ?
Im using release keystore SHA-1 with firebase.

[santiago sarmiento]

Could you solve it?

[Mohammad Umar]

Hey, I am facing an issue regarding google login. I have two components in my React Native app, Login and Signup, on Login I click google login button, pop up opens, user clicks its gmail and gets login, fine no issue.
Even I cancel the pop-up right status code is triggered and flow works as expected.

When I click same google login button in Signup, pop-up opens, if i cancel the pop-up statusCodes.SIGN_IN_CANCELLED should trigger but instead statusCodes.IN_PROGRESS gets triggered and I get this error,

Error: Sign-in in progress
Error Code: 12502
Status Code: ASYNC_OP_IN_PROGRESS

Any thoughts what I am doing wrong, or any configuration is missing ?

[Neha Gupta]

I followed all the steps but nothing happens at GoogleSignin.signIn(), no error too. I get true as response from GoogleSignin.hasPlayServices().

[ElectroFist]

Ahh finally found something really useful, was stuck on this for days. Thank you