PANEL: SIGN IN WITH GOOGLE
Lets your app offer a “Sign in with Google” button. The panel shows the two values Google’s console asks for (package name and the signing key’s SHA-1), walks through creating the OAuth clients, and stores the resulting client IDs in the app. Nothing is sent to Google until a user taps the button.
OAUTH CLIENT IDGoogle’s name for “this app is allowed to ask users to sign in”. One is created per platform (an Android client and an iOS client); each looks like …apps.googleusercontent.com. Never paste a client secret — mobile apps do not use one, and the panel rejects it.
SHA-1 FINGERPRINTA checksum of the key that signs your Android app. Google requires it so a look-alike app cannot borrow your client ID. Sorvel already holds the key; the panel shows the fingerprint after your first Android build.
ID TOKENWhat the app receives after a successful sign-in: a signed statement from Google saying who the user is (with the email). The app hands it, together with a nonce, to your backend — for Supabase that is signInWithIdToken. It does not open a session on its own.
BUILT APP ONLYGoogle only redirects back to a real installed app, so this cannot be tried in Expo Go or in the browser preview. Use a development build or an APK. On iOS, offering Google means the App Store also requires Sign in with Apple; the kit ships both.