docs: Clarify Google sign-in setup for web and Android - #724
Merged
Conversation
developerjamiu
force-pushed
the
docs/google-setup-clarity
branch
from
July 30, 2026 10:48
ab1b0fc to
de4a260
Compare
Zfinix
reviewed
Jul 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes friction found by walking the Google sign-in setup guide end to end against a fresh 4.0.0-beta.1 project, testing on Android (emulator) and web.
Setup page
flutter run -d chromedoesn't work" caveat move into a warning placed before the build command, since setting up around the dev server is the natural mistake and the page only warned about it afterwards. The build command gains--base-href /app/(without it the app loads blank under/app;FlutterRouteserves files as-is, and the project template's ownflutter_buildscript includes the flag) and a "replacemy_project_server" sentence matching the page's placeholder pattern./appis a compiled snapshot, somain.dartchanges need a rebuild. Testing showed a stale build is an easy way to hitredirect_uri_mismatchafter correcting a redirect URI.google-services.jsonsteps are removed. The Auth Platform download is a client-secret JSON, not agoogle-services.json, and a plain Flutter project has nocom.google.gms.google-servicesGradle plugin to read one, so the step cannot supply the server client ID. PassingserverClientId(the Web client's ID) is now the primary path, shown in the initialize snippet's mobile branch;google-services.jsonremains as a note for Firebase-based projects. Verified against the failureGoogleSignInException(clientConfigurationError, serverClientId must be provided on Android)and confirmed working after the change.localhost, linking the new troubleshooting entry.Troubleshooting page
redirect_uri_mismatchcause: stale web build.assets/config.jsonpinslocalhost, which overrides the framework's10.0.2.2emulator handling; resolution via--dart-define=SERVER_URL=...).Follow-up (not in this PR): the template shipping
assets/config.jsonwithlocalhostaffects every scaffolded project on Android and is being raised as a framework issue; the endpoints page's "localhost adapts to the platform" wording should be revisited once that lands.