-
Notifications
You must be signed in to change notification settings - Fork 887
Add guides for native Sign in with Google in Expo and document useSig… #2786
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
…nInWithGoogle hook
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
@chriscanin have pushed my docs review here - let me know your thoughts. Feel free to put it back in draft as we discussed if it needs to be retweaked. A lot of the changes I submitted are consistency + docs voice changes. |
…ble names and remove outdated package reference
…plugin array formatting
|
@chriscanin have left the second docs review after your recent changes: docs review pt 2 after changes. Have a look and let me know your thoughts. I want to double check a few more things and test out the flow, and then it should be good. |
| 1. For the **Application type**, select **Web application**. | ||
| 1. Add a name (e.g., "Web client for token verification"). | ||
| 1. Select **Create**. A modal will open with your **Client ID**. | ||
| 1. Copy and save the **Client ID** - you'll need this for `EXPO_PUBLIC_CLERK_GOOGLE_WEB_CLIENT_ID`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the Client Secret not needed? Like for Android: https://clerk.com/docs/guides/configure/auth-strategies/sign-in-with-google @chriscanin
| ## Add your Android application to Clerk | ||
|
|
||
| Add your Android application to the [**Native Applications**](https://dashboard.clerk.com/~/native-applications) page in the Clerk Dashboard. You will need your Android app's **package name**. | ||
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this step not needed? Like in the Android guide. @chriscanin
| 1. Select **Add connection** and select **For all users**. | ||
| 1. In the **Choose provider** dropdown, select **Google**. | ||
| 1. Ensure that both **Enable for sign-up and sign-in** and **Use custom credentials** are toggled on. | ||
| 1. Save the **Authorized Redirect URI** somewhere secure. Keep this modal and page open. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is being saved, but where do we actually use it? @chriscanin
🔎 Previews:
What does this solve?
useSignInWithGoogle()hook API, parameters, return values, and error handlingFiles Added:
docs/reference/expo/use-google-sign-in.mdx- Complete API reference for the useSignInWithGoogle() hookdocs/guides/configure/auth-strategies/sign-in-with-google.expo.mdx- Comprehensive setup guide for Google Sign-InWhat changed?
Added API Reference Documentation: Created complete reference for
useSignInWithGoogle()hook including:createdSessionId,setActive,signIn,signUp)Added Setup Guide: Created detailed setup guide covering:
Checklist