iOS Client Event Result Codes
static const Byte SUCCESS = 0 ; static const Byte AUTH_ERROR = 1 ; static const Byte RESOURCE_NOT_FOUND = 2 ; static const Byte RESOURCE_MOVED = 3 ; static const Byte BAD_REQUEST = 4 ; static const Byte CONNECTION_ERR = 5 ; static const Byte UNKNOWN_ERROR = 6 ; static const Byte RESULT_SIZE_ERROR = 7; static const Byte SUCCESS_RECOVERED = 8; static const Byte CONNECTION_ERROR_RECOVERABLE = 9;
SUCCESS
The request was successfully received and processed by the server.
AUTH_ERROR
The session id sent in the request was incorrect. This can happen if the client connects without initializing with the correct keys.
RESOURCE_NOT_FOUND
The resource for which the request was intended is not known to the server. For example a bad room id is given to a joinRoom request.
RESOURCE_MOVED
The resource for which the request was intended to has moved to a state where it can’t process the request. For example, if a client sends a chat or updatePeers message and the connected user is not present in any room.
UNKNOWN_ERROR
This is an unexpected error. Retrying the request is recommended if this happens.
BAD_REQUEST
This occurs if the parameters passed to the request are invalid. For example if null or empty string is passed in the roomId parameter of a joinRoom request.
CONNECTION_ERR
This occurs if the underlying TCP connection with AppWarp cloud service got broken. The client will need to reconnect to the service and retry the operation.
SUCCESS_RECOVERED
This indicates that the user connection has been successfully restored.
CONNECTION_ERROR_RECOVERABLE
This occurs if the underlying TCP connection with AppWarp cloud service got broken. But also indicates that it is possible to recover the connection if the application requires by calling the RecoverConnection API.