A Flutter package that implements Google Sign In
in pure Dart. This package is compatible with google_sign_in
plugin
and works on all platforms Flutter supports but it's intended to be
mainly used on Desktop.
- Depend on it
dependencies: google_sign_in: ^4.1.4 google_sign_in_dartio: ^0.0.6
- Run
flutter pub get
- Import
import 'package:google_sign_in/google_sign_in.dart'; import 'package:google_sign_in_dartio/google_sign_in_dartio.dart';
- Register the package
Note: You might want to
import 'package:flutter/material.dart'; import 'package:google_sign_in/google_sign_in.dart'; import 'package:google_sign_in_dartio/google_sign_in_dartio.dart'; void main() { if (isDesktop) { GoogleSignInPlatform.register(clientId: <clientId>); } runApp(MyApp()); }
await
for theregister
method to finish before calling anyGoogleSignIn
methods when your app starts.
You can use the normal GoogleSignIn
methods.
final GoogleSignInAccount account = await GoogleSignIn().signIn();
- Go to the Google Cloud Platform console and select you project
- Go to
APIs & Service
->Credentials
- Create new credentials for your app by selecting
CREATE CREDENTIALS
and thenOAuth client ID
- Select
Other
asApplication type
, give it a name (eg. macOS) and then clickCreate
The user accessToken
expires after about one hour, after witch you need to ask the user to login again. If you want to
keep the user logged in, you need to deploy a oAuth code exchange endpoint. Once you have your endpoint you can register
the package like this.
If you use this only for FirebaseAuth you don't need the code exchange since the token must be valid only when you
use the signInWithCredentials
method.
import 'package:flutter/material.dart';
import 'package:google_sign_in/google_sign_in.dart';
import 'package:google_sign_in_dartio/google_sign_in_dartio.dart';
void main() {
if (isDesktop) {
GoogleSignInPlatform.register(
clientId: <clientId>,
exchangeEndpoint: <endpoint>,
);
}
runApp(MyApp());
}
GoogleSignInTokenData
exposes serverAuthCode
field that should
contain the exchange code from the authorization request. This will
always be null when using this package because we already allow you to
provide a code exchange endpoint witch exposes the code and code
verifier in a trusted environment and encourages not to do the code
exchange on the client.
See instruction on how to deploy a code exchange endpoint.