Status codes

SDK status codes

-3

The cancel or pause operation failed because the target media transfer was not found.

Verify the message ID or transfer handle before calling cancel/pause. The file may have already finished downloading — use the download callback to confirm.

-1

An unknown error occurred.

If this error persists, contact support with your App Key, user ID, and the time the error occurred so that server-side logs can be retrieved.

0

The operation completed successfully.

405

The message was not delivered because the recipient has added you to their blocklist.

Remove the user from the blocklist via the Server API if your use case requires it.

20106

You have been muted in this direct message channel and cannot send messages.

Contact the channel owner or an administrator to lift the mute restriction.

20109

The system channel only supports `RC:SRSMsg` messages. This message type is not allowed in a system channel.

Send only RC:SRSMsg messages to system channels. Use a different channel type for other message types.

20512

The App Key's data center does not match the data center used for the cloud configuration request.

Verify that your server-side API calls and client-side SDK initialization both target the same data center region. If you use an overseas data center (Singapore, North America, Saudi Arabia), pass the correct area code during SDK initialization and use the matching regional API endpoint.

20604

Message sending rate exceeded. A maximum of 5 messages per second is allowed.

Add a delay between send calls on the client side to stay within the 5 msg/s limit.

20606

This operation is not supported. The server has disabled it (private cloud only).

This error only applies to private cloud deployments. Public cloud users can ignore it.

20607

The request rate limit was exceeded. The default limit for query operations is 50 requests per second.

Throttle your query calls to stay within 50 requests per second.

22201

The original message for the expansion operation does not exist.

Ultra group messages are stored for 7 days by default. Check sentTime to see whether the message has expired. The message may also have been manually deleted — query the channel history to confirm.

22202

The original message does not support expansion.

Set canIncludeExpansion = true when sending the message to enable expansion support.

22203

The expansion content format is invalid. Expansion content must be a valid JSON string.

Ensure the expansion content is a JSON string, for example {"key":"value"}.

22204

You do not have permission to perform this expansion operation.

Verify that the conversation type parameter is correct. Ultra group expansion requires ConversationType_ULTRAGROUP (value 10).

22406

The current user is not a member of this group.

Confirm group membership via the console or the Server API. If the user is listed as a member but the error persists, contact support with your App Key, user ID, group ID, and the time the error occurred.

22408

The user has been muted in this group channel.

Lift the mute restriction using the group or ultra group mute Server API.

23406

The current user is not in this open channel.

Open channels are automatically destroyed when empty and members are automatically removed when they go offline. Rejoin the open channel before attempting operations. Use the open channel status sync API to observe state changes.

23407

The open channel mute allowlist user count has exceeded the limit.

There are two quota limits that trigger this error: the per-call limit for adding users to the individual mute allowlist is 5 user IDs, and the per-call limit for adding users to the all-muted allowlist is 20 user IDs.

23408

The user has been muted in this open channel.

The mute may be applied at three levels: room-wide mute, global user mute, or individual user mute. Use the corresponding Server API to lift the specific mute.

23409

The user has been kicked out of and banned from this open channel. The ban duration was set when the kick was issued.

Use the unblock open channel user Server API to remove the ban.

23410

The open channel does not exist.

Open channels are automatically destroyed when they are empty and members go offline. Check whether the open channel was destroyed. You can query and create open channels via the console Server API debugger.

23411

The open channel has reached its member capacity limit.

By default, open channels have no member limit, but a limit can be configured. Confirm whether a cap has been set. Submit a support ticket to request an adjustment to the member limit.

23412

An invalid parameter was passed to the open channel API. Verify that all parameters are non-null and valid.

Check the parameter values against the API documentation. If the parameters look correct and the error persists, contact support with the API name, parameters, and the time the error occurred.

23413

An error occurred while querying open channel message history.

Contact support with your App Key, user ID, open channel ID, and the query timestamp.

23414

Chatroom message cloud storage has not been enabled for this application.

Contact support to enable the open channel cloud message storage service.

23423

The number of KV attributes in this open channel has reached the limit. The default maximum is 100 entries per open channel.

Delete unused KV entries before adding new ones. The limit of 100 entries per open channel cannot be raised.

23424

You do not have permission to modify this open channel KV attribute — it was set by another user.

To forcibly overwrite a KV attribute set by another user, use the force-set API. See the open channel KV attribute management documentation for details.

23426

The open channel custom attribute (KV) service has not been enabled.

Enable the open channel custom attribute service in the console under IM Service → Feature Configuration.

23427

The specified open channel KV attribute does not exist.

The attribute may have been deleted, or set with autoDelete = 1 (automatically deleted when the user leaves the room), or the open channel itself may have been destroyed. Query the open channel KV to confirm. If the deletion is unexpected, contact support.

23428

The batch KV set or delete operation partially failed.

Contact support with your App Key, user ID, open channel ID, and the time the error occurred.

23429

The batch KV operation exceeded the limit. A maximum of 10 entries can be set or deleted per call.

Split your request into batches of at most 10 entries. This limit cannot be changed.

24001

No device ID is registered, which means the user is not logged in.

Contact support with your App Key, user ID, and the time the error occurred.

24002

The device ID already exists.

Contact support with your App Key, user ID, and the time the error occurred.

24009

No matching user or token was found.

Confirm that the user has been registered and that the token is valid. You can verify the token in the console under Operations → User Management. Re-obtain a token via the console Server API debugger and test the connection again.

24015

An internal server error occurred.

Contact support with your App Key, user ID, and the time the error occurred.

24360

You do not have permission to set this user profile attribute from the client SDK.

The uniqueId field cannot be set from the client. Use the Server API to set it if needed. Remove uniqueId from the updateMyUserProfile call.

24361

The specified key does not exist in the user profile basic attribute list.

Check the valid key names in the user profile documentation. Only recognized keys can be updated.

24362

The specified key does not exist in the user profile extended attribute list.

Extended attribute keys must be configured in the console under IM Service → User Information Hosting → Custom Attributes before they can be set.

24363

The number of custom extended user profile attributes has exceeded the maximum of 20.

Delete unused extended attributes to stay within the 20-attribute limit.

24364

A user profile attribute value exceeds the maximum length of 256 characters.

Shorten the value to 256 characters or fewer.

24365

The batch user profile query exceeded the count limit.

The client SDK can query up to 20 users per call. The Server API supports up to 100 users per call.

24366

No user profile was found for this user ID in the hosting service.

Set the user's profile via the user profile API before querying it.

24367

The value for this user profile attribute must be a number.

Gender, role, and level fields require integer values. Check the user profile API documentation for the expected type.

24368

The user profile attribute value is outside the allowed range.

Ensure the value is within the permitted range defined in the user profile documentation.

24369

The user information hosting service is not enabled.

