From cd0ada033cdaee8dc8a960e6c0516a2247557236 Mon Sep 17 00:00:00 2001 From: Vojtech Novak Date: Sun, 8 Sep 2024 19:26:02 +0200 Subject: [PATCH] docs: even better developer_error troubleshooting (#25) --- docs/setting-up/get-config-file.mdx | 13 +++++++------ docs/troubleshooting.md | 2 +- 2 files changed, 8 insertions(+), 7 deletions(-) diff --git a/docs/setting-up/get-config-file.mdx b/docs/setting-up/get-config-file.mdx index dc04990..740d95b 100644 --- a/docs/setting-up/get-config-file.mdx +++ b/docs/setting-up/get-config-file.mdx @@ -10,12 +10,12 @@ Please note that you **do not** need Firebase to configure Google Sign In. Howev Read below on how to set up Google Sign In for your Android app. -### Obtain SHA-1 certificate fingerprints - -:::warning -This is crucial for Google Sign-In to work on Android. If not done correctly, you will get the infamous [`DEVELOPER_ERROR` error](/docs/troubleshooting#developer_error). +:::danger +Completing this guide is crucial for Google Sign-In to work on Android. If not done correctly, you will get the infamous `DEVELOPER_ERROR` error [(how to troubleshoot it)](/docs/troubleshooting#developer_error). ::: +### Obtain SHA-1 certificate fingerprints + You likely have multiple signing configurations - for example for building local debug and release APKs, builds on [Expo EAS](https://docs.expo.dev/app-signing/managed-credentials/#inspecting-credentials-configuration), and [Play App Signing](https://support.google.com/googleplay/android-developer/answer/9842756?hl=en) for production deployments. You will need to get the SHA1 certificate fingerprints for _all_ keystores you intend to use and enter them _all_ in Firebase or Google Cloud Console. @@ -34,9 +34,10 @@ import TabItem from '@theme/TabItem'; Check if "Google Play App Signing" is enabled for your app [in the console](https://play.google.com/console/u/0/). - If it is enabled, you need to obtain the "App signing certificate" `SHA-1`. + If it is enabled, you need to take the following steps: - You can find it at: App -> Release (in the left sidebar) -> Setup -> App integrity. Under the App signing key certificate, copy `SHA-1 certificate fingerprint`. +1. In Google Play Console, navigate to: \ -> Release section (in the left sidebar) -> Setup -> App Signing. +2. Under the "App signing key certificate" _and also_ "Upload key certificate", take note of `SHA-1 certificate fingerprint`. diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index 8982ad2..03e112d 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -22,7 +22,7 @@ This is always (_always_!) a configuration mismatch between your app and Google' Follow these pointers: - [Search the issue tracker](https://github.com/react-native-google-signin/google-signin/issues?q=is%3Aissue+DEVELOPER+ERROR+is%3Aclosed) for old reports of the error -- Make sure that your SHA certificate fingerprints and package name you entered in Firebase / Google Cloud Console are correct. If you are in development, make sure your development signing fingerprint is added as well. +- Make sure that your SHA certificate fingerprints and package name you entered in Firebase / Google Cloud Console are correct. [See how your app was signed](https://x.com/vonovak/status/1692127631473529226). If you are in development, make sure your development signing fingerprint is added as well. - Follow the [setup guide](/docs/setting-up/get-config-file) and perform its steps once again. - If you're passing `webClientId` in configuration object to `GoogleSignin.configure()` make sure it's correct and that it is of type web (NOT Android!). You can get your `webClientId` from [Google Developer Console](https://console.developers.google.com/apis/credentials). It is listed under "OAuth 2.0 client IDs".