android-client-result

*We assure you that we do not spam. You may receive occasional emails from us.
 You can always unsubscribe.
Android

Android Client Event Result Codes

  public static final byte SUCCESS = 0;    
  public static final byte AUTH_ERROR = 1;    
  public static final byte RESOURCE_NOT_FOUND = 2;    
  public static final byte RESOURCE_MOVED = 3;     
  public static final byte BAD_REQUEST = 4;
  public static final byte CONNECTION_ERR = 5;
  public static final byte UNKNOWN_ERROR = 6;
  public static final byte RESULT_SIZE_ERROR = 7;
  public static final byte SUCCESS_RECOVERED = 8;
  public static final 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 occurs if when successfully recover a session.

CONNECTION_ERROR_RECOVERABLE

This occurs if the underlying TCP connection with AppWarp cloud service got broken but same session can be recovered. The client will need call RecoverConnection() to resume same session.