The user information hosting service is enabled by default. Contact support if you continue to see this error.

24401

The ultra group feature has not been enabled for this application.

Ultra group is included in the premium plan and is enabled by default. Contact support if this error persists.

24402

An ultra group service error occurred.

Contact support with your App Key, user ID, and the time the error occurred.

24403

An invalid parameter was passed to an ultra group API call.

Check all parameters against the ultra group API documentation.

24404

An unknown ultra group error occurred.

Contact support with your App Key, user ID, and the time the error occurred.

24406

The current user is not a member of this ultra group.

Confirm membership via the console Server API debugger and join the group if needed.

24408

The user has been muted in this ultra group.

Lift the mute using the ultra group mute management Server API.

24410

The specified ultra group does not exist.

Create the ultra group via the console Server API debugger.

24412

The user has reached the maximum number of ultra groups they can join. The limit is 100.

The user must leave an existing ultra group before joining a new one.

24413

The maximum number of channels per ultra group has been reached. The limit is 50.

Delete an existing channel before creating a new one. The 50-channel limit per group cannot be raised.

24414

The specified ultra group channel ID does not exist.

Create the channel via the console or the create-channel Server API before referencing it.

24415

The message sending rate for this ultra group channel has been exceeded. The default limit is 20 messages per second per channel.

Spread out sends over time or implement client-side queuing to stay within the 20 msg/s channel limit.

24416

The user is not a member of this private ultra group channel.

Add the user to the private channel using the add-to-private-channel Server API.

25101

The recall request contained an invalid parameter.

Contact support with your App Key, user ID, and the time the error occurred.

25102

Cloud message storage for direct and group channels is not enabled.

Contact support to enable the cloud message storage service.

25104

An unknown server error occurred.

Contact support with your App Key, user ID, and the time the error occurred.

25107

Recalling another user's message is not allowed because the server-side "only recall own messages" setting is enabled.

By default the SDK can recall any message. When the "only recall own messages" switch is enabled on the server, you can only recall messages you sent yourself. Contact support to change this server-side setting.

25402

The hosting (entrust) service encountered an internal error.

Contact support with your App Key, user ID, and the time the error occurred.

25403

An invalid parameter was passed to a hosting service API call.

Verify all parameters against the user information hosting API documentation. Contact support if the issue persists.

25404

This operation is not permitted. Only the group owner can modify group permission settings.

Confirm the group owner ID via the query group profiles Server API before attempting owner-only operations.

25405

You do not have permission to perform this operation.

Check the group's permissions field via the query group profiles Server API.

25406

A parameter value exceeds the maximum allowed length.

Check each parameter value against the API documentation. If parameters are within limits and the error persists, contact support with the API name and parameters.

25407

A parameter contains an illegal character.

Verify that the built-in group attribute keys are used correctly.

25408

A parameter value must be a number.

Check the API documentation for numeric parameter requirements. Contact support if parameters are correct and the error persists.

25409

A group with this ID already exists.

The group has already been created. You can use the existing group directly.

25410

The specified group ID does not exist.

Create the group first using the create group Server API.

25411

The group member count limit has been exceeded.

A single invite call can add at most 30 members. The total group membership cap is 3,000.

25412

One or more of the specified users are already members of this group.

The user is already a member — no further invite or join action is needed.

25413

This attribute cannot be modified from the client SDK.

Check the group custom attributes configuration in the console under Information Hosting Service → Group Custom Attributes to see which fields are client-editable.

25414

Joining this group is not allowed because the group has restricted membership.

Check the group's permissions field via the query group profiles Server API to understand the join policy.

25415

The specified extended attribute key does not exist for this group.

Add the key in the console under Information Hosting Service → Group Custom Attributes before referencing it.

25416

The query rate limit was exceeded. The default limit for group hosting query APIs is 5 requests per second.

Throttle your query calls to stay within the 5 requests/second limit.

25417

The group owner cannot be kicked, cannot leave the group, or cannot be assigned as an admin.

Transfer ownership to another member first if you need to remove the current owner from the group.

25418

The specified user is not a member of this group.

Confirm membership using the query specific group member Server API.

25419

The admin or follower count limit has been exceeded. Maximum admins: 20. Maximum followers: 200. Maximum members: 3,000.

Remove existing admins or followers before adding new ones.

25420

The specified user is not an admin of this group.

Assign the user as a group admin first using the add group manager Server API.

25421

No invite request was found for this group ID and user ID combination.

Invite records expire after 7 days. Check whether the invitation is still valid and re-invite if necessary.

25422

The batch group query count exceeded the limit.

A single query can fetch at most 20 groups, or up to 100 group members.

25423

The group name cannot be empty.

Provide a non-empty group name when creating or updating a group.

25424

Joining this group requires approval from an administrator.

The join request has been submitted. Wait for an admin to approve it. Check the group's permissions field via the query group profiles Server API.

25425

The group owner cannot be assigned as an admin.

The group owner already has full permissions. Admin role assignment applies only to regular members.

25426

You do not have permission to invite users to this group.

Check the group's permissions field and the inviting user's role via the query group profiles and query group member Server APIs.

25427

The invited user must accept the invitation before joining the group.

The invitation has been sent. Wait for the invitee to accept. Check the group's permissions field to understand the invite policy.

25428

This group application has already been handled by another administrator.

No action needed — another admin has already processed the request.

25429

This legacy group does not support the managed group API. It must be imported first.

Import the legacy group using the group managed import API before calling managed group operations.

25430

The group ID is invalid because it contains special characters.

Use only letters and numbers in the group ID.

25432

The page token could not be parsed.

Use the pageToken value returned by the previous paginated response. Do not construct or modify the token manually.

25460

The two users are already friends. The operation is not needed.

Confirm the friendship status using the get friend list Server API before sending a friend request.

25461

A friend request has been sent and is waiting for the other user to accept.

Friend add permission can be configured at the App Key level (via IM Service → Feature Configuration → Friend Settings) or at the user level (via the set friend add permission client API).

25462

Cannot add this user as a friend because you are on their blocklist.

The target user must remove you from their blocklist before you can send a friend request.

25463

Cannot add this user as a friend because you are not on their allowlist.

The target user has enabled allowlist-only friend requests. Ask them to add you to their allowlist first.

25464

Cannot add this user as a friend because they are on your blocklist.

Remove the target user from your blocklist before sending a friend request.

25465

Cannot add this user as a friend because they are not on your allowlist.

Add the target user to your allowlist before sending a friend request.

25466

The friend request does not exist or has expired.

Friend requests expire after 7 days. Verify the user ID and re-send the request if needed.

25467

Your friend list has reached the maximum of 3,000 friends.

Remove existing friends to free up capacity before adding new ones.

25468

The target user's friend list has reached the maximum of 3,000 friends.

