From 5d82d3867fa3745b8486f62436e3c1c8a99cece8 Mon Sep 17 00:00:00 2001 From: Luca Kermas Date: Wed, 28 Jan 2026 21:32:45 +0100 Subject: [PATCH 1/4] Add tips for serverClientId on android --- .../11-authentication/04-providers/02-google/01-setup.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/06-concepts/11-authentication/04-providers/02-google/01-setup.md b/docs/06-concepts/11-authentication/04-providers/02-google/01-setup.md index d6230ad9..13da8098 100644 --- a/docs/06-concepts/11-authentication/04-providers/02-google/01-setup.md +++ b/docs/06-concepts/11-authentication/04-providers/02-google/01-setup.md @@ -182,6 +182,10 @@ Fill in all required information, you can get the debug SHA-1 hash by running `. Put the file inside the `android/app/` directory and rename it to `google-services.json`. +:::tip +If your `google-services.json` does not include a web OAuth client entry, you may need to pass the `serverClientId` when [initializing the GoogleSignInService](#present-the-authentication-ui) +::: + :::info For a production app you need to get the SHA-1 key from your production keystore! This can be done by running this command: ([Read more](https://support.google.com/cloud/answer/6158849#installedapplications&android&zippy=%2Cnative-applications%2Candroid)). @@ -240,6 +244,10 @@ void main() { } ``` +:::tip +You may need to provide client IDs programmatically as described on the [configuration page](#configuring-client-ids-on-the-app) +::: + ### Using GoogleSignInWidget If you have configured the `SignInWidget` as described in the [setup section](../../setup#present-the-authentication-ui), the Google identity provider will be automatically detected and displayed in the sign-in widget. From d8fd4057e784fd9afbc750f1992466241bab45e8 Mon Sep 17 00:00:00 2001 From: Luca Kermas Date: Wed, 28 Jan 2026 21:34:00 +0100 Subject: [PATCH 2/4] Use only one info --- .../11-authentication/04-providers/02-google/01-setup.md | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/docs/06-concepts/11-authentication/04-providers/02-google/01-setup.md b/docs/06-concepts/11-authentication/04-providers/02-google/01-setup.md index 13da8098..5a0537f9 100644 --- a/docs/06-concepts/11-authentication/04-providers/02-google/01-setup.md +++ b/docs/06-concepts/11-authentication/04-providers/02-google/01-setup.md @@ -182,8 +182,8 @@ Fill in all required information, you can get the debug SHA-1 hash by running `. Put the file inside the `android/app/` directory and rename it to `google-services.json`. -:::tip -If your `google-services.json` does not include a web OAuth client entry, you may need to pass the `serverClientId` when [initializing the GoogleSignInService](#present-the-authentication-ui) +:::info +If your `google-services.json` does not include a web OAuth client entry, you may need to provide client IDs programmatically as described on the [configuration page](#configuring-client-ids-on-the-app). ::: :::info @@ -244,10 +244,6 @@ void main() { } ``` -:::tip -You may need to provide client IDs programmatically as described on the [configuration page](#configuring-client-ids-on-the-app) -::: - ### Using GoogleSignInWidget If you have configured the `SignInWidget` as described in the [setup section](../../setup#present-the-authentication-ui), the Google identity provider will be automatically detected and displayed in the sign-in widget. From afdd7480af31c2a7dcf01101c8d780a9d123cf9e Mon Sep 17 00:00:00 2001 From: Luca Kermas Date: Wed, 28 Jan 2026 21:49:46 +0100 Subject: [PATCH 3/4] fix anchor --- .../11-authentication/04-providers/02-google/01-setup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/06-concepts/11-authentication/04-providers/02-google/01-setup.md b/docs/06-concepts/11-authentication/04-providers/02-google/01-setup.md index 5a0537f9..896a5c60 100644 --- a/docs/06-concepts/11-authentication/04-providers/02-google/01-setup.md +++ b/docs/06-concepts/11-authentication/04-providers/02-google/01-setup.md @@ -183,7 +183,7 @@ Fill in all required information, you can get the debug SHA-1 hash by running `. Put the file inside the `android/app/` directory and rename it to `google-services.json`. :::info -If your `google-services.json` does not include a web OAuth client entry, you may need to provide client IDs programmatically as described on the [configuration page](#configuring-client-ids-on-the-app). +If your `google-services.json` does not include a web OAuth client entry, you may need to provide client IDs programmatically as described on the [configuration page](./configurationƒ#configuring-client-ids-on-the-app). ::: :::info From 40bb974a6f501d0e2a27c718fd8069823a594bcc Mon Sep 17 00:00:00 2001 From: Luca Kermas Date: Wed, 28 Jan 2026 21:54:37 +0100 Subject: [PATCH 4/4] damn. fix typo --- .../11-authentication/04-providers/02-google/01-setup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/06-concepts/11-authentication/04-providers/02-google/01-setup.md b/docs/06-concepts/11-authentication/04-providers/02-google/01-setup.md index 896a5c60..d5d72451 100644 --- a/docs/06-concepts/11-authentication/04-providers/02-google/01-setup.md +++ b/docs/06-concepts/11-authentication/04-providers/02-google/01-setup.md @@ -183,7 +183,7 @@ Fill in all required information, you can get the debug SHA-1 hash by running `. Put the file inside the `android/app/` directory and rename it to `google-services.json`. :::info -If your `google-services.json` does not include a web OAuth client entry, you may need to provide client IDs programmatically as described on the [configuration page](./configurationƒ#configuring-client-ids-on-the-app). +If your `google-services.json` does not include a web OAuth client entry, you may need to provide client IDs programmatically as described on the [configuration page](./configuration#configuring-client-ids-on-the-app). ::: :::info