Skip to content

docs: crosslink web sections #87

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.

Sign up for GitHub

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

Merged
vonovak merged 1 commit into from
Nov 4, 2025
Merged

docs: crosslink web sections #87

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 4 additions & 0 deletions docs/setting-up/web.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -68,3 +68,7 @@ After the script is loaded, you can call the functions for signing in and render
If you call any of the module functions before the client library is loaded, such calls trigger the [`onError` callback](/docs/api#webonetapsignincallbacks) with the [`PLAY_SERVICES_NOT_AVAILABLE` error code](../errors#status-codes).

You can read the official docs for loading the Client Library [here](https://developers.google.com/identity/gsi/web/guides/client-library).

## Usage

See [here](../web-support#usage).
4 changes: 4 additions & 0 deletions docs/web-support.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,10 @@ On the web, the `signIn` and `createAccount` functions are not `Promise`-based b
The reason for callback-based apis rather than promise-based is that it's possible to get into an "error" state (when one-tap is not available) and later get a successful sign in from the button flow. Because of how the Google Sign In for web SDK is done, modeling this with a promise-based api is not possible.
:::

## Setup

See [here](setting-up/web).

## Usage

To implement web support, follow these two steps:
Expand Down