-11029: The custom type length exceeds the limit.
-11023: Encrypt message failed.
-11014: The topic count exceeds the limit.
-11003: The topic member count exceeds the limit.
-11006: The channel is in error state.
-11004: The channel is reused in RTC.
-11005: The channel instance count exceeds the limit.
-11030: The custom type is invalid.
-11009: The message is invalid.
-11018: The topic meta is invalid.
-11008: The topic name is invalid.
-11011: The user list is invalid.
-11034: The channel join operation is canceled.
-11007: The channel join failed.
-11015: Join topic failed.
-11028: Leave channel failed.
-11037: The message delivered successfully but store in history failed.
-11010: The message length exceeds the limit.
-11012: The stream channel is not available.
-11027: The connection state is invalid.
-11001 ~ -12000 : reserved for channel error. -11001: The user has not joined the channel.
-11002: The user has not subscribed the channel.
-11032: The channel presence is not ready.
-11024: Publish message failed.
-11026: Publish message timeout.
-11025: Publish message too frequent.
-11033: The destination user of publish message is offline.
-11036: The message receiver is offline and the message store in history failed.
-11035: The message receiver is offline but the message store in history succeeded.
-11021: Subscribe channel failed.
-11019: Subscribe channel timeout.
-11020: Subscribe channel too frequent.
-11017: The topic does not exist.
-11016: The topic is not joined.
-11013: The topic is not subscribed.
-11022: Unsubscribe channel failed.
-11031: unsupported message type (in MacOS/iOS platform，message only support NSString and NSData)
-10017: Already call same request.
-15002: The timestamp is invalid.
-15005: The history service not available.
-15001 ~ -16000 : reserved for history error. -15001: The history operation failed.
-15004: The history operation is not permitted.
-15003: The history operation timeout.
-10016: Try to login or join with inconsistent app ID.
-10007: The service is not initialized.
-10018: Already call destroy or release, this instance is forbidden to call any api, please create new instance.
-10003: The app ID is invalid.
-10008: The channel name is invalid.
-10019: The channel type is invalid.
-10020: The encryption parameter is invalid.
-10004: The event handler is invalid.
-10014: The parameter is invalid.
-10024: The private config is invalid, set private config should both set serviceType and accessPointHosts.
-10005: The token is invalid.
-10006: The user ID is invalid.
-14007: Acquire lock failed.
-14004: The lock already exists.
-14005: The lock name is invalid.
-14006: The lock is not acquired.
-14009: The lock service is not available.
-14008: The lock is not exist.
-14001 ~ -15000 : reserved for lock error. -14001: The lock operation failed.
-14003: The lock operation is performing.
-14002: The lock operation timeout.
-10013: The login is aborted due to unrecoverable error.
-10023: This login operation stopped by a new login operation or logout operation.
-10010: There is no server resources now.
-10015: The login is not authorized. Happens user login the RTM system without granted from console.
-10012: The login is rejected by server.
-10011: The login timeout.
-10025: Perform operation failed due to RTM service is not connected.
-10001 ~ -11000 : reserved for generic error. -10001: The SDK is not initialized.
-10002: The user didn't login the RTM system.
0: No error occurs.
-10021: The operation is too frequent.
-13004: The cached presence state count exceeds the limit.
-13003: The argument in presence operation is invalid.
-13006: The state key is invalid.
-13007: The state value is invalid.
-13001 ~ -14000 : reserved for presence error. -13001: The user is not connected.
-13002: The presence is not writable.
-13013: The presence operation failed.
-13012: The presence operation timeout.
-13005: The state count exceeds the limit.
-13010: The state key already exists.
-13008: The state key length exceeds the limit.
-13009: The state value length exceeds the limit.
-13011: The user is not exist.
-10026: Renew token timeout.
-10022: The service is not configured in private config mode.
-12013: The metadata key already exists.
-12004: The argument in storage operation is invalid.
-12009: The metadata key is invalid.
-12007: The lock name in storage operation is invalid.
-12016: The metadata item is invalid.
-12003: The metadata item is invalid.
-12005: The revision in storage operation is invalid.
-12010: The metadata value is invalid.
-12011: The metadata key length exceeds the limit.
-12008: The lock in storage operation is not acquired.
-12002: The metadata item count exceeds the limit.
-12006: The metadata length exceeds the limit.
-12019: The storage service not available.
-12015: The storage operation performed without subscribing.
-12001 ~ -13000 : reserved for storage error. -12001: The storage operation failed.
-12018: The storage operation timeout.
-12014: The revision in storage operation is outdated or the key does not exist.
-12017: The user count exceeds the limit when try to subscribe.
-12012: The metadata value length exceeds the limit.
-10009: The token has expired.
The error codes of rtm client.