You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/install.mdx
+41-5Lines changed: 41 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ Why paid? According to the [State of React Native Survey](https://results.2024.s
11
11
12
12
[//]: #'🌟'
13
13
14
-
### Universal Sign In (premium) {#premium}
14
+
### Universal Sign In (premium) {/*#premium*/}
15
15
16
16
⭐️ **Key Features**:
17
17
@@ -47,7 +47,7 @@ Available on the public npm registry, this version:
47
47
48
48
> To migrate from the public version to the premium one, follow the [migration guide](migrating#migrating-from-original-to-universal-sign-in).
49
49
50
-
## Accessing the private npm package {#package-manager-setup}
50
+
## Accessing the private npm package {/*#package-manager-setup*/}
51
51
52
52
The private npm package is like any other, but it's hosted on the [GitHub npm packages registry](https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-npm-registry), not the public npm registry. Therefore, a small bit of setup is needed:
53
53
@@ -82,15 +82,37 @@ npmScopes:
82
82
```
83
83
84
84
</TabItem>
85
+
86
+
<TabItem value="pnpm" label="pnpm">
87
+
create a `.npmrc` file in your project root with the following content (pnpm respects `.npmrc`):
Alternatively, [bun also reads `.npmrc` files](https://bun.sh/docs/pm/npmrc#configure-options-for-a-specific-registry), so the npm setup above works too.
CI environment setup is similar to the local one: you also need a `.npmrc` (or similar) file. Follow [this GitHub Actions example](https://gist.github.com/nandorojo/46b3e46de12177b9ad7e4d454310de21#file-private-npm-in-gh-actions-md) - other CI providers require very similar steps.
87
111
88
112
</TabItem>
89
113
90
114
</Tabs>
91
115
92
-
If you use another package manager ([such as Bun](https://bun.sh/docs/install/registries)), refer to its documentation for setting up a custom registry.
93
-
94
116
## Installing
95
117
96
118
<Tabs queryString="package-manager">
@@ -108,6 +130,20 @@ If you use another package manager ([such as Bun](https://bun.sh/docs/install/re
bun add @react-native-google-signin/google-signin@latest
143
+
```
144
+
145
+
</TabItem>
146
+
111
147
</Tabs>
112
148
113
149
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 the package manager is not configured correctly — try uninstalling and reinstalling the package.
@@ -127,4 +163,4 @@ The latest version of the Universal Sign In package supports (use older versions
This method is only needed on Android. You may run into a `401 Unauthorized` error when an access token is invalid. Call this method to remove the token from local cache and then call `requestAuthorization()` to get a fresh access token. Calling this method on Apple does nothing and always resolves. This is because on Apple, `requestAuthorization()` always returns valid tokens, refreshing them first if they have expired or are about to expire (see [docs](https://developers.google.com/identity/sign-in/ios/reference/Classes/GIDGoogleUser#-refreshtokensifneededwithcompletion:)).
If you use Expo (with the config plugin and prebuild), or if you're using Firebase, you don't need to provide the `iosClientId` parameter to the `configure` method.
Copy file name to clipboardExpand all lines: docs/security.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -126,7 +126,7 @@ const getNonce = () => {
126
126
</TabItem>
127
127
</Tabs>
128
128
129
-
## App Check for iOS (advanced) {#appcheck}
129
+
## App Check for iOS (advanced) {/*#appcheck*/}
130
130
131
131
App Check helps protect your apps from abuse by preventing unauthorized clients from authenticating using Google Sign-in: only the apps you've authorized can acquire access tokens and ID tokens from Google's OAuth 2.0 and OpenID Connect endpoint.
Copy file name to clipboardExpand all lines: docs/setting-up/get-config-file.mdx
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,9 +38,9 @@ import Tabs from '@theme/Tabs';
38
38
importTabItemfrom'@theme/TabItem';
39
39
40
40
<Tabs>
41
-
<TabItemvalue="config-doctor"label="A device or any APK file"default>
41
+
<TabItemvalue="config-doctor"label="✅ Any APK or device"default>
42
42
43
-
Use the [Configuration Doctor](../config-doctor). (Requires an [Universal sign in](/docs/install#premium) license.)
43
+
Use the [Configuration Doctor](../config-doctor). This is the **only universal option** — it works regardless of how the APK was built or where it came from. The other tabs cover specific scenarios.
44
44
45
45
1. Get a device / emulator with the app installed, or get the APK (build it locally or in cloud, download from the Play Console / Play Store...)
Copy file name to clipboardExpand all lines: docs/troubleshooting.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,15 +8,15 @@ description: 'Common issues and solutions for Android (`DEVELOPER_ERROR`, cancel
8
8
9
9
## Android
10
10
11
-
### Sign in result is `cancelled` even though the user did not cancel the flow {#unexpected_cancelled}
11
+
### Sign in result is `cancelled` even though the user did not cancel the flow {/_#unexpected_cancelled_/}
12
12
13
13
You may be hitting an [error in the Android SDK](https://issuetracker.google.com/issues/424210681). This error is usually observed with `presentExplicitSignIn`. Follow the [`DEVELOPER_ERROR paragraph`](#developer_error) to resolve it.
14
14
15
15
### Login does not work when downloading from the Play Store.
16
16
17
17
See [`DEVELOPER_ERROR` paragraph](#developer_error).
18
18
19
-
### `DEVELOPER_ERROR` or `code: 10` or `Developer console is not set up correctly` error message {#developer_error}
19
+
### `DEVELOPER_ERROR` or `code: 10` or `Developer console is not set up correctly` error message {/_#developer_error_/}
20
20
21
21
This is always (! _absolutely always_ !) a configuration mismatch between your app and the server-side setup (in Firebase or Google Cloud console).
0 commit comments