From 996f7bb3fcd3617bf3ce21ee069bd18df33e45ee Mon Sep 17 00:00:00 2001 From: Stojan Dimitrovski Date: Thu, 22 Jun 2023 12:02:32 +0200 Subject: [PATCH] docs: adjust wording per suggestions from Tyler --- .../pages/guides/auth/social-login/auth-google.mdx | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/apps/docs/pages/guides/auth/social-login/auth-google.mdx b/apps/docs/pages/guides/auth/social-login/auth-google.mdx index 83a30b49d6e..fea9733b444 100644 --- a/apps/docs/pages/guides/auth/social-login/auth-google.mdx +++ b/apps/docs/pages/guides/auth/social-login/auth-google.mdx @@ -93,11 +93,13 @@ For apps written in Kotlin, please consult the [community maintained library](/d ### Configuration -1. Configure OAuth credentials for your Google Cloud project in the [Credentials](https://console.cloud.google.com/apis/credentials) page of the console. When creating a new OAuth client ID, choose _Android_ for the application type. Use the instructions on screen to provide the SHA-1 certificate fingerprint used to sign your Android app. +1. Configure OAuth credentials for your Google Cloud project in the [Credentials](https://console.cloud.google.com/apis/credentials) page of the console. When creating a new OAuth client ID, choose _Android_ or _iOS_ depending on the mobile operating system your app is built for. + - For Android, use the instructions on screen to provide the SHA-1 certificate fingerprint used to sign your Android app. + - For iOS, use the instructions on screen to provide the app Bundle ID, and App Store ID and Team ID if the app is already published on the Apple AppStore. 2. Configure the [OAuth Consent Screen](https://console.cloud.google.com/apis/credentials/consent). This information is shown to the user when giving consent to your app. In particular, make sure you have set up links to your app's privacy policy and terms of service. 3. Finally, add the client ID from step 1 in the [Google provider on the Supabase Dashboard](https://supabase.com/dashboard/project/_/auth/providers), under _Authorized Client IDs_. -Note that you do not have to configure the OAuth flow in order to use native sign in. +Note that you do not have to configure the OAuth flow in the Supabase Dashboard in order to use native sign in. ## Using native sign in for Chrome extensions @@ -159,7 +161,7 @@ You will need to configure a client ID for your Chrome extension: 2. Configure the [OAuth Consent Screen](https://console.cloud.google.com/apis/credentials/consent). This information is shown to the user when giving consent to your app. 3. Finally, add the client ID from step 1 in the [Google provider on the Supabase Dashboard](https://supabase.com/dashboard/project/_/auth/providers), under _Authorized Client IDs_. -Note that you do not have to configure the OAuth flow in order to use sign in with Chrome extensions. +Note that you do not have to configure the OAuth flow in the Supabase Dashboard to sign in with Google inside Chrome extensions. ## Using personalized sign-in buttons, One Tap or automatic sign-in @@ -211,7 +213,7 @@ Use of nonce is recommended, though optional. Make sure each nonce is generated 2. Configure the [OAuth Consent Screen](https://console.cloud.google.com/apis/credentials/consent). This information is shown to the user when giving consent to your app. In particular, make sure you have set up links to your app's privacy policy and terms of service. 3. Finally, add the client ID from step 1 in the [Google provider on the Supabase Dashboard](https://supabase.com/dashboard/project/_/auth/providers) under _Authorized Client IDs_. -Note that you do not have to configure the OAuth flow client ID and secret when using this approach! +Note that you do not have to configure the OAuth flow client ID and secret in the Supabae Dashboard when using this approach! export const Page = ({ children }) =>