We have previously finished Clerk side of config in Part 3! Here we will configure the Google side. We will create
A Project: This is our top-level container (e.g., "My Startup"). We only need one project for all our apps.
The Consent Screen: We configure this once per project. This is what users see when they log in (logo, privacy policy link, etc.).
Client IDs: We create multiple of these within the same project.
Step 1/3 - Create a Project
Fill in the Project Name and then "Create"
Select "API and Services"
Select oAuth Consent Screen
Step 2/3: Create a New App
"Get Started"
Fill in the App name and the email, the "Next"
Fill in the rest of the information and Finish
Step 3/3 - Create a New oauth Client
We will need one Client for each app/platform/env (eg iOS, Android, web; development, preview, production).
For now we are just add one for iOS/development.
Create a new oAuth Client
Make sure "iOS" is selected and Bundle Id matches to our app
It should match the bundle name in app.json
Client created!
Explanation
By default, for Development Instances, Clerk provides "Shared Credentials" for popular providers like Google.
When you created an iOS type credential in Google Cloud, Google purposefully omitted the Client Secret. Instead, it uses your Bundle ID to verify the app's identity.
Problem?
If you’re having trouble finding your OAuth Client ID or Client Secret, I’ve documented multiple ways to locate them (even if the menu layout has changed):
Login with Google (oAuth) - Finding Client ID & Secret in Google Cloud Console (2026)
Top comments (0)