Companion
Error codes and reasons used as values of errorCode and reason.
Properties
Detaching (cancelling) an in-progress attachment upload failed. Android-only.
An attachment failed to download.
Opening a downloaded attachment in an external application failed (for example, no installed app can handle the file's MIME type). Android-only.
Refreshing an expired attachment URL failed. Android-only; iOS exposes the same condition via attachment-fetcher events.
An attachment failed to upload to the Messenger service.
An attachment failed validation (for example, file too large or unsupported type).
Logout from an authenticated session failed.
The session requires (re-)authorization. Refresh the OpenID token and call ChatController.reauthorizeImplicitFlow(idToken, nonce) to resume the session.
The clear-conversation feature is disabled in the Messenger deployment configuration, so com.genesys.cloud.ui.structure.controller.ChatController.clearConversation cannot proceed. Enable the feature in Genesys Cloud admin to use it.
The clear-conversation feature is enabled but the operation failed (for example, because of a transient network or server error). The conversation history is not cleared and the chat session remains active.
The server returned an HTTP 4xx response. Android-only; iOS surfaces client-side HTTP failures via GeneralError or ConfigurationsError.
The client is not authenticated but attempted an operation requiring authentication.
The Messenger deployment configuration could not be loaded. The chat cannot be created until the configuration becomes available.
The SDK could not establish or maintain the WebSocket connection to the Messenger service. Typically delivered when the device is offline or the connection is interrupted. Use com.genesys.cloud.ui.structure.controller.ChatController.reconnectChat to attempt recovery.
A network-layer exception (for example, java.io.IOException or java.net.SocketTimeoutException) prevented the SDK from reaching the server. Android-only.
The conversation could not be auto-started.
A new conversation could not be created.
Custom attributes could not be sent to the server.
Failed to load chat data (for example, message history).
The server returned an HTTP 403 (Forbidden) response. Android-only.
A general error that does not fit other categories.
A downloaded image exceeded the maximum allowed size and was rejected.
The Messenger deployment is in a disabled state and cannot accept connections.
The server returned an HTTP 404 (Not Found) response. Android-only.
The push token registration request targeted a different deployment than the one the token was previously registered against. The host application should disable push for the previous deployment before registering for the new one.
The server returned an HTTP 5xx response. Android-only; iOS surfaces server failures via GeneralError or ConnectionError.
The Messenger service is temporarily unavailable (for example, during an outage or maintenance window). Retry the operation later.
The chat session ended because the session expired (for example, idle timeout).
A message failed to send.
The request timed out (HTTP 504, or a socket/read timeout). Android-only; iOS surfaces timeouts via ConnectionError.