Skip to content

clarifications for OAuth Clients in Google Console with examples #73

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions docs/setting-up/get-config-file.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -86,6 +86,21 @@ You will _NOT_ need the created IDs later - the only goal here is for them to be

![Google Cloud Console - creating Android OAuth ID](/img/android-client-id.png)


Let's say you're using an Expo app. You'll end up with an OAuth Client per build. In Expo, you need one for `development` (used when running with, for example, `npx expo run:android`; SHA-1 usually obtained from `keytool -list -v -keystore android/app/debug.keystore -alias androiddebugkey -storepass android -keypass android`) and `production` (what ends up on the Google Play Store for users to download; obtained from `eas credentials` > `choose production`).

![Google Cloud Console - Google Console example with Clients per build](/img/google-console-with-oauth-examples-per-build.png)

:::info
Your code doesn't need to reference the Android Clients, only the Web Client, like so:

```
GoogleSignin.configure({
webClientId: 608470570303-kgb[redacted]apps.googleusercontent.com,
})
```
:::

</TabItem>

</Tabs>
Expand Down
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.