The implementation currently in use. This should be one of the following depending on the platform in use and the functionality supported by this extension:

• Android
• iOS
• default
• unknown

Whether the current device supports the extensions functionality

The native version string of the native extension.

The singleton instance of the GoogleIdentity class.

The version of this extension.

This should be of the format, MAJOR.MINOR.BUILD

Constructor You should not call this directly, but instead use the singleton access

Disconnects the current user from the app and revokes previous authentication. If the operation succeeds, the OAuth 2.0 token is also removed from keychain.

Once disconnect is called you can expect signInSilently to fail.

Disposes the extension and releases any allocated resources. Once this function has been called, a call to init is neccesary again before any of the extensions functionality will work.

Get a valid access token and a valid ID token, refreshing them first if they have expired or are about to expire.

Parameters

Get the current GoogleUser. Will return null if there is no user signed in.

Initialises the extension class for use with the provided key.

Parameters

Returns true if there is a currently signed in user.

Setup the Google Identity settings and initiate a connection to the API services. Most importantly this call sets the client IDs for your application.

Parameters

         GoogleIdentity.service.addEventListener( GoogleIdentityEvent.SETUP_COMPLETE, setupCompleteHandler );
         
         var options:GoogleIdentityOptions = new GoogleIdentityOptions( "ANDROID_CLIENT_ID", "IOS_CLIENT_ID" );
         GoogleIdentity.service.setup( options );
         
         private function setupCompleteHandler( event:GoogleIdentityEvent ):void
         {
             // Setup is complete, can call sign in etc now
             GoogleIdentity.service.signInSilently();
         }
         

Starts the user initiated sign-in process

If the user has previously accepted authentication etc then you can expect a silent sign in at startup to succeed. You can do this early in your application to automatically sign in returning users.

It will dispatch an ERROR event if sign in fails, generally if the user hasn't signed in previously. You should call signIn at some other point in your application.

Marks current user as being in the signed out state

Dispatched when the user has been disconnected from this application.

An error occured

error and errorCode will contain details of the error that occurred.

- SIGN_IN_CANCELLED [12501]: The sign in was cancelled by the user. i.e. user cancelled some of the sign in resolutions, e.g. account picking or OAuth consent. - SIGN_IN_FAILED [12500]: The sign in attempt didn't succeed with the current account. Unlike SIGN_IN_REQUIRED. when seeing this error code, there is nothing user can do to recover from the sign in failure. - SIGN_IN_REQUIRED [4]: The client attempted to connect to the service but the user is not signed in. - INTERNAL_ERROR [8]: An internal error occurred. Retrying should resolve the problem. - INVALID_ACCOUNT [5]: The client attempted to connect to the service with an invalid account name specified. - NETWORK_ERROR [7]: A network error occurred. Retrying should resolve the problem.

Dispatched when setup is complete. You should wait for this event before attempting any other functionality.

Dispatched when sign in completes. user will contain a valid GoogleUser object.

At this point the access and id tokens may not be valid. If you are planning on using them you should now call getToken and listen for the completion event.

Dispatched when the user has been signed out.

Dispatched when the tokens failed to be retrieved or refreshed.

Dispatched when a call to getToken has completed successfully

The access and id tokens in the user object will now be valid.