DEV Community

Cathy Lai
Cathy Lai

Posted on

Login with Google on an iPhone (Local Metro server + Dev Build) - Part 4/7: Google Cloud Console

Configure oAuth

So now we will create

  1. The Project: This is our top-level container (e.g., "My Startup"). We only need one project for all our apps.

  2. The Consent Screen: We configure this once per project. This is what users see when they log in (logo, privacy policy link, etc.).

  3. Client IDs: We create multiple of these within the same project.

Step 1/3 - Create a Project

Google Cloud Console - Welcome

Google Cloud Console - New Project

Fill in the Project Name and then "Create"
Google Cloud Console - Project Name

Select "API and Services"
Google Cloud Console - API and Services

Select oAuth Consent Screen
Google Cloud Console - oAuth Consent Screen option

Step 2/3: Create a New App

"Get Started"
Google Cloud Console Create an App

Fill in the App name and the email, the "Next"
Google Cloud Console - Name and Email

Fill in the rest of the information and Finish
Google Cloud Console - Emails

Google Cloud Console - 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
Google Cloud Console - New oAuth Client

Make sure "iOS" is selected and Bundle Id matches to our app
Google Cloud Console - oAuth Client Config

It should match the bundle name in app.json

Client created!

Side Note

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.

Top comments (0)