The client attempted to call a method from an API that failed to connect. Possible reasons include:

• The API previously failed to connect with a resolvable error, but the user declined the resolution.
• The device does not support GmsCore.
• The specific API cannot connect on this device.

The result was canceled either due to client disconnect or PendingResult.cancel().

The connection was suspended while the call was in-flight.

API calls will be failed with this status if ServiceConnection.onServiceDisconnected(ComponentName) is called by the Android platform before the call is completed.

This indicates that the underlying service was bound, since onServiceDisconnected should never be called unless onServiceConnected was called first.

It is possible this failure could be resolved by retrying.

The application is misconfigured. This error is not recoverable and will be treated as fatal. The developer should look at the logs after this to determine more actionable information.

The operation failed with no more detailed information.

An internal error occurred. Retrying should resolve the problem.

A blocking call was interrupted while waiting and did not run to completion.

The client attempted to connect to the service with an invalid account name specified.

A network error occurred. Retrying should resolve the problem.

The connection timed-out while attempting to re-connect.

This failure indicates a connection to Google Play services was successfully established, however it was disconnected for some reason (for example, Google Play services crashed), and re-connecting took longer than expected.

Any API calls failed with this status would have been initiated after the connection was disconnected.

The connection timed-out while waiting for Google Play services to update.

This failure indicates a connection to Google Play services was successfully established, however it was disconnected because Google Play services was updated, and the update took far longer than expected.

Any API calls failed with this status would have been initiated after the disconnection for the update.

There was a non-DeadObjectException RemoteException while calling a connected service.

This signifies that an API was able to connect to Google Play services and received an instance, but that when calling an individual method, a RemoteException was thrown.

Note that the exception would not be a DeadObjectException, which indicates that the binding has died (for example if the remote process died). This is because DeadObjectExceptions are handled by the connection management infrastructure of GoogleApi.

If this is encountered during an API call for an API that uses the Google Play services ServiceBroker (most do), it is after a bound service is successfully received from the ServiceBroker.

Completing the operation requires some form of resolution. A resolution will be available to be started with Status.startResolutionForResult(Activity, int). If the result returned is Activity.RESULT_OK, then further attempts should either complete or continue on to the next issue that needs to be resolved.

The installed version of Google Play services has been disabled on this device. The calling activity should pass this error code to GoogleApiAvailability.getErrorDialog(Activity, int, int) to get a localized error dialog that will resolve the error when shown.

The installed version of Google Play services is out of date. The calling activity should pass this error code to GoogleApiAvailability.getErrorDialog(Activity, int, int) to get a localized error dialog that will resolve the error when shown.

The client attempted to connect to the service but the user is not signed in. The client may choose to continue without using the API. Alternately, if Status.hasResolution() returns true the client may call Status.startResolutionForResult(Activity, int) to prompt the user to sign in. After the sign in activity returns with Activity.RESULT_OK further attempts should succeed.

The operation was successful.

The operation was successful, but was used the device's cache. If this is a write, the data will be written when the device is online; errors will be written to the logs. If this is a read, the data was read from a device cache and may be stale.

Timed out while awaiting the result.