The target user must remove some friends before they can accept new friend requests.

25469

The two users are not friends. This operation requires a friend relationship.

Check the relationship status using the check friend Server API.

25470

The number of custom friend attributes exceeds the maximum of 10.

Remove unused custom friend attributes to stay within the 10-attribute limit.

25471

The target user has set their account to not accept friend requests.

Check the target user's friend add permission level using the query friend add level Server API.

25472

The friend does not exist. The user has not been registered.

Register the user via the Server API before attempting friend operations.

25473

You cannot add yourself as a friend.

Ensure the userId and targetId parameters are different. The client-side userId must differ from the currently connected user's ID.

26001

The user-level push service request contains an invalid parameter.

Contact support with your App Key, user ID, the specific API called, and its parameters.

26002

The client version number is too low and needs to sync its version. Submit a support ticket to enable the user-level configuration switch.

Contact support to enable the user-level configuration switch for your application.

26004

The number of channel tags for this user has reached the maximum of 20.

Delete unused tags before adding new ones. The 20-tag limit cannot be raised.

26005

Read receipt v4 has not been enabled for this application.

Contact support to enable read receipt v4.

26007

The message ID order is incorrect. `startMsgId` must not have an earlier timestamp than `endMsgId`.

Ensure startMsgId represents a time after endMsgId in your query parameters.

26009

The `messageUid` parameter is invalid.

Check the messageUid value you are passing to the API.

26010

An invalid parameter was passed to the server.

Contact support with your App Key, user ID, the specific API called, and its parameters.

26020

The user online status subscription feature has not been enabled.

Contact support to enable the client-side user online status subscription feature.

26021

A user can be subscribed to by at most 5,000 other users.

The user has too many subscribers. The 5,000 subscriber limit cannot be changed.

26022

You have reached the maximum number of users you can subscribe to. The limit is 5,000.

Unsubscribe from some users before adding new subscriptions.

26106

The uploaded file exceeds the maximum allowed size of 100 MB.

Compress or split the file so that it is under 100 MB before uploading.

26107

The `size` parameter was not provided, but the file size limit is enforced.

Pass the file size (in KB) using the size parameter when uploading files.

30001

The current connection has been released.

Monitor connection state using the connection status delegate. Retry or switch to a more stable network. Contact support if the issue persists.

30002

The connection is not available. Call `connect` and wait for the connection success callback before invoking other APIs.

Monitor connection state using the connection status delegate and wait for ConnectionStatus_Connected before calling other APIs.

30003

The server did not acknowledge the message within the timeout window.

Retry after a short delay or switch to a more stable network. Contact support if the issue persists.

30005

The connection navigation address request timed out.

Retry after a short delay or switch to a more stable network. Contact support if the issue persists.

30006

The HTTP response during navigation failed.

Retry after a short delay or switch to a more stable network. Contact support if the issue persists.

30007

The navigation response contained unexpected data.

Retry after a short delay or switch to a more stable network. Contact support if the issue persists.

30009

No valid IP address was found after parsing the navigation data.

Contact support with your App Key, user ID, and the time the error occurred.

30015

Connection attempts are too frequent.

Not currently used on iOS. No action required.

30016

The message size exceeds the 128 KB limit (measured after JSON serialization).

Common cause: the thumbnail for a media message is too large. Keep the base64-encoded thumbnail under 80 KB. Ensure the RCMessage.content payload stays within 128 KB.

30019

The network connection is unavailable.

Retry after a short delay or switch to a more stable network. Contact support if the issue persists.

30021

The TCP connection succeeded but the RMTP handshake failed.

Retry after a short delay or switch to a more stable network. Contact support if the issue persists.

31000

The connection acknowledgment timed out.

Retry after a short delay or switch to a more stable network. Contact support if the issue persists.

31002

The client INFO field format is invalid. The expected format is: `{PlatformType}-{DeviceInfo}-{SDKVersion}`, where DeviceInfo is `{DeviceType}|{DeviceModel}|{NetworkType}|{CarrierCode}`.

Contact support with your App Key, user ID, and the time the error occurred.

31004

The token is invalid, the App Key and token do not match, or the token has expired.

Ensure the App Key used in initWithAppKey: matches the one used to obtain the token from your server. If using an overseas data center, confirm that the correct area code is set. Check the token expiration policy in the console under App Info. Re-obtain a token via the console Server API debugger and test again.

31005

App verification is enabled, but the verification check failed.

Contact support with your App Key and bundle ID information.

31007

The bundle ID does not match the information registered in the console.

Contact support with your App Key and bundle ID information.

31008

The App Key has been blocked or deleted.

Submit a request to restore the App Key in the console under App Management.

31009

The connection was rejected because the user has been blocked.

Unblock the user using the unblock user Server API.

31010

The user was kicked offline by another session.

By default, the same user account can be simultaneously online on one device per platform type (mobile, web, desktop, mini-program). If you need multiple simultaneous sessions of the same type, refer to the multi-device online documentation.

31020

The token has expired.

Check the token expiration policy in the console under App Info. Re-obtain a fresh token via the console Server API debugger and reconnect.

31023

When the "do not kick online clients" setting is enabled, this code indicates that another session of the same platform type is already online.

See the reconnection and kick-off documentation for details on managing concurrent sessions.

31024

The total number of active connections has exceeded the concurrent connection limit configured on the server (private cloud only).

Check the concurrent connection limit for this App Key in the private cloud admin console. Changing the limit requires a new App Key.

31025

The client connected to the wrong environment, causing the connection to be rejected (for example, using a development App Key against a production environment).

Contact support with your App Key and bundle ID information.

31026

App Server joint authentication is enabled, but authentication with the App Server failed.

Contact support with your App Key and bundle ID information.

31029

The user account has been deactivated.

Check whether the user has been deactivated using the query deactivated users Server API. Reactivate the user ID if needed.

31030

The private cloud license check failed. The App Key license has expired.

Check whether the App Key and license in the private cloud admin console are expired. Contact your account manager to renew.

32001

An internal protocol error occurred during a query, upload, or download — no data was returned.

Contact support with your App Key, user ID, and the time the error occurred.

32002

An internal protocol layer error — the message data is incomplete.

Contact support with your App Key, user ID, and the time the error occurred.

32011

The server actively closed the QUIC connection (QUIC transport only).

Contact support with your App Key, user ID, and the time the error occurred.

32054

The connection was reset by the server, possibly because the carrier treated it as invalid. The SDK automatically triggers a reconnection — no app-level action is needed.

Retry or switch to a more stable network. Contact support if the issue persists.

33000

The message could not be saved to the local database when sending or inserting.

Ensure the device has sufficient storage and that connect has succeeded. Contact support if the issue persists.

33001

The SDK protocol stack has not been initialized.

