The following enumerations are used in IMIconnect iOS SDK.
This enumeration exposes enumeration data with type of logs that will be logged.
|No log will be displayed/recorded.
|A large amount of logs will be logged that can help to debug.
|Logs will be kept at a minimum level.
This enumeration represents the target on which the logs will be displayed or recorded.
|Logs will be displayed in the console.
|Logs will be recorded in a file.
This enumeration describes different connection status between the SDK and the Real Time Messaging server.
|No connection attempt has been made.
|The SDK is attempting to establish a connection with Real Time Messaging server.
|The SDK is connected and allows you to publish and receive messages.
|The connection is refused by the Real Time Messaging server.
|The SDK is disconnected from the Real Time Messaging server.
|A connection error has occurred while connecting to Real Time Messaging server.
This enumeration describes different error codes of the SDK.
|Returned when trying to access a feature without initializing the SDK.
|Returned when trying to initialize the SDK when it is already initialized.
|Returned when trying to access a feature without registering a user.
|Returned when trying to access a feature that is not supported by the app.
|Returned when a required parameter is not passed or an invalid value has been passed to a method.
|Returned when trying to communicate with the RTM server without establishing a connection.
|Returned when a registration is failed.
|Returned when a response from the server is invalid.
|ICErrorCodeTokenInvalid = 38
|The token is not in the expected format.
|ICErrorCodeTokenUnauthorized = 39
|The token does not provide authorization to access the requested resource.
|ICErrorCodeTokenExpired = 40
|The token has expired.
|ICErrorCodeTokenRequired = 41
|The token is required.
This enumeration describes the supported message channels.
|The incoming message comes from Push notification channel.
|The incoming message comes from Real Time Messaging channel.
This enumeration describes the message types.
|A standard non-interactive message.
|A message that contains pre-built out-of-the-box interactive elements. This type of message typically causes actions to occur on the device in response to notification buttons.
|Message data is alert from connect platform.
|Message data is a DeliveryReceipt, TransactionId is available and can be used to match the receipt to the original message.
|Standard Push or RTM.
|Represents the notification part of an RTM.
|Message data is a ReadReceipt, only TransactionId is available and can be used to match the receipt to the original message.
|Message is a republish of a MO, all data from the original message is available.
|Message data is a TypingStart from connect platform end.
|Message data is a TypingStop from connect platform end.
Message field could be null for below message types:
|The thread is a conversation, the users can send messages on this thread.
|The thread is an announcement thread, the users can only receive messages on this thread.
|Synchronization should synchronize all available data.
|Synchronization should occur based on policy limits.
|Synchronization should be disabled.
|None is the default message status.
|Message sent successfully to connect platform.
|Message delivered to the user device.
|Message read by the user device.
|The thread is active. The user can receive (and send if the thread type is conversation) messages on this thread
|The thread is closed. The user cannot receive (and send if the thread type is conversation) any messages on this thread
Updated about 1 year ago