ConnectionsStatusCodes

Error code upon trying to connect to the Nearby Connections API via Google Play Services. This error indicates that Nearby Connections is already in use by some app, and thus is currently unavailable to the caller. Delivered to GoogleApiClient.OnConnectionFailedListener.

The Manifest.permission.ACCESS_COARSE_LOCATION permission is required.

The Manifest.permission.ACCESS_FINE_LOCATION permission is required.

The Manifest.permission.ACCESS_WIFI_STATE permission is required.

The Manifest.permission.BLUETOOTH permission is required.

The Manifest.permission.BLUETOOTH_ADMIN permission is required.

The Manifest.permission.BLUETOOTH_ADVERTISE permission is required.

The Manifest.permission.BLUETOOTH_CONNECT permission is required.

The Manifest.permission.BLUETOOTH_SCAN permission is required.

The Manifest.permission.CHANGE_WIFI_STATE permission is required.

The Manifest.permission.NEARBY_WIFI_DEVICES permission is required.

The Manifest.permission.RECORD_AUDIO permission is required.

Location must be turned on (needed for Wifi scans starting from Android M), preferably using /android/reference/com/google/android/gms/location/SettingsApi.

The app is already advertising; call stopAdvertising() before trying to advertise again.

The app is already connected to the specified endpoint. Multiple connections to a remote endpoint cannot be maintained simultaneously.

The app is already discovering the specified application ID; call stopDiscovery() before trying to advertise again.

The app already has active operations (advertising, discovering, or connected to other devices) with another Strategy. Stop these operations on the current Strategy before trying to advertise or discover with a new Strategy.

There was an error trying to use the phone's Bluetooth capabilities.

The remote endpoint rejected the connection request.

An attempt to read from/write to a connected remote endpoint failed. If this occurs repeatedly, consider invoking Connections.disconnectFromEndpoint(GoogleApiClient, String).

An attempt to interact with a remote endpoint failed because it's unknown to us -- it's either an endpoint that was never discovered, or an endpoint that never connected to us (both of which are indicative of bad input from the client app).

The operation failed, without any more information.

The device is not connected to a network (over Wifi or Ethernet). Prompt the user to connect their device when this status code is returned.

The remote endpoint is not connected; messages cannot be sent to it.

The operation was successful.

The app called an API method out of order (i.e. another method is expected to be called first).

An attempt to read/write data for a Payload of type Payload.Type.FILE or Payload.Type.STREAM failed.

There was an error trying to use the phone's Bluetooth/WiFi/NFC capabilities.

Returns an untranslated debug (not user-friendly!) string based on the current status code.