Call initWithAppKey: before calling any other SDK methods.

33002

A local database error occurred.

Ensure that initWithAppKey: has been called and the connection succeeded. Contact support if the issue persists.

33003

An invalid parameter was passed to the API.

Check the parameter values against the API documentation comments.

33007

Cloud message storage for direct and group channels has not been enabled.

Contact support to enable the cloud message storage service. If it was just enabled, uninstall and reinstall the app to force the SDK to update its navigation info.

33008

Failed to insert a message into the local database.

Ensure initWithAppKey: has been called, the connection succeeded, and the device has sufficient storage. Contact support if the issue persists.

33009

The open channel has been reclaimed and is no longer active.

Confirm the open channel status via the console Server API debugger.

33100

The specified tag does not exist.

Retrieve the tag list first to confirm the tag exists. Create the tag if it is missing.

33101

A tag with this ID already exists.

Retrieve the tag list to verify the existing tags before creating a new one.

33102

The tag is not associated with this channel.

Retrieve all tags for the specific channel to confirm which tags are associated with it.

33103

The method is currently executing and cannot be called again until it completes.

Wait for the current operation to finish before calling the method again.

34001

A connection already exists. No need to connect again.

Check the current connection status before calling connect. If already connected, skip the call.

34002

The video message duration exceeds the 2-minute limit.

Trim the video to under 2 minutes before sending.

34003

The GIF message file size exceeds the 2 MB limit.

Compress the GIF to under 2 MB before sending.

34004

The open channel KV state has not finished syncing.

Add a short delay after joining the open channel before querying KV data. Call KV APIs only after the sync-complete callback fires.

34005

The connection environment is incorrect (private cloud only).

Public cloud users can ignore this error. Private cloud: using a public cloud SDK against a private cloud environment will trigger this error. Ensure you are using the correct private cloud SDK build.

34006

The connection attempt timed out.

Monitor connection state using the connection status delegate. Retry or switch to a more stable network. Contact support if the issue persists.

34007

The queried public service profile does not exist.

Verify that the public service type and ID are correct.

34008

The message does not support expansion.

Set canIncludeExpansion = true before sending the message. Expansion is supported only in direct, group, and ultra group channels.

34009

Message expansion failed.

Ensure the SDK is initialized and the connection has succeeded before calling expansion APIs.

34010

The message expansion data exceeds the size limit. Key length: max 32 characters. Value length: max 4,096 characters. Total entries: max 300. Entries per call: max 20.

Reduce the size or number of expansion key-value pairs to stay within the limits.

34011

The media message file HTTP upload failed.

Retry after a short delay or switch to a more stable network. Contact support if the issue persists.

34012

The specified channel type does not support tags. Tags are supported only for direct, group, and system channels.

Use tags only with ConversationType_PRIVATE, ConversationType_GROUP, or ConversationType_SYSTEM.

34013

The number of channels added to or removed from a tag in a single call exceeds the limit of 1,000.

Split the operation into batches of at most 1,000 channels per call.

34014

The group read receipt version is not supported by the current SDK or feature configuration.

Confirm that you are calling the correct read receipt API for your integrated SDK (IMKit vs. IMLib). For Global IM UIKit, enable the read receipt feature in your configuration.

34015

Video compression failed.

Check whether the video file path is accessible and the resource is valid. Contact support with your App Key, user ID, and the time the error occurred if the issue persists.

34016

User-level settings have not been enabled.

Contact support with your App Key, user ID, and the time the error occurred.

34017

A message interceptor returned a null message object.

Review your RCMessageInterceptor implementation and ensure none of the interceptor methods return a null message.

34018

The media file is missing or has a size of 0.

Use [[NSFileManager defaultManager] fileExistsAtPath:localPath] to verify the file exists. Use attributesOfItemAtPath:error: to check the file size.

34019

The media file format is not supported for upload.

Contact support with your App Key, user ID, and the time the error occurred.

34020

The file has expired or been cleaned up. Short videos are stored for 7 days; other files for 6 months.

Check the message sentTime to confirm whether the file retention period has passed. Contact support if the file appears to have expired prematurely.

34021

The message type has not been registered.

Custom messages must be registered before use — call registerMessageType: with your custom message class. If the error is for a built-in message type, ensure the SDK is properly initialized.

34022

This API does not support ultra group channels.

Check the ConversationType parameter. If using ConversationType_ULTRAGROUP, use the ultra group-specific APIs.

34025

Message expansion failed because the channel type in the message does not match the channel types supported by this API.

Expansion supports direct, group, and ultra group channels. For direct and group channels, use the expansion APIs in RCCoreClient. For ultra group channels, use the RCChannelClient APIs with UltraGroup in the method name.

34200

The `language` parameter passed to the push language API is invalid.

The language parameter in setPushLanguageCode or setPushLanguage cannot be empty.

34201

The channel type passed to this API is not supported.

Check the parameter documentation to confirm which channel types this API supports.

34202

The timestamp parameter is invalid.

Verify the timestamp type and value against the API documentation.

34203

The message UID (server-assigned unique message ID) parameter is invalid.

Verify the messageUid type and value against the API documentation.

34204

The `messageId` parameter is invalid, or no message with this ID was found.

Verify the messageId type and value against the API documentation.

34205

The `Message` or `MessageContent` parameter is invalid.

Verify the message and content object types against the API documentation.

34206

The `messageList` parameter is invalid.

Verify the message list type and contents against the API documentation.

34207

The `mediaType` parameter is invalid.

Verify the mediaType value against the API documentation.

34208

The `requestUrl` parameter passed to the media download API is invalid or empty.

Ensure the mediaUrl parameter is non-null and a valid URL string.

34209

The `ConversationType` parameter is invalid.

Verify the value is a valid RCConversationType enum member.

34210

The `targetId` parameter is invalid.

Ensure targetId is a non-empty NSString with a length between 1 and 64 characters.

34211

The `channelId` parameter passed to a channel-related API is invalid.

Verify the channelId type and value against the API documentation.

34212

The `tagId` parameter is invalid.

Ensure tagId is a non-empty NSString with a length between 1 and 10 characters.

34213

The `tagName` parameter is invalid.

Ensure tagName is a non-empty NSString with a length between 1 and 15 characters.

34214

The `userId` parameter is invalid.

Ensure userId is a non-empty NSString.

34215

The `userIdList` parameter is invalid.

Verify the user ID list type and contents against the API documentation.

34216

The `UserOnlineStatus` parameter is invalid.

The custom online status value (customerStatus) must be an integer between 1 and 255.

34217

The `downloadMediaFileName` parameter is invalid.

Ensure the fileName parameter is non-null and non-empty.

34218

The `duration` parameter passed to `setOfflineMessageDuration` is invalid.

The duration value must be an integer between 0 and 8.

34219

The `count` field in `HistoryMessageOption` is invalid.

Ensure the count value in HistoryMessageOption is greater than 0.

34220

The `MessageExpansion` parameter is invalid.

Verify the MessageExpansion type and value against the API documentation.

34221

The `keyArray` parameter for the ultra group message expansion API is invalid.

Ensure the keyArray is a non-null, non-empty array.

34222

An invalid VoIP device token was detected by `uploadVoIPDeviceToken`.

Contact support with your App Key, user ID, and the time the error occurred.

34223

The `message.content` passed to `sendMediaMessage` is not a media message content object.

Ensure message.content is an instance of RCMediaMessageContent before calling sendMediaMessage.

34224

The time parameter is invalid.

Ensure the time parameter is a non-null, non-empty string.

34225

The `RCConversationIdentifier` parameter is invalid.

Ensure the RCConversationIdentifier object is non-null and has a matching conversation type.

34226

The `getBlockPush` API call failed.

Verify that the targetId value is between 1 and 255, and that the SDK is initialized and connected.

34227

A database query call failed.

Contact support with your App Key and the time the error occurred.

34228

The `PushNotificationLevel` parameter is invalid.

Verify the PushNotificationLevel value against the API documentation.

34231

The ultra group channel type is invalid.

Ensure the value is a valid RCUltraGroupChannelType enum member.

34232

The `count` parameter is invalid.

Verify the count type and range against the API documentation.

34233

The `sendTime` parameter is invalid.

Ensure sendTime is a valid timestamp value greater than or equal to 0.

34235

The `mediaUrl` parameter is empty.

Ensure the mediaUrl parameter is non-null and non-empty.

34236

The `uniqueId` parameter is invalid.

Ensure the uniqueId parameter is non-null and non-empty.

34238

The proxy configuration is invalid. The `RongIMProxy` object is null or malformed.

Verify the proxy configuration object against the API documentation.

34239

The proxy test host passed to `testProxy` is invalid.

Verify the test host value against the API documentation.

34240

The `testProxy` call could not reach the specified proxy test host.

Verify the proxy host and port are reachable. Contact support if the issue persists.

34241

The message type passed to `recallUltraGroupMessage` is not supported for recall.

Verify that the message object name is a supported type for ultra group message recall.

34243

The `message` parameter passed to the API is null.

Ensure the message object, message.targetId, and message.content are all non-null before calling the API.

34245

The configured proxy address is not reachable.

Contact support with your App Key, user ID, and the time the error occurred.

34251

The file could not be saved.

Check whether the device storage is full. Contact support if the issue persists.

34252

The file does not exist.

Contact support with your App Key, user ID, and the time the error occurred.

34253

The file size is invalid.

Contact support with your App Key, user ID, and the time the error occurred.

34254

The download URL is invalid.

Contact support with your App Key, user ID, and the time the error occurred.

34255

The file slice index is invalid (multipart upload error).

Contact support with your App Key, user ID, and the time the error occurred.

34256

The upload session ID is invalid (multipart upload error).

Contact support with your App Key, user ID, and the time the error occurred.

34257

The App Key is invalid.

Ensure initWithAppKey: is called before connecting, and that the App Key passed is correct and active.

34259

The `rtcRoomId` parameter is invalid.

Ensure rtcRoomId is a non-null, non-empty NSString.

34260

The `key` parameter is invalid.

Verify the key type and constraints against the API documentation.

34261

The `keys` parameter is invalid.

Verify the keys type and constraints against the API documentation.

34262

The `value` parameter is invalid.

Ensure value is an NSString with a length between 0 and 4,096 characters.

34263

The `entries` parameter is invalid.

Ensure entries is a non-null, non-empty NSString.

34264

The `notificationExtra` parameter is invalid.

Ensure notificationExtra is an NSString with a length between 0 and 2,048 characters.

34265

The `ChatRoomMemberOrder` parameter is invalid.

Use RC_ChatRoom_Member_Asc or RC_ChatRoom_Member_Desc for the sort order parameter.

34266

The `TimestampOrder` parameter is invalid.

Use a valid RCTimestampOrder enum value.

34268

The `status` parameter is invalid.

Use a valid RCUltraGroupTypingStatus enum value.

34271

The `objectName` parameter is invalid.

Ensure objectName is a non-empty NSString with a length of at most 128 characters.

34274

The `keyword` parameter is invalid.

Ensure keyword is a non-empty NSString with a length of at most 1,000 characters.

34275

The `objectName` list parameter is invalid.

Ensure the object name list is a non-null, non-empty array.

34279

The `limit` parameter is invalid.

Verify the limit type and range against the API documentation.

34280

The `MessageDirection` parameter is invalid.

Verify the MessageDirection value against the API documentation.

34281

The `SentStatus` parameter is invalid for this operation.

For direct channels, delivery time can only be retrieved for messages with status RECEIVED or READ. For group channels, use messages with status SENT, RECEIVED, or READ.

34282

The `targetId` list parameter is invalid.

Ensure the list is an NSArray with between 1 and 20 elements.

34283

The `spanMinutes` parameter is invalid.

Ensure the spanMinutes value is between 0 and 1,440.

34286

The navigation URL is empty.

Contact support with your App Key, user ID, and the time the error occurred.

34287

The `ConversationIdentifier` list parameter is invalid.

Ensure the parameter is an NSArray of RCConversationIdentifier objects with 1 to 20 elements.

34288

The `ClearMessageOption` list parameter is invalid.

Ensure the parameter is an NSArray of RCClearMessageOption objects with 1 to 20 elements.

34289

The `startMessageUID` parameter is invalid.

Ensure startMessageUID is a string with a length between 0 and 64 characters.

34290

The `endMessageUID` parameter is invalid.

Ensure endMessageUID is a string with a length between 0 and 64 characters.

34291

Read receipt v4 is not supported by this SDK component.

Read receipt v4 is only supported in the Global IM UIKit component. Contact support if you are using Global IM UIKit and this error persists.

34292

Updating read receipt v4 information is not supported.

Contact support with your App Key, user ID, and the time the error occurred.

34296

The channel type does not support directed messages. Only group and ultra group channels are supported.

Use ConversationType_GROUP or ConversationType_ULTRAGROUP when sending directed messages.

34300

A media upload or download interceptor returned a null value from its handler method.

Ensure the requestHandler return value in your RCDownloadInterceptor implementation is always non-null.

34301

The local database has not been initialized.

Ensure SDK initialization and connection have completed successfully. Contact support if the issue persists.

34303

A local database SQL execution error occurred.

Contact support with your App Key, user ID, and the time the error occurred.

34304

The queried data was not found in the local database.

Contact support with your App Key, user ID, and the time the error occurred.

34305

Network data parsing failed.

Contact support with your App Key, user ID, and the time the error occurred.

34306

The `subscribeType` parameter for the subscription API is invalid.

Use a valid RCSubscribeType enum value.

34307

The subscription duration parameter is invalid.

The expiry parameter is a duration in seconds. The minimum is 60 seconds (1 minute) and the maximum is 2,592,000 seconds (30 days).

34308

The subscriber user ID list is empty or contains invalid elements.

Ensure the parameter is an NSArray of non-empty string user IDs, each at most 64 characters, with at most 200 elements.

34309

The pagination page size parameter is invalid.

Ensure the page size is between 1 and 200.

34312

The `userProfile` parameter is invalid.

Ensure the RCUserProfile object is non-null.

34313

The `userProfileVisibility` parameter is invalid.

Use a valid RCUserProfileVisibility enum value.

34314

The `extra` parameter is invalid.

Ensure extra is an NSString value.

34318

The `GroupInfo` parameter is invalid.

Ensure the GroupInfo object is non-null.

34319

The `groupId` parameter is invalid.

Ensure groupId is a string composed of letters, digits, or the characters +, =, -, _, |, :, with a length between 1 and 64 characters.

34320

The `groupName` parameter is invalid.

Ensure groupName is a non-empty string (after trimming whitespace and newlines) with at most 64 characters.

34321

The `groupIds` parameter is invalid.

Ensure groupIds is an NSArray of string elements, each at most 64 characters.

34322

The `GroupMemberRole` parameter is invalid.

Use a valid RCGroupMemberRole enum value.

34323

The `GroupApplicationStatus` parameter is invalid.

Ensure the parameter is a non-empty NSArray of NSNumber elements that match the RCGroupApplicationStatus enum.

34324

The `GroupApplicationDirection` parameter is invalid.

Ensure the parameter is a non-empty NSArray of NSNumber elements that match the RCGroupApplicationDirection enum.

34325

The `nickname` parameter is invalid.

Ensure nickname is a non-empty string (after trimming whitespace and newlines) with at most 64 characters.

34326

The `reason` parameter is invalid.

Ensure reason is a non-empty string (after trimming whitespace and newlines) with at most 128 characters.

34327

The `remark` parameter is invalid.

Ensure remark is a non-empty string (after trimming whitespace and newlines) with at most 64 characters.

34328

The `PagingQueryOption` parameter is invalid.

Ensure the RCPagingQueryOption object is non-null.

34329

Data is still synchronizing. The requested data is not yet available.

Retry the request after a short delay once sync has completed. Contact support if this error persists.

34330

The `QueryFriendsDirectionType` parameter is invalid.

Use a valid RCQueryFriendsDirectionType enum value.

34331

The `DirectionType` parameter is invalid.

Use a valid RCDirectionType enum value.

34332

The `FriendApplicationType` parameter is invalid.

Ensure the parameter is a non-empty NSArray of NSNumber elements matching the RCFriendApplicationType enum.

34333

The `FriendApplicationStatus` parameter is invalid.

Ensure the parameter is a non-empty NSArray of NSNumber elements matching the RCFriendApplicationStatus enum.

34334

The `FriendAddPermission` parameter is invalid.

Use a valid RCFriendAddPermission enum value.

35060

An invalid parameter type was passed to the translation API. Check both the top-level parameter types and the element types within any list parameters.

Verify parameter types against the translation API documentation.

35061

The translation input list is empty or contains more than 10 elements.

Ensure the translation list is non-empty and contains at most 10 items.

35062

The channel translation strategy value is invalid.

Use a valid translation strategy type from the SDK.

35063

The source and target languages for translation are the same.

Set the source and target languages to different values.

35064

The translation mode value passed to the translation API is invalid.

Use only RCTranslateModeMechanical or RCTranslateModeIntelligent for the translation mode parameter.

35065

The text content to translate is empty or invalid.

Ensure the text to translate is non-null and non-empty.

407

The recipient only accepts messages from users on their allowlist, and the sender is not on it.

Add the sender to the recipient's allowlist using the allowlist Server API.

1004

The request failed because of an authentication error.

Check that the token and App Key are valid and have not expired. Re-authenticate if necessary.

20112

The message was rejected because the content contains sensitive words.

Remove the sensitive content and resend.

20113

The message failed content moderation review.

Review your content moderation policies in the console and adjust message content accordingly.

20114

The message can no longer be edited because the allowed modification window has passed.

Messages can only be edited within the permitted time window after sending. No action is required unless you need to adjust the time limit via the console.

20115

The message body (serialized as JSON) exceeds the maximum allowed size of 128 KB.

Reduce the message body size. For image messages, ensure the base64-encoded thumbnail does not exceed 80 KB.

20116

This message type does not support modification.

Check whether the message type supports editing before calling the modify API.

21406

The current user is not a member of this discussion.

Join the discussion before retrying the operation.

21501

The message was blocked because it contains sensitive words. The sender cannot send this message.

Check the sensitive word list in the embedded console. Remove the sensitive words or change the filter mode.

21502

The message was delivered, but sensitive words were replaced. The recipient receives the modified version.

Check the sensitive word list in the embedded console. The filter mode is set to replace. This is informational.

23437

The extra information passed when joining an open channel exceeds the maximum length (128 characters by default).

Reduce the length of the extra information. The limit can be changed via the server configuration.

24411

The community channel member count has exceeded the allowed maximum.

Contact support to adjust the member limit if needed.

25474

Robot users cannot be added as friends.

Only non-robot users can be added as friends.

25480

The user profile update failed content review.

Check your content moderation policies and revise the profile content accordingly.

26003

An internal service error occurred.

Contact support with your App Key and the time the error occurred.

26006

The server-driven unread count feature is not enabled.

Enable the feature before using server-driven unread count APIs.

26008

The timestamp parameter does not support synchronization.

Use a supported timestamp field or API flow for synchronization.

26101

The short video service is not activated.

Enable the short video service via the console.

26314

Read receipt V5 is not activated.

Contact support to enable read receipt V5.

26315

The requested read receipt method is not supported.

Check the V5 read receipt API documentation for supported methods.

26316

A parameter length exceeds the allowed limit for read receipt V5.

Reduce the parameter length to the allowed maximum.

26317

The specified channel type is not supported by read receipt V5.

Use a supported channel type for V5 read receipts.

26318

The specified query type is not supported by read receipt V5.

Use a supported query type as defined in the V5 documentation.

26320

The current user is not the sender of the message. Only the sender can perform this operation.

Ensure the current user is the original sender of the message.

26321

This message does not require a read receipt.

Skip the read receipt request for messages that don't require it.

26322

The message referenced in the read receipt request does not exist.

Verify the message UID before sending a read receipt.

28300

The voice-to-text service is not enabled.

Enable the voice-to-text service via the console or contact support.

28304

The voice-to-text conversion failed.

Verify the audio format and content, then retry.

28305

The voice-to-text service encountered an internal exception.

Contact support with your App Key and the time the error occurred.

28306

A required parameter for the voice-to-text request is missing.

Check the API documentation and provide all required parameters.

28307

The voice-to-text usage limit has been exceeded.

Contact support to increase your usage quota.

28400

The translation V2 service is not activated.

Contact support to enable translation V2.

28401

The translation V2 request failed.

Retry the request. If the issue persists, contact support.

28402

The translation V2 service encountered an internal exception.

Contact support with your App Key and the time the error occurred.

28403

Required parameters are missing from the translation V2 request.

Check the API documentation and provide all required parameters.

28404

One or more translation V2 parameters have an invalid format.

Verify the parameter formats against the API documentation.

28405

The translation V2 usage quota has been exceeded.

Contact support to increase the quota.

28406

The text submitted for translation exceeds the maximum allowed length.

Split the text into shorter segments and translate them separately.

28407

The specified language is not supported by the translation V2 service.

Use a supported language code. Refer to the translation documentation for the list of supported languages.

29002

The specified stream does not exist.

Verify the stream identifier and ensure the stream was created before reading it.

29003

The streaming session timed out because no data was received for 30 seconds.

Ensure the data source sends chunks at least once every 30 seconds.

29004

The streaming session exceeded the 30-minute total time limit.

Split long streaming sessions into multiple streams within the 30-minute limit.

29005

The streaming message content failed review and the data has been deleted.

Review content moderation policies and ensure streaming content complies with them.

29006

The stream data exceeded 128 KB and was truncated.

Reduce the size of each stream chunk to stay under 128 KB.

29007

The streaming message service encountered an internal exception.

Contact support with your App Key and the time the error occurred.

29301

The LLM service request failed.

Retry the request. If the issue persists, contact support.

29302

The LLM service returned an error response.

Check the response details and contact support if the issue persists.

29303

The LLM service did not respond within the timeout period.

Retry the request. If timeouts persist, contact support.

29310

The specified agent ID was not found.

Verify the agent ID and ensure the agent has been created and configured.

29311

The specified LLM provider is not supported.

Use a supported LLM provider. Contact support for the list of available providers.

29320

The LLM/agent service request parameter format is invalid.

Verify the parameter formats against the agent API documentation.

29321

The `channelType` parameter is invalid in the LLM/agent service request.

Check the supported channelType values in the agent API documentation.

29322

The `channelId` parameter is invalid in the LLM/agent service request.

Provide a valid, non-empty channel ID.

29323

The `targetId` parameter is invalid in the LLM/agent service request.

Provide a valid target ID.

29324

An invalid parameter was provided in the LLM or agent service request.

Check the request payload against the LLM or agent service documentation before retrying.

29325

An invalid parameter was provided in the LLM or agent service request.

Check the request payload against the LLM or agent service documentation before retrying.

29326

An invalid parameter was provided in the LLM or agent service request.

Check the request payload against the LLM or agent service documentation before retrying.

29327

An invalid parameter was provided in the LLM or agent service request.

Check the request payload against the LLM or agent service documentation before retrying.

29328

An invalid parameter was provided in the LLM or agent service request.

Check the request payload against the LLM or agent service documentation before retrying.

29329

An invalid parameter was provided in the LLM or agent service request.

Check the request payload against the LLM or agent service documentation before retrying.

29330

An invalid parameter was provided in the LLM or agent service request.

Check the request payload against the LLM or agent service documentation before retrying.

29331

An invalid parameter was provided in the LLM or agent service request.

Check the request payload against the LLM or agent service documentation before retrying.

29332

An invalid parameter was provided in the LLM or agent service request.

Check the request payload against the LLM or agent service documentation before retrying.

29399

An unknown error occurred in the LLM/agent service.

Contact support with your App Key and the time the error occurred.

30017

This message type does not support sending.

Check that the message type is a sendable type as defined in the SDK documentation.

30027

The SDK is currently closing the connection.

Wait for the disconnect flow to complete before reconnecting or calling dependent APIs.

31027

This one-time token has already been used. A one-time token can only establish a connection once.

Request a new token from the app server and use it to reconnect.

31031

An invalid parameter was provided in the agent request.

Validate the agent request payload and context fields before retrying.

31032

An invalid parameter was provided in the agent request.

Validate the agent request payload and context fields before retrying.

31033

The agent service is unavailable.

Retry later or contact support if the service remains unavailable.

31034

An invalid parameter was provided in the agent request.

Validate the agent request payload and context fields before retrying.

31035

An invalid parameter was provided in the agent request.

Validate the agent request payload and context fields before retrying.

31036

An invalid parameter was provided in the agent request.

Validate the agent request payload and context fields before retrying.

31037

An invalid parameter was provided in the agent request.

Validate the agent request payload and context fields before retrying.

31038

An invalid parameter was provided in the agent request.

Validate the agent request payload and context fields before retrying.

31039

An invalid parameter was provided in the agent request.

Validate the agent request payload and context fields before retrying.

31040

An invalid parameter was provided in the agent request.

Validate the agent request payload and context fields before retrying.

31041

An invalid parameter was provided in the agent request.

Validate the agent request payload and context fields before retrying.

31042

An invalid parameter was provided in the agent request.

Validate the agent request payload and context fields before retrying.

31043

An invalid parameter was provided in the agent request.

Validate the agent request payload and context fields before retrying.

31044

The number of context messages in the agent request exceeds the maximum limit.

Reduce the number of context messages included in the agent request.

33302

Pulling the remote conversation list failed.

Retry the conversation sync after checking the network and login state.

33401

The message has not been sent successfully yet and cannot be edited.

Wait for the message to be delivered successfully before attempting to edit it.

33402

The message modification time limit has been exceeded.

Messages can only be edited within the configured time window after sending.

34024

The ultra group channel does not exist.

Verify the channel ID before calling the ultra group API.

34028

This request does not allow redirects. Use the final resource URL instead.

Pass the actual file URL rather than a redirecting URL.

34029

This message type does not support read receipts.

Use read receipts only with supported message and conversation types.

34030

The media file download was rejected with a 403 error.

Check download permissions for the media resource.

34129

The `ConnectOption` parameter passed to `connect()` is null.

Provide a non-null ConnectOption when calling NCEngine.connect().

34234

The local file path does not exist.

Verify the file path is accessible before passing it to the API.

34237

The `MessageTag` or its `value()` is null or empty.

Ensure the MessageTag and its value are non-null and non-empty.

34242

The `conversations` parameter is null or contains null entries.

Provide a non-null list with no null entries.

34244

The `SentStatus` parameter is null or set to `SENDING`.

Provide a valid non-null SentStatus that is not SENDING.

34258

The `JoinMode` parameter is null.

Provide a valid non-null JoinMode value.

34269

The `title` parameter is null or empty.

Provide a non-null, non-empty title string.

34270

The `portrait` (avatar URL) parameter is null or empty.

Provide a valid non-null, non-empty portrait URL.

34276

The `offset` parameter is less than 0.

Provide an offset of 0 or greater.

34277

The `startTime` parameter is less than 0, or it is greater than `endTime`.

Provide a startTime that is ≥ 0 and less than endTime.

34284

The `ConversationType` list is null, empty, or exceeds the maximum of 300 entries.

Provide a non-null list of 1 to 300 channel types.

34293

The `hours` parameter is invalid.

Validate the hours value against the API requirements before retrying.

34294

Fetching message changed information is not available.

Use this API only when the message change tracking feature is available.

34295

The message changed information has already been fetched.

Do not fetch the same change information repeatedly unless new data is available.

34302

The database file is corrupted.

Contact support with your App Key, user ID, and the time the error occurred.

34315

The database upgrade failed.

Contact support with your App Key, user ID, and the time the error occurred.

34335

The `extProfile` field for friend info is invalid.

Verify the format and content of the extProfile map.

34336

The real-time conversation feature is not enabled.

Contact support to enable the real-time conversation feature.

34337

The user-triggered log upload feature is not enabled.

Contact support to enable log upload.

34338

Log uploads are being triggered too frequently. The minimum interval between uploads has not been met.

Wait for the required interval before triggering another log upload.

34339

A log upload for this time period has already been submitted.

Do not submit duplicate log uploads for the same time period.

34340

The log upload failed.

Retry the upload. If the issue persists, contact support.

34341

The `pushServer` parameter is invalid.

Provide a valid pushServer configuration.

34342

The statistics server URL is invalid.

Provide a valid statistics server URL.

34343

The `pushToken` is invalid.

Provide a valid, non-null push token.

34344

Parsing the server response data failed.

Contact support with your App Key, user ID, and the time the error occurred.

34439

The local database disk is full.

Free device storage space and retry the operation.

35024

The message type parameter is invalid.

Provide a valid message type as defined in the SDK documentation.

35025

The sort order parameter is invalid.

Provide a valid order value.

35054

Only the default channel of a community group supports pinning the last message update.

Apply last message pinning only to the default channel.

35055

Only the default ultra group channel supports pinning.

Pin messages or channels only in the default ultra group channel.

35056

The read receipt configuration for sending is incorrect.

Review the needReceipt configuration and ensure it is valid for the channel type.

35057

The voice-to-text feature is not enabled for this voice message.

Enable voice-to-text in the console before using this feature.

35058

A voice-to-text request is already in progress for this message.

Wait for the current STT request to complete before starting a new one.

35059

The message content type is not supported by the voice-to-text service.

Only send audio messages to the voice-to-text API.

35066

The message was intercepted and was not sent.

Check your interceptor logic, moderation rules, or send policy before retrying.

39001

The streaming message feature is not available.

Contact support to enable streaming messages for your account.

39002

The concurrent streaming message request limit of 3 has been reached.

Wait for one of the active streams to complete before starting a new one.

39003

The expansion key does not support modification or deletion for streaming messages.

Check the streaming message expansion key restrictions in the documentation.

39004

The streaming message was reset while data was being pulled.

Restart the pull request from the beginning.

39005

The streaming message pull request failed.

Retry the pull request. If the issue persists, contact support.

39006

Content is already being pulled for this stream. Duplicate requests are not allowed.

Wait for the current pull request to complete before making another.

39007

The streaming message content has already been fully synced locally. No need to pull again.

Skip the pull request if the stream is already synced.

APNs push status codes

The following lists error codes, causes, and recommended actions you may encounter during push testing after uploading an APNs push certificate in the console.

Error Code	Cause	Action
5, 8	Incorrect device token information.	Check whether the device is jailbroken, verify that the token passed to CommsayChat.registerDevicePushToken(_:pushMode:completionHandler:) is valid, and confirm that the provisioning profile used in Xcode matches the current environment (sandbox vs. production).
52	The user ID does not exist in the current environment.	Verify that the connection succeeded and that the App Key used in NCEngine.initialize(_:) corresponds to the correct environment. The completion handler of NCEngine.connect(params:dbOpenedHandler:completionHandler:) returns the logged-in user ID — confirm it matches the user ID used in your push test.
53	The uploaded push certificate is empty.	Check and re-upload the certificate. Verify that the Bundle ID you entered in the console matches the Bundle ID embedded in the certificate.
54, 62	The uploaded certificate or certificate password is incorrect.	Check the certificate password, re-upload the certificate, and verify that the Bundle ID you entered matches the one in the certificate.
55	The user ID is not currently logged in on an iOS device.	Check whether the connection on the iOS device succeeded and whether multiple clients are connected with the same user ID.
57	Failed to send Apple push notification.	SSL parsing error — re-upload the certificate.
2, 56	No device token is registered for this user ID.	Check whether the device is jailbroken, whether the user has granted notification permissions, whether remote notification permission has been requested via UNUserNotificationCenter, and whether CommsayChat.registerDevicePushToken(_:pushMode:completionHandler:) was called after connecting.
58	Failed to parse the original parameters.	Contact support to resolve the issue.
60	Socket error.	Internal error — resend the push notification.
61	Push notifications are blocked for this user ID.	Check whether the client has disabled push notifications. If multiple clients or apps share the same App Key, check all client code for push-blocking logic.
3, 4, 6, 7, 64	Network issue — push delivery failed.	Network error — retry.
0, 1, 10, 255, 59	Apple APNs server is temporarily unavailable.	Wait and try again later.
66	The uploaded certificate does not match the current environment (sandbox vs. production).	Check the certificate environment and re-upload the correct one.
67	The certificate password is incorrect.	Check the certificate password and re-upload, or re-enter the correct password.
68	The Bundle ID entered in the console does not match the Bundle ID in the certificate.	Verify the Bundle ID you entered against the one embedded in the certificate.
70	VoIP device token is empty.	Confirm whether a VoIP device token has been registered for this device.
73	No user information found — this user ID has never retrieved a Nexconn token.	Re-obtain the user token from your server.
74	The package name in the uploaded certificate does not match the configured package name.	Verify that the package name (Bundle ID) in the uploaded certificate matches the configured package name in the console.
75	The uploaded certificate contains a wildcard Bundle ID.	Per Apple requirements, apps using a wildcard App ID cannot use APNs remote push notifications. Use an explicit Bundle ID instead.
1050	APNs request timed out. The push notification may arrive late or may have failed.	Network issue — retry.