Add guides for native Sign in with Google in Expo and document useSig…

[chriscanin]

🔎 Previews:

What does this solve?

• Adds comprehensive documentation for developers implementing native Google Sign-In in their Expo apps
• Provides step-by-step setup instructions for configuring Google OAuth credentials and Clerk integration
• Documents the new useSignInWithGoogle() hook API, parameters, return values, and error handling

Files Added:

• docs/reference/expo/use-google-sign-in.mdx - Complete API reference for the useSignInWithGoogle() hook
• docs/guides/configure/auth-strategies/sign-in-with-google.expo.mdx - Comprehensive setup guide for Google Sign-In

What changed?

• Added API Reference Documentation: Created complete reference for useSignInWithGoogle() hook including:

  • Method signature with TypeScript types
  • Return value descriptions (createdSessionId, setActive, signIn, signUp)
  • Three practical examples: basic usage, with custom metadata, and reusable component
  • Comprehensive error handling guide covering user cancellation, platform errors, missing packages, and Play Services issues

• Added Setup Guide: Created detailed setup guide covering:

  • Google Cloud Console configuration (creating Web, iOS, and Android OAuth 2.0 credentials)
  • SHA-1 certificate fingerprint generation for Android debug and release builds
  • Adding iOS and Android apps to Clerk Dashboard Native Applications
  • Enabling Google as an SSO connection in Clerk
  • Environment variable configuration for client IDs
  • App config integration with proper expo plugin setup
  • Build requirements and instructions (prebuild vs EAS Build)

Checklist

• I have clicked on "Files changed" and performed a thorough self-review
• All existing checks pass

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Updated (UTC)
clerk-docs	Ready	Preview	Dec 5, 2025 6:42pm

[SarahSoutoul]

@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.

[SarahSoutoul]

@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.

[SarahSoutoul]

Second docs review added here: docs review pt2 @chriscanin.

@alexisintech tagging you for visibility if you wanted to have a look at this PR!