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
@@ -109,7 +109,7 @@ The response object for OneTap's `signIn` and `createAccount`.
109
109
110
110
Learn more about additional web-only parameters at [Google's reference documentation](https://developers.google.com/identity/gsi/web/reference/js-reference#IdConfiguration).
@@ -197,19 +197,20 @@ The entry point of the Universal Sign In API, exposed as `GoogleOneTapSignIn`.
197
197
198
198
On the web, the signatures of `signIn`, `presentExplicitSignIn`, and `createAccount` are callback-based and on native they are Promise-based. Read more in the [guide](/docs/one-tap#web-support).
Copy file name to clipboardExpand all lines: docs/migrating.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
@@ -22,11 +22,11 @@ Migrating from Original to Universal module is mostly about changing the method
22
22
|`signOut`|`signOut`||
23
23
|`revokeAccess`|`revokeAccess`| Universal requires email/id parameter on web. |
24
24
|`hasPreviousSignIn`| Use `signIn` response | Check for `noSavedCredentialFound` response type. |
25
-
|`clearCachedAccessToken`|Not provided, presumably not needed.| -|
25
+
|`clearCachedAccessToken`|`clearCachedAccessToken`| Same functionality.|
26
26
27
27
---
28
28
29
-
## Migrating to new JS API
29
+
## Migrating to the new JS API
30
30
31
31
Version 13 introduced a new JS API, which changes some method response signatures and makes minor changes to error handling (details [here](https://github.com/react-native-google-signin/google-signin/pull/1326)). If you're upgrading from version 12 or earlier, you'll need to make some minor adjustments.
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.
0 commit comments