Corona Client Event Result Codes
["SUCCESS"] = 0, ["AUTH_ERROR"] = 1, ["RESOURCE_NOT_FOUND"] = 2, ["RESOURCE_MOVED"] = 3, ["BAD_REQUEST"] = 4, ["CONNECTION_ERROR"] = 5, ["UNKNOWN_ERROR"] = 6, ["RESULT_SIZE_ERROR"] = 7, ["SUCCESS_RECOVERED"] = 8, ["CONNECTION_ERROR_RECOVERABLE"] = 9, ["USER_PAUSED_ERROR"]=10
The request was successfully received and processed by the server.
The session id sent in the request was incorrect. This can happen if the client connects without initializing with the correct keys.
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.
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.
This is an unexpected error. Retrying the request is recommended if this happens.
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.
This occurs if the underlying TCP connection with AppWarp cloud service is broken. The client will need to reconnect to the service and retry the operation.
This occurs if the size of the message is too big. The client will need to reconnect to the service and retry the operation.
This occurs only when Connection Resiliency is used and the connection gets recovered within the specified time.If not, you will get a CONNECTION_ERR.
This occurs only when Connection Resiliency is used and the connection was broken due to some reason.If not, you will get a CONNECTION_ERR.
This occurs when trying to connect to a user who has been paused for that particular time.