react-native-google-signin · vonovak · Aug 31, 2025 · Aug 31, 2025
diff --git a/.yarn/releases/yarn-4.7.0.cjs b/.yarn/releases/yarn-4.7.0.cjs
diff --git a/.yarn/releases/yarn-4.9.2.cjs b/.yarn/releases/yarn-4.9.2.cjs
diff --git a/.yarnrc.yml b/.yarnrc.yml
@@ -1,3 +1,3 @@
 nodeLinker: node-modules
 
-yarnPath: .yarn/releases/yarn-4.7.0.cjs
+yarnPath: .yarn/releases/yarn-4.9.2.cjs
diff --git a/babel.config.js b/babel.config.js
diff --git a/docs/buttons/google-logo-button.mdx b/docs/buttons/google-logo-button.mdx
@@ -4,7 +4,7 @@ sidebar_class_name: sponsor-heart
 
 # GoogleLogoButton
 
-A Google Sign-In button that follows Google's official branding guidelines. Intended for native apps.
+A Google Sign-In button that follows Google's official branding guidelines. Intended for native apps. It renders null when used on the web.
 
 import Banner from '../_sponsorBanner.mdx';
 

diff --git a/docs/buttons/web.mdx b/docs/buttons/web.mdx
@@ -19,7 +19,7 @@ As the Universal sign in Guide explains, there are two ways to sign in on the we
 
 One-tap UI may not always be available: This happens if user has [opted out](https://developers.google.com/identity/gsi/web/guides/features#globally_opt_out) or when they close the dialog several times in a row, entering the [cooldown period](https://developers.google.com/identity/gsi/web/guides/features#exponential_cooldown).
 
-The Google Sign-In button serves as a fallback. Tapping it will open the regular Google Sign-In dialog.
+The Google Sign-In button serves as a fallback. Tapping it opens the regular Google Sign-In dialog.
 
 ```tsx
 import { WebGoogleSigninButton } from '@react-native-google-signin/google-signin';

diff --git a/docs/errors.md b/docs/errors.md
@@ -36,14 +36,14 @@ try {
 import { statusCodes } from '@react-native-google-signin/google-signin';
 ```
 
-Status codes are useful when determining which kind of error has occurred during the sign-in process. Under the hood, these constants are derived from native GoogleSignIn error codes and are platform-specific. Always compare `error.code` to `statusCodes.*` and do not rely on the raw value of `error.code`.
+Status codes are useful when determining which kind of error has occurred during the sign-in process. Under the hood, these constants are derived from native error codes and are platform-specific. Always compare `error.code` to `statusCodes.*` and do not rely on the raw value of `error.code`.
 
 See [example usage](one-tap#signin).
 
-| Name                          | Description                                                                                                                                                                                                                                                                                                                                                                 |
-| ----------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `IN_PROGRESS`                 | Trying to invoke another operation (e.g. `signInSilently`) when previous one has not yet finished. If you call e.g. `signInSilently` twice, two calls to `signInSilently` in the native module will be done. The promise from the first call to `signInSilently` will be rejected with this error, and the second will resolve / reject with the result of the native call. |
-| `PLAY_SERVICES_NOT_AVAILABLE` | Play services are not available or outdated. This happens on Android, or on the web when you're calling the exposed APIs [before the Client library is loaded](setting-up/web).                                                                                                                                                                                             |
+| Name                          | Description                                                                                                                                                                                                                                                                                                                                                             |
+| ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `IN_PROGRESS`                 | Trying to invoke another operation (e.g. `signInSilently`) when previous one has not yet finished. If you call e.g. `signInSilently` twice, two calls to `signInSilently` in the native module are done. The promise from the first call to `signInSilently` will be rejected with this error, and the second will resolve / reject with the result of the native call. |
+| `PLAY_SERVICES_NOT_AVAILABLE` | Play services are not available or outdated. This happens on Android, or on the web when you're calling the exposed APIs [before the Client library is loaded](setting-up/web).                                                                                                                                                                                         |
 
 ### Status codes specific to Universal sign in {#universal-status-codes}
 

diff --git a/docs/install.mdx b/docs/install.mdx
@@ -15,7 +15,6 @@ Why paid? According to the [State of React Native Survey](https://results.2024.s
 ⭐️ **Key Features**:
 
 - **Cross-Platform**: Unified APIs which work on **Android**, **iOS**, **Web**, and **macOS**.
-
   - Android: Built with [Credential Manager library](https://developers.google.com/identity/android-credential-manager)
   - Web: Uses [Sign In with Google for Web](https://developers.google.com/identity/gsi/web/guides/features)
   - iOS & macOS: Powered by the [Google Sign-In SDK](https://developers.google.com/identity/sign-in/ios/start)

diff --git a/docs/integration-notes.md b/docs/integration-notes.md
@@ -1,5 +1,5 @@
 ---
-sidebar_position: 55
+sidebar_position: 61
 ---
 
 # Integration notes
@@ -18,6 +18,7 @@ sidebar_position: 55
 
 The default requested scopes are `email` and `profile`.
 
-If you want to manage other data from your application (for example access user agenda or upload a file to drive) you need to request additional permissions. This can be accomplished by adding the necessary scopes when configuring the GoogleSignin instance.
+If you want to manage other data from your application (for example, access user agenda or upload a file to drive) you need to request additional permissions. This can be accomplished by calling [`requestAuthorization`](one-tap#requestauthorization) or by
+adding the necessary scopes when calling [`configure`](one-tap#configure).
 
 Visit https://developers.google.com/identity/protocols/googlescopes or https://developers.google.com/oauthplayground/ for a list of available scopes.