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

docs/_partials/authentication/social-connections/enable-google-social-connection.mdx

@@ -0,0 +1,5 @@
+1. In the Clerk Dashboard, navigate to the [**SSO connections**](https://dashboard.clerk.com/~/user-authentication/sso-connections) page.
+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.

docs/_partials/expo/use-sign-in-with-google-example.mdx

@@ -0,0 +1,93 @@
+The following example demonstrates how to use the [`useSignInWithGoogle()`](/docs/reference/expo/use-sign-in-with-google) hook to manage the Google authentication flow. Because the `useSignInWithGoogle()` hook automatically manages the [transfer flow](!transfer-flow) between sign-up and sign-in, you can use this component for both your sign-up and sign-in pages.
+
+```tsx {{ filename: 'components/GoogleSignInButton.tsx', collapsible: true }}
+import { useSignInWithGoogle } from '@clerk/clerk-expo'
+import { useRouter } from 'expo-router'
+import { Alert, Platform, StyleSheet, Text, TouchableOpacity, View } from 'react-native'
+
+interface GoogleSignInButtonProps {
+  onSignInComplete?: () => void
+  showDivider?: boolean
+}
+
+export function GoogleSignInButton({
+  onSignInComplete,
+  showDivider = true,
+}: GoogleSignInButtonProps) {
+  const { startGoogleAuthenticationFlow } = useSignInWithGoogle()
+  const router = useRouter()
+
+  // Only render on iOS and Android
+  if (Platform.OS !== 'ios' && Platform.OS !== 'android') {
+    return null
+  }
+
+  const handleGoogleSignIn = async () => {
+    try {
+      const { createdSessionId, setActive } = await startGoogleAuthenticationFlow()
+
+      if (createdSessionId && setActive) {
+        await setActive({ session: createdSessionId })
+
+        if (onSignInComplete) {
+          onSignInComplete()
+        } else {
+          router.replace('/')
+        }
+      }
+    } catch (err: any) {
+      if (err.code === 'SIGN_IN_CANCELLED' || err.code === '-5') {
+        return
+      }
+
+      Alert.alert('Error', err.message || 'An error occurred during Google Sign-In')
+      console.error('Google Sign-In error:', JSON.stringify(err, null, 2))
+    }
+  }
+
+  return (
+    <>
+      <TouchableOpacity style={styles.googleButton} onPress={handleGoogleSignIn}>
+        <Text style={styles.googleButtonText}>Sign in with Google</Text>
+      </TouchableOpacity>
+
+      {showDivider && (
+        <View style={styles.divider}>
+          <View style={styles.dividerLine} />
+          <Text style={styles.dividerText}>OR</Text>
+          <View style={styles.dividerLine} />
+        </View>
+      )}
+    </>
+  )
+}
+
+const styles = StyleSheet.create({
+  googleButton: {
+    backgroundColor: '#4285F4',
+    padding: 15,
+    borderRadius: 8,
+    alignItems: 'center',
+    marginBottom: 10,
+  },
+  googleButtonText: {
+    color: '#fff',
+    fontSize: 16,
+    fontWeight: '600',
+  },
+  divider: {
+    flexDirection: 'row',
+    alignItems: 'center',
+    marginVertical: 20,
+  },
+  dividerLine: {
+    flex: 1,
+    height: 1,
+    backgroundColor: '#ccc',
+  },
+  dividerText: {
+    marginHorizontal: 10,
+    color: '#666',
+  },
+})
+```

docs/_partials/expo/web-client-id.mdx

@@ -0,0 +1,7 @@
+#### Create a Web Client ID and Client Secret
+
+1. In the same project, create another client. Next to **Credentials**, select **Create Credentials**. Then, select **OAuth client ID**.
+1. For the **Application type**, select **Web application**.
+1. Add a name (e.g., "Web client for token verification").
+1. Under **Authorized redirect URIs**, select **Add URI** and paste the **Authorized Redirect URI** you saved from the Clerk Dashboard.
+1. Select **Create**. A modal will open with your **Client ID** and **Client Secret**. Save these values somewhere secure. You'll need these for the following steps.

docs/guides/configure/auth-strategies/sign-in-with-google.expo.mdx

@@ -0,0 +1,203 @@
+---
+title: Sign in with Google
+description: Learn how to use Clerk to natively Sign in with Google in your Expo app.
+sdk: expo
+---
+
+<TutorialHero
+  beforeYouStart={[
+    {
+      title: "A Clerk application is required.",
+      link: "/docs/getting-started/quickstart/setup-clerk",
+      icon: "clerk",
+    },
+    {
+      title: "Follow the Expo quickstart",
+      link: "/docs/expo/getting-started/quickstart",
+      icon: "expo",
+    },
+    {
+      title: "A Google Developer account is required.",
+      link: "https://console.developers.google.com/",
+      icon: "user-circle",
+    },
+  ]}
+/>
+
+This guide will teach you how to add **native** [Sign in with Google](https://support.google.com/accounts/answer/12849458?hl=en) to your Clerk Expo application. This is different from Google OAuth - if you want to use Google OAuth, see the [dedicated guide](/docs/guides/configure/auth-strategies/social-connections/google).
+
+To make the setup process easier, it's recommended to keep two browser tabs open - one for the [Clerk Dashboard](https://dashboard.clerk.com/~/user-authentication/sso-connections) and one for your [Google Cloud Console](https://console.cloud.google.com/).
+
+<Steps>
+  ## Enable Google as a social connection
+
+  <Include src="_partials/authentication/social-connections/enable-google-social-connection.mdx" />
+
+  ## Configure Google Cloud Console
+
+  Before you can use Google Sign-In in your app, you need to create OAuth 2.0 credentials in the Google Cloud Console.
+
+  ### Create a Google Cloud Project
+
+  1. Navigate to the [Google Cloud Console](https://console.cloud.google.com/).
+  1. Select an existing project or [create a new one](https://console.cloud.google.com/projectcreate). You'll be redirected to your project's **Dashboard** page.
+  1. Enable the [**Google+ API**](https://console.cloud.google.com/apis/library/plus.googleapis.com?project=expo-testing-480017) for your project.
+
+  ### Create OAuth 2.0 credentials
+
+  You'll need to create two sets of OAuth 2.0 credentials: one for your native platform and one for the web client. **Even if you are building a native app, you still need to create the web client for Clerk's token verification.**
+
+  If you're building for both iOS and Android, ensure that you create all three sets of credentials (iOS, Android, and web).
+
+  <Tabs items={["iOS", "Android"]}>
+    <Tab>
+      #### Create an iOS Client ID
+
+      1. Navigate to [**APIs & Services**](https://console.cloud.google.com/apis/dashboard). Then, in the left sidebar, select **Credentials**.
+      1. Next to **Credentials**, select **Create Credentials**. Then, select **OAuth client ID**. You might need to [configure your OAuth consent screen](https://support.google.com/cloud/answer/6158849#userconsent). Otherwise, you'll be redirected to the **Create OAuth client ID** page.
+      1. For the **Application type**, select **iOS**.
+      1. Complete the required fields:
+         - **Name**: Add a name for your client.
+         - **Bundle ID**: Add your iOS **Bundle ID**.
+      1. Select **Create**. A modal will open with your **Client ID**. Copy and save the **Client ID** - you'll need this for `EXPO_PUBLIC_CLERK_GOOGLE_IOS_CLIENT_ID`.
+
+      <Include src="_partials/expo/web-client-id" />
+    </Tab>
+
+    <Tab>
+      #### Create an Android Client ID
+
+      1. In the same project, create another client. Next to **Credentials**, select **Create Credentials**. Then, select **OAuth client ID**.
+      1. For the **Application type**, select **Android**.
+      1. Complete the required fields:
+         - **Package name**: Your package name is in your `app.json` or `app.config.ts`.
+         - **SHA-1 certificate fingerprint**: To get your SHA-1, run the following command in your terminal:
+
+           ```sh {{ filename: 'terminal' }}
+           $ keytool -keystore path-to-debug-or-production-keystore -list -v
+           ```
+
+           > [!NOTE]
+           > Replace `path-to-debug-or-production-keystore` with the path to your debug or production keystore. By default, the debug keystore is located in `~/.android/debug.keystore`. It may ask for a keystore password, which is `android`. **Please note that Java is required to run the `keytool` command.**
+      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_ANDROID_CLIENT_ID`.
+
+      <Include src="_partials/expo/web-client-id" />
+    </Tab>
+  </Tabs>
+
+  ## Set the Client ID and Client Secret (from your web client) in the Clerk Dashboard
+
+  <Include src="_partials/authentication/social-connections/set-client-id-secret" />
+
+  ## Add your native application to Clerk
+
+  <Tabs items={["iOS", "Android"]}>
+    <Tab>
+      Add your iOS application to the [**Native Applications**](https://dashboard.clerk.com/~/native-applications) page in the Clerk Dashboard. You'll need your iOS app's **App ID Prefix** (Team ID) and **Bundle ID**.
+    </Tab>
+
+    <Tab>
+      Add your Android application to the [**Native Applications**](https://dashboard.clerk.com/~/native-applications) page in the Clerk Dashboard. You'll need your Android app's **package name**.
+    </Tab>
+  </Tabs>
+
+  ## Configure environment variables
+
+  Add the Google OAuth client IDs to your `.env` file. You'll have saved these values in the previous steps.
+
+  ```bash {{ filename: '.env' }}
+  EXPO_PUBLIC_CLERK_GOOGLE_WEB_CLIENT_ID=your-web-client-id.apps.googleusercontent.com
+  EXPO_PUBLIC_CLERK_GOOGLE_IOS_CLIENT_ID=your-ios-client-id.apps.googleusercontent.com
+  EXPO_PUBLIC_CLERK_GOOGLE_ANDROID_CLIENT_ID=your-android-client-id.apps.googleusercontent.com
+
+  # (iOS only)
+  # EXPO_PUBLIC_CLERK_GOOGLE_IOS_URL_SCHEME is the URL scheme for Google sign-in callback
+  # Replace your-ios-client-id with the same <your-ios-client-id> from EXPO_PUBLIC_CLERK_GOOGLE_IOS_CLIENT_ID. It should only be the part of your iOS Client ID before ".apps.googleusercontent.com".
+  EXPO_PUBLIC_CLERK_GOOGLE_IOS_URL_SCHEME=com.googleusercontent.apps.your-ios-client-id
+  ```
+
+  ## Set up native Sign in with Google (iOS only)
+
+  This step is for **iOS only** and is **optional**. Currently, Sign in with Google will open a web browser to initiate the flow. If you'd rather have the app handle the flow natively and not open a web browser, follow this step.
+
+  ### Configure the Clerk Expo plugin
+
+  The `@clerk/clerk-expo` config plugin configures the URL scheme needed for Google's authentication callback. Add the plugin to your `app.json` or `app.config.ts`, depending on your app's configuration:
+
+  > [!QUIZ]
+  > What is the difference between `app.json` and `app.config.ts`?
+  >
+  > ---
+  >
+  > `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.
+
+  <Tabs items={["app.json", "app.config.ts"]}>
+    <Tab>
+      Replace `your-ios-client-id` with the same `<your-ios-client-id>` from your `EXPO_PUBLIC_CLERK_GOOGLE_IOS_CLIENT_ID` environment variable (it should only be the part of your iOS Client ID before ".apps.googleusercontent.com").
+
+      ```json {{ filename: 'app.json' }}
+      {
+        "expo": {
+          "plugins": ["@clerk/clerk-expo"],
+          "extra": {
+            "EXPO_PUBLIC_CLERK_GOOGLE_IOS_URL_SCHEME": "com.googleusercontent.apps.your-ios-client-id"
+          }
+        }
+      }
+      ```
+    </Tab>
+
+    <Tab>
+      ```ts {{ filename: 'app.config.ts' }}
+      export default {
+        expo: {
+          plugins: ['@clerk/clerk-expo'],
+          extra: {
+            EXPO_PUBLIC_CLERK_GOOGLE_IOS_URL_SCHEME: process.env.EXPO_PUBLIC_CLERK_GOOGLE_IOS_URL_SCHEME,
+          },
+        },
+      }
+      ```
+    </Tab>
+  </Tabs>
+
+  The plugin resolves the `EXPO_PUBLIC_CLERK_GOOGLE_IOS_URL_SCHEME` value from either of the following:
+
+  1. An environment variable (recommended for EAS builds, configured in `eas.json`).
+  1. The `config.extra` field in your app config.
+
+  For EAS builds, add the environment variable to your build profile in `eas.json`:
+
+  ```json {{ filename: 'eas.json' }}
+  {
+    "build": {
+      "development": {
+        "env": {
+          "EXPO_PUBLIC_CLERK_GOOGLE_IOS_URL_SCHEME": "com.googleusercontent.apps.your-ios-client-id"
+        }
+      }
+    }
+  }
+  ```
+
+  ### Create the Sign in with Google button
+
+  The `<GoogleSSOButton />` component from the Expo quickstart will open a web browser to initiate the Sign in with Google flow. Replace it with the `<GoogleSignInButton />` component from the following example.
+
+  <Include src="_partials/expo/use-sign-in-with-google-example" />
+
+  ## Create a native build
+
+  Create a native build with EAS Build or a local prebuild, since Google Authentication is not supported in Expo Go.
+
+  ```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
+  ```
+</Steps>

docs/guides/configure/auth-strategies/sign-in-with-google.mdx

@@ -1,6 +1,6 @@
 ---
 title: Sign in with Google
-description: Learn how to configure Sign in with Google for your Clerk-powered Android app.
+description: Learn how to use Clerk to natively Sign in with Google in your Android app.
 sdk: android
 ---
 
@@ -15,24 +15,23 @@ sdk: 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",
+    },
   ]}
 />
 
-[Sign in with Google](https://support.google.com/accounts/answer/12849458?hl=en) helps you easily and securely sign in to third-party apps or services with your Google Account, without having to enter a username and password repeatedly across different services.
-
-This guide will teach you how to add native Sign in with Google to your Clerk apps on Android platforms. This is different from Google OAuth - if you want to use Google OAuth, see the [dedicated guide](/docs/guides/configure/auth-strategies/social-connections/google).
+This guide will teach you how to add native [Sign in with Google](https://support.google.com/accounts/answer/12849458?hl=en) to your Clerk apps on Android platforms. This is different from Google OAuth - if you want to use Google OAuth, see the [dedicated guide](/docs/guides/configure/auth-strategies/social-connections/google).
 
 To make the setup process easier, it's recommended to keep two browser tabs open - one for the [Clerk Dashboard](https://dashboard.clerk.com/~/user-authentication/sso-connections) and one for your [Google Cloud Console](https://console.cloud.google.com/).
 
 <Steps>
   ## Enable Google as a social connection
 
-  1. In the Clerk Dashboard, navigate to the [**SSO connections**](https://dashboard.clerk.com/~/user-authentication/sso-connections) page.
-  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.
+  <Include src="_partials/authentication/social-connections/enable-google-social-connection.mdx" />
 
   ## Create the Google Developer Android client
 
@@ -41,7 +40,7 @@ To make the setup process easier, it's recommended to keep two browser tabs open
   1. In the top-left, select the menu icon (**≡**) and select **APIs & Services**. Then, select **Credentials**.
   1. Next to **Credentials**, select **Create Credentials**. Then, select **OAuth client ID.** You might need to [configure your OAuth consent screen](https://support.google.com/cloud/answer/6158849#userconsent). Otherwise, you'll be redirected to the **Create OAuth client ID** page.
   1. For the **Application type**, select **Android**.
-  1. Complete the required fields.
+  1. Complete the required fields:
      - **Package name**: Your package name is in your `build.gradle` file, formatted as `com.example.myclerkapp`.
      - **SHA-1 certificate fingerprint**: To get your SHA-1, run the following command in your terminal:
 

docs/guides/configure/auth-strategies/social-connections/google.mdx

@@ -23,6 +23,11 @@ Enabling OAuth with [Google](https://developers.google.com/identity/protocols/oa
 > [!WARNING]
 > Google OAuth 2.0 **does not** allow apps to use WebViews for authentication. See the dedicated [Google blog post](https://developers.googleblog.com/en/modernizing-oauth-interactions-in-native-apps-for-better-usability-and-security) for more information. If your app requires users to sign in via in-app browsers, follow the setup instructions in the [Google Help guide](https://support.google.com/faqs/answer/12284343).
 
+<If sdk={["expo", "android"]}>
+  > [!IMPORTANT]
+  > This guide explains how to configure Sign in with Google for web-based flows. To configure Sign in with Google on native applications (such as Android or Expo apps), see the [dedicated guide](/docs/guides/configure/auth-strategies/sign-in-with-google).
+</If>
+
 ## Configure for your development instance
 
 For _development instances_, Clerk uses preconfigured shared OAuth credentials and redirect URIs—no other configuration is needed.
@@ -41,11 +46,7 @@ To make the setup process easier, it's recommended to keep two browser tabs open
 <Steps>
   ### Enable Google as a social connection
 
-  1. In the Clerk Dashboard, navigate to the [**SSO connections**](https://dashboard.clerk.com/~/user-authentication/sso-connections) page.
-  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.
+  <Include src="_partials/authentication/social-connections/enable-google-social-connection.mdx" />
 
   ### Create a Google Developer project
 

docs/manifest.json

@@ -1717,6 +1717,10 @@
                           "title": "`useSignInWithApple()`",
                           "href": "/docs/reference/expo/use-sign-in-with-apple"
                         },
+                        {
+                          "title": "`useSignInWithGoogle()`",
+                          "href": "/docs/reference/expo/use-sign-in-with-google"
+                        },
                         {
                           "title": "`useSSO()`",
                           "href": "/docs/reference/expo/use-sso"