-
Notifications
You must be signed in to change notification settings - Fork 935
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. |
|
Second docs review added here: docs review pt2 @chriscanin. @alexisintech tagging you for visibility if you wanted to have a look at this PR! |
will check out today! |
|
quick update: before the christmas break, on dec 18th, chris still had to wrap some things up with this feature, and wasn't comfortable releasing it before the break (as if something happened during break, he wouldn't be available to handle it, rightfully so!! 🎄). chris will have an update on this soon, so that we can keep this feature and PR moving forward 🙏 |
|
Hey @alexisintech , the JS repo has been merged into main for the core-3 release. I am working on a PR to merge into core-2. |
awesome! once that's done, you and I can go through testing for core 2 so that we can get this PR merged (we can even do both core 2 and core 3, if you want!) |
|
@alexisintech I have created another PR and drafted it, this new PR will be for the core-3 release, to ensure when core-3 goes out, our docs are updated. |
| ```bash {{ filename: 'terminal' }} | ||
| # Using EAS Build | ||
| eas build --platform ios | ||
| eas build --platform android | ||
|
|
||
| # Or using local prebuild | ||
| npx expo prebuild && npx expo run:ios --device | ||
| npx expo prebuild && npx expo run:android --device | ||
| ``` |
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.
Slight suggestion that doesn't need to be taken. But, I was thinking we could also have this under <Tabs> with Android and iOS as options, like we did for the rest of the file. @alexisintech
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.
yeah i considered that too! 🧠 👯 was going to test android first, and see what in the entire doc was going to get updated (bc i'm still not sure if tabs is the right direction, but won't know until we test android)
| title: "A Google Developer account is required.", | ||
| link: "https://console.developers.google.com/", | ||
| icon: "user-circle", | ||
| } | ||
| }, | ||
| { | ||
| title: "Follow the Android quickstart", | ||
| link: "/docs/android/getting-started/quickstart", | ||
| icon: "android", | ||
| }, |
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.
@alexisintech Not a massive issue, but do we want to align the order of these to be consistent with the order in the Expo guide.
Android
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.
sure 9d51926
| > | ||
| > --- | ||
| > | ||
| > `app.json` is for projects using static JSON configuration (simpler projects). `app.config.ts` is for projects that need dynamic configuration (environment variables, conditional logic, etc.). The `app.config.ts` is the TypeScript version of `app.json` and will overwrite `app.json` with any values that it has. |
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.
app.json is for projects using static JSON configuration. app.config.ts is for projects that need dynamic configuration (environment variables, conditional logic, etc.). When both files exist, app.config.ts receives the values from app.json and can extend or override them. Choose the tab below based on which configuration approach your project uses.
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.
updated: 72403f0
|
update: the web browser version of sign in with google is working, chris is getting the native version working and then we will test that for ios, and then test the guide for android 👍 |

🔎 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