AppWarp::ResultCode::success = 0;
  AppWarp::ResultCode::auth_error = 1;
  AppWarp::ResultCode::resource_not_found = 2;
  AppWarp::ResultCode::resource_moved = 3;
  AppWarp::ResultCode::bad_request = 4;
  AppWarp::ResultCode::connection_error = 5;
  AppWarp::ResultCode::unknown_error = 6;
  AppWarp::ResultCode::size_error = 7;
  AppWarp::ResultCode::api_not_found = 8;
  AppWarp::ResultCode::success_recovered = 9,
  AppWarp::ResultCode::connection_error_recoverable = 10	

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.

API NOT FOUND

This occurs if invalid API Key was used during initialization

SUCCESS RECOVERED

This occurs when you have successfully recovered a connection error

CONNECTION ERROR RECOVERABLE

This occurs if there is a connection error but it can be recovered using recoverConnection() function.