Skip to main content

Installation

There are two ways to consume the package:

⭐️ Key Features:

🛡️ Advanced security features

🔧 Easier setup - Automatic detection of configuration parameters for faster integration.

📱 An example app - to showcase all Universal sign in features

Your purchase enables improvements in the module and upstream SDKs (such as 1, 2).

Public version

Available on the public npm registry, this version:

  • Has platform support limited to Android and iOS.
  • Uses functional, but deprecated legacy Android Google Sign-In.
  • Contains none of the extra features listed above.

If you want to migrate from the public version to the Universal version, follow the migration guide.

Obtaining Universal Sign In

Universal sign in requires purchasing a license, after which you will be able to configure your (or your colleagues') access to the private npm package and to the private repo with the sources and examples. Alternatively, as an Expo customer, obtain access through this form.

Accessing the private npm package

The private npm package is like any other, but it's hosted on the GitHub npm packages registry, not the public npm registry. Therefore, a small bit of setup is needed:

  1. Obtain here a Personal Access Token with packages:read permission.

  2. Set up your package manager to fetch the package from the GH packages registry. In this example, we're using an NPM_TOKEN_GOOGLE_SIGN_IN environment variable.

create a .yarnrc.yml file in your project root with the following content:

.yarnrc.yml
npmScopes:
react-native-google-signin:
npmRegistryServer: https://npm.pkg.github.com
npmAuthToken: '${NPM_TOKEN_GOOGLE_SIGN_IN}'

If you use another package manager (such as Bun), refer to its documentation setting up a custom registry.

Installing

yarn add @react-native-google-signin/google-signin@latest

After installing: if you're using the Universal version, open the lockfile (yarn.lock / package-lock.json...) and verify that the package is fetched from the GitHub registry (the entry must point to npm.pkg.github.com, not registry.npmjs.org). If it does not, it means that your package manager is not configured correctly - try uninstalling and reinstalling the package.

There are several guides to follow now:

Requirements

The packages support last 3 stable releases of React Native. Unofficially, they may work with older versions too.

If you're using the New Architecture, it's strongly recommended to use the latest React Native version available.