Status Codes

This document lists all the status codes of RongIMLib, based on the enumeration ErrorCode.

Connection Status Codes

The app can monitor the connection status of the SDK. The following status codes may be thrown during the connection.

tip

• Before version 5.6.1, the code type in the callback functions of Events.DISCONNECT and Events.SUSPEND was ConnectionStatus.
• Starting from version 5.7.0, the code type in the callback functions of Events.DISCONNECT and Events.SUSPEND is ErrorCode.

ConnectionStatus provides the following connection statuses:

Status Code	Description
0	Connection successful
1	Connecting
2	User actively disconnected
3	Network unavailable, SDK will automatically reconnect
4	Socket unavailable, SDK will automatically reconnect
6	Kicked by another device
9	User banned
12	Domain error

Business Error Codes

-1

TIMEOUT

Unknown error.

Troubleshooting Suggestions:
API request timed out. Try again later. If the issue persists, submit a ticket with details like App Key, User ID, and Issue Occurrence Time.

0

SUCCESS

Success.

Troubleshooting Suggestions: API request successful.

2

ACTIVE_DISCONNECT

Active disconnect.

Troubleshooting Suggestions: The business layer explicitly called disconnect to disconnect.

405

REJECTED_BY_BLACKLIST

Message sending failed because you’ve been added to the recipient’s blacklist.

Troubleshooting Suggestions: Remove the user from the blacklist based on business needs. Refer to Remove User from Blacklist.

20106

FORBIDDEN_IN_PRIVATE

Muted in private chat.

Troubleshooting Suggestions: Unmute the user based on business needs. For details, refer to Set User Private Chat Mute.

20109

SYS_CONVERSATION_NOT_SUPPORT_MESSAGE

System conversations don’t support this message type.

Troubleshooting Suggestions: System conversations only allow RC:SRSMsg type messages. Other message types aren’t supported.

20512

CLOUD_DATA_CENTER_INVALID

The AppKey’s data center doesn’t match the requested cloud control data center.

Troubleshooting Suggestions:

1. If you selected a domestic data center, use the domestic API address when integrating RC server API on the App server. The client defaults to connecting to the domestic data center.
2. If you selected an overseas data center (e.g., Singapore, North America, or Saudi Arabia), use the corresponding overseas API address when integrating RC server API on the App server.
3. Check which data center your app belongs to on the RC Console > App Configuration > Basic Info > AppKey Configuration page.
4. When integrating the client, pass the corresponding area code or manually set the SDK server address.

20604

SEND_FREQUENCY_TOO_FAST

Message sending frequency too high. Only 5 messages per second are allowed.

Troubleshooting Suggestions: Delay the API call on the client side to prevent errors due to excessive frequency.

20606

OPERATION_NOT_SUPPORT

Operation not supported. Only valid for private cloud. The server has disabled this operation.

Troubleshooting Suggestions: Only applicable to private cloud environments. Public cloud users can ignore this.

20607

REQUEST_OVER_FREQUENCY

Request exceeded the call frequency limit. Try again later.

Troubleshooting Suggestions: Query command call limit exceeded. The default limit is 50 calls per second. Keep the client API call frequency within 50 calls per second.

22201

MESSAGE_EXPAND_NOT_EXIST

Ultra group expansion message, but the original message doesn’t exist.

Troubleshooting Suggestions:

1. Ultra group historical messages are stored for 7 days by default. Messages older than 7 days are deleted. Check the message’s sentTime to determine if it’s older than 7 days.
2. The original message may have been manually deleted.

22202

MESSAGE_EXPAND_NOT_SUPPORT

Ultra group expansion message, but the original message doesn’t support expansion.

Troubleshooting Suggestions: The message supports expansion only if canIncludeExpansion is set to true when sending.

22203

MESSAGE_EXPAND_FORMAT_ERROR

Ultra group expansion message, expansion content format error.

Troubleshooting Suggestions: The expansion content failed to be parsed by the server. Expansion content must be in JSON string format, e.g., {"key":"value"}.

22204

MESSAGE_EXPAND_NOT_AUTHORIZED

Ultra group expansion message, no operation permission.

Troubleshooting Suggestions: The conversation type parameter is incorrect. Check if the conversation type value passed is 10.

22406

NOT_IN_GROUP

Not in the group.

Troubleshooting Suggestions:

1. Check if the user is in the group.
2. If the user is in the group but the server still returns this error, submit a ticket with details like App Key, User ID, Group ID, and Issue Occurrence Time.

22408

FORBIDDEN_IN_GROUP

Muted in the group.

Troubleshooting Suggestions: The business layer can unmute the group/ultra group as needed. For details, refer to Group Mute Service.

23406

NOT_IN_CHATROOM

Not in the chatroom.

Troubleshooting Suggestions:

1. Query, join, etc., in the chatroom module.
2. Chatrooms have an automatic destruction mechanism and an automatic exit mechanism for offline members. Triggering these mechanisms may also result in the user not being in the chatroom. You can get detailed information in Chatroom Status Synchronization.
3. If the user is in the chatroom but the server still returns this error, submit a ticket with details like App Key, User ID, Chatroom ID, and Issue Occurrence Time.

23407

GET_USERINFO_ERROR

Chatroom mute whitelist user limit exceeded.

Troubleshooting Suggestions: This error code is returned in two cases:

1. Adding users to the chatroom whitelist, the passed userId exceeds the limit (max 5). For interface details, refer to Add User to Chatroom Whitelist.
2. Adding users to the chatroom global mute whitelist, the passed userId exceeds the limit (max 20). For interface details, refer to Add User to Chatroom Global Mute Whitelist.

23408

FORBIDDEN_IN_CHATROOM

Muted in the chatroom.

Troubleshooting Suggestions:

1. Mute status includes: Set Chatroom Global Mute, Global Mute User, Mute Specific Chatroom User.
2. The business layer can unmute as needed based on the above mute status: Unmute Chatroom Globally, Unmute User Globally, Unmute Specific Chatroom User.

23409

RC_CHATROOM_USER_KICKED

Kicked and banned from the chatroom. The ban duration depends on the time passed when the server called the kick-out interface.

Troubleshooting Suggestions: The business layer can unblock as needed. For details, refer to Unblock Chatroom User.

23410

RC_CHATROOM_NOT_EXIST

Chatroom doesn’t exist.

Troubleshooting Suggestions:

1. Chatrooms have an automatic destruction mechanism and an automatic exit mechanism for offline members. For details, refer to Chatroom Destruction Mechanism and Exit Chatroom documentation. The business layer can observe if these mechanisms caused the issue.
2. You can also query, create, etc., in the chatroom module.

23411

RC_CHATROOM_IS_FULL

Chatroom member limit exceeded. Developers can submit a ticket to request a change in the chatroom member limit.

Troubleshooting Suggestions:

1. Chatroom business defaults to no member limit, but a limit can be configured. First, confirm if a chatroom member limit has been configured.
2. To adjust the chatroom member limit, submit a ticket.

23412

RC_CHATROOM_PATAMETER_INVALID

The chatroom API parameter is invalid. Ensure the parameter is not empty or invalid.

Troubleshooting:

1. Check if the parameter is empty or invalid according to the API documentation.
2. If the issue persists after checking, submit a ticket with details like the API name, parameters, and the time the issue occurred.

23413

CHATROOM_GET_HISTORYMSG_ERROR

An error occurred while retrieving chatroom history messages.

Troubleshooting: Submit a ticket with details like App key, user ID, chatroom ID, and the query time.

23414

CHATROOM_NOT_OPEN_HISTORYMSG_STORE

Chatroom cloud storage is not enabled.

Troubleshooting: Enable chatroom message cloud storage in RC Console > App Configuration > IM Service > Chat pricing plans.

23423

CHATROOM_KV_EXCEED

The chatroom KV attribute limit has been exceeded.

Troubleshooting: The default limit is 100 KV attributes per chatroom.

23424

CHATROOM_KV_OVERWRITE_INVALID

You do not have permission to modify existing KV attribute values in the chatroom.

Troubleshooting: You cannot modify KV attributes set by others. Use the force-set API if needed. Refer to Chatroom Attribute Management (KV).

23425

CHATROOM_SET_PROPERTY_OVER_FREQUENCY

(Deprecated) The chatroom status setting frequency has been exceeded. The limit is 100 status sets or deletes per second.

23426

CHATROOM_KV_STORE_NOT_OPEN

Chatroom attribute customization is not enabled.

Troubleshooting: Enable chatroom attribute customization in RC Console > App Configuration > IM Service > Free Basic Features.

23427

CHATROOM_KEY_NOT_EXIST

The chatroom attribute does not exist.

Troubleshooting:

1. Check if the attribute exists via Query Chatroom Attributes.
2. Chatroom attributes are deleted when the chatroom is destroyed.
3. If autoDelete is set to 1, the attribute is deleted when the user exits the chatroom.
4. If the attribute was not manually deleted, submit a ticket with details like App key, user ID, chatroom ID, KV attribute, and the time the issue occurred.

23428

CHATROOM_KV_STORE_NOT_ALL_SUCCESS

Batch setting or deleting KV attributes was partially unsuccessful.

Troubleshooting: Submit a ticket with details like App key, user ID, chatroom ID, and the time the issue occurred.

23429

CHATROOM_KV_STORE_OUT_LIMIT

The batch setting or deleting of KV attributes exceeded the limit (max 10).

Troubleshooting: The limit is 10 KV attributes per batch. This limit cannot be adjusted.

23431

CHATROOM_KV_SET_ERROR

(Deprecated) Setting the chatroom KV failed because multiple devices attempted to modify the same KV simultaneously. Delay the operation and try again.

24001

HAVNODEVICEID

No DeviceId is registered, meaning the user is not logged in.

Troubleshooting: Submit a ticket with details like App key, user ID, and the time the issue occurred.

24002

DEVICEIDISHAVE

The DeviceId already exists.

Troubleshooting: Submit a ticket with details like App key, user ID, and the time the issue occurred.

24009

FEILD

No corresponding user or Token.

Troubleshooting:

1. Check if the user is registered. Verify the Token's validity in RC Console > Operations Management > User Management.
2. Get a new Token for connection verification.

24011

NULLCHANNELNAME

(Deprecated) ChannelName is empty.

24015

INTERNALERRROR

Internal server error.

Troubleshooting: Submit a ticket with details like App key, user ID, and the time the issue occurred.

24360

RC_USER_PROFILE_KEY_NOT_ALLOW_SDK_SET

No permission to set this user’s managed attribute.

Troubleshooting:

1. The client does not allow setting the uniqueId parameter. Check if uniqueId was set when calling the updateMyUserProfile API.
2. To set uniqueId, use the Server API.

24361

RC_USER_PROFILE_KEY_NOT_EXIST

This key does not exist in the user’s managed basic attribute list.

Troubleshooting: The key for modifying user-managed information does not exist.

24362

RC_USER_PROFILE_EXT_KEY_NOT_EXIST

This key does not exist in the user’s managed extended attribute list.

Troubleshooting: When modifying the userExtProfile field, the key does not exist. Extended user information keys must be set via the RC Console.

24363

RC_USER_PROFILE_EXT_KV_COUNT_EXCEED_LIMIT

The maximum limit for setting user-managed extended attributes has been exceeded.

Troubleshooting: The maximum limit is 20 extended attributes.

24364

RC_USER_PROFILE_VALUE_LENGTH_EXCEED_LIMIT

The Value of the user’s managed basic or extended attribute exceeds the maximum character limit.

Troubleshooting: The maximum length for Value is 256 characters.

24365

RC_USER_PROFILE_QUERY_COUNT_EXCEED_LIMIT

The limit for batch querying user-managed information has been exceeded.

Troubleshooting:

1. The client can query up to 20 users at a time.
2. Using the Server API, you can query up to 100 users at a time.

24366

RC_USER_PROFILE_USER_NOT_EXIST

This user does not exist.

Troubleshooting: The user ID is not registered. Register the user and try again.

24367

RC_USER_PROFILE_VALUE_CAN_ONLY_BE_NUMBERS

The Value of this user-managed attribute can only be a number.

Troubleshooting: Gender, role, and level must be of type integer.

24368

RC_USER_PROFILE_VALUE_EXCEED_RANGE

The Value of this user-managed attribute exceeds the allowed range.

Troubleshooting: When updating user information, the Value must not exceed the allowed range.

24369

RC_USER_PROFILE_SERVICE_UNAVAILABLE

User information management service is not enabled.

Troubleshooting: Enable the service in RC Console > App Configuration > IM Service > Information Management Service > Function Settings.

24401

ULTRA_GROUP_SERVICE_UNAVAILABLE

Ultra group service is not enabled.

Troubleshooting: Enable the service in RC Console > App Configuration > IM Service > Ultra Group Service.

24402

ULTRA_GROUP_SERVICE_ERROR

Ultra group service exception.

Troubleshooting: Submit a ticket with details like App key, user ID, and the time the issue occurred.

24403

ULTRA_GROUP_PARAMETER_ERROR

Ultra group parameter error.

Troubleshooting: Check if the parameters are in the correct format.

24404

ULTRA_GROUP_UNKNOWN_ERROR

Ultra group unknown exception.

Troubleshooting: Submit a ticket with details like App key, user ID, and the time the issue occurred.

24406

NOT_IN_ULTRA_GROUP

Not a member of the ultra group.

Troubleshooting: Query, join, or perform other actions in the ultra group module.

24408

FORBIDDEN_IN_ULTRA_GROUP

Ultra group member is muted.

Troubleshooting:

24410

ULTRA_GROUP_NOT_EXIST

Ultra group does not exist.

Troubleshooting: Create an ultra group.

24412

ULTRA_GROUP_JOINED_OVERSIZE

The limit for joining ultra groups has been exceeded.

Troubleshooting: The maximum limit is 100 ultra groups.

24413

ULTRA_GROUP_CHANNELS_OVERSIZE

The limit for creating ultra group channels has been exceeded.

Troubleshooting: The maximum limit is 50 channels.

24414

ULTRA_GROUP_CHANNEL_ID_NOT_EXIST

Ultra group channel ID does not exist.

Troubleshooting:

1. Create an ultra group channel as needed.

24415

ULTRA_GROUP_MESSAGE_SENT_OVER_FREQUENCY

The message sending limit for the ultra group channel has been exceeded.

Troubleshooting: Each ultra group channel has a message sending frequency limit, defaulting to 20 messages per second. If the total messages sent per second exceed this limit, this error code will be returned. Delay sending or retry.

24416

ULTRA_GROUP_USER_NOT_IN_PRIVATE_CHANNEL

User is not in the ultra group’s private channel.

Troubleshooting:

25101

RECALL_MESSAGE

Invalid message recall parameters. Ensure the parameters are correctly filled.

Troubleshooting: Submit a ticket with details like App key, user ID, and the time the issue occurred.

25102

MESSAGE_STORAGE_SERVICE_UNAVAILABLE

Single and group chat cloud storage service is not enabled.

Troubleshooting: Enable the service in RC Console > App Configuration > IM Service > Chat pricing plans.

25104

RC_SERVER_UNKOWN_ERROR

Unknown exception.

Troubleshooting: Submit a ticket with details like App key, user ID, and the time the issue occurred.

25107

RECALL_MESSAGE_USER_INVALID

IMLib can recall messages sent by yourself or others. The IM service has a switch to control whether only messages sent by yourself can be recalled. When this switch is enabled, recalling messages sent by others will result in this error.

Troubleshooting:

1. By default, IMLib SDK can recall messages sent by any user. When the "IMLib SDK only allows recalling messages sent by yourself" switch is enabled, only messages sent by yourself can be recalled. To enable this service, submit a ticket.
2. When recalling messages via the Server API, no judgment is made, and all messages can be recalled.

25402

RC_ENTRUST_SERVER_ERROR

Entrust service exception.

Troubleshooting: Submit a ticket with details like App key, user ID, and the time the issue occurred.

25403

RC_ENTRUST_SERVER_PARAMETER_ERROR

Entrust service parameter error.

Troubleshooting:

1. Check if the correct parameters are passed.
2. If you have questions, submit a ticket with details like App key, user ID, the specific API called, and the parameters used.

25404

RC_GROUP_ILLEGAL_ERROR

Illegal operation. Non-group owner modifying group permissions. The corresponding key is returned in the msg.

Troubleshooting: Only the group owner has permission to perform this operation. Confirm the group owner ID.

25405

RC_GROUP_AUTHORITY_ERROR

No permission to perform the operation.

Troubleshooting: Confirm the operation permissions (permissions field).

25406

RC_GROUP_PARAMETER_LENGTH_EXCEED_LIMIT

Parameter exception, length exceeds the limit.

Troubleshooting:

1. Check if the parameters are valid and if their length exceeds the limit according to the API documentation.
2. If the parameters are valid but the issue persists, provide the corresponding API and parameter information, and submit a ticket.

25407

RC_GROUP_PARAMETER_FORMAT_ERROR

Parameter exception, illegal characters.

Troubleshooting: The built-in key for group attributes does not exist.

25408

RC_GROUP_PARAMETER_VALUE_CAN_ONLY_BE_NUMBERS

Parameter value must be a number.

Troubleshooting:

1. Check if the parameters are valid and must be numbers according to the API documentation.
2. If the parameters are valid but the issue persists, provide the corresponding API and parameter information, and submit a ticket.

25409

RC_GROUP_ID_ALREADY_EXIST

Group ID already exists.

Troubleshooting: The group ID has already been created. No need to recreate it.

25410

RC_GROUP_ID_NOT_EXIST

Group ID does not exist.

Troubleshooting: The group ID does not exist. Create it as needed.

25411

RC_GROUP_MEMBERS_COUNT_EXCEED_LIMIT

Group member limit exceeded.

Troubleshooting:

1. A maximum of 30 users can be invited to join a group at once.
2. The total group member limit is 3000.

25412

RC_GROUP_MEMBERS_ALREADY_IN_GROUP

Group member ID is already in the group.

Troubleshooting: The user has already joined the group. No need to invite or add them again.

25413

RC_GROUP_NOT_ALLOW_SDK_OPERATION

This operation is not allowed via the SDK.

Troubleshooting: This attribute cannot be modified by the client. Check the Group Custom Attributes in the RC Console.

25414

RC_GROUP_NOT_ALLOW_JOIN

No one is allowed to join the group.

Troubleshooting: Confirm the group’s operation permissions (permissions field).

25415

RC_GROUP_EXT_KEY_NOT_EXIST

The extended information Key does not exist.

Troubleshooting: Add the key in RC Console > App Configuration > IM Service > Information Management Service > Group Custom Attributes.

25416

RC_GROUP_REQUEST_OVERFREQUENCY

Query frequency limit exceeded.

Troubleshooting: The default limit for group entrust - user query related APIs is 5 queries per second. This currently only applies to web clients.

25417

RC_GROUP_OWNER_NOT_ALLOW_QUIT_OR_KICK

The group owner cannot be kicked, quit the group, or be set as an admin.

Troubleshooting: Confirm the user’s role as group owner.

25418

RC_GROUP_USER_NOT_IN_GROUP

User ID is not in the group.

Troubleshooting: Confirm the user’s presence in the group.

25419

RC_GROUP_MANAGER_OR_FOLLOW_COUNT_EXCEED_LIMIT

Admin/follower count exceeds the limit.

Troubleshooting:

1. The maximum number of admins is 20.
2. The maximum number of followers is 200.
3. The maximum group member limit is 3000.

25420

RC_GROUP_USER_IS_NOT_MANAGER_IN_GROUP

The user is not an admin in this group.

Troubleshooting: Set Group Admin as needed.

25421

RC_GROUP_APPLICATION_NOT_EXIST

No invitation request exists for the corresponding group ID and user ID.

Troubleshooting:

1. Invitations are only stored for 7 days. Check if the invitation has expired.
2. Check if an invitation was sent. Invite Others to Join the Group as needed.

25422

RC_GROUP_QUERY_GROUP_COUNT_EXCEED_LIMIT

The limit for querying group information has been exceeded.

Troubleshooting:

1. A maximum of 20 groups can be queried at once.
2. A maximum of 100 group members can be queried at once.

25423

RC_GROUP_NAME_INVALID

Group name cannot be empty.

25424

RC_GROUP_JOIN_GROUP_NEED_MANAGER_ACCEPT

Joining the group requires admin approval.

Troubleshooting: Confirm the group’s operation permissions (permissions field).

25425

RC_GROUP_OWNER_NOT_ALLOW_BE_MANAGER

The group owner cannot be set as an admin.

Troubleshooting: Confirm the user’s role in the group.

25426

RC_GROUP_NO_INVITE_PERMISSION

No permission to invite users to the group.

Troubleshooting:

1. Confirm the group’s operation permissions (permissions field).
2. Confirm the user’s role in the group.

25427

RC_GROUP_NEED_INVITEE_ACCEPT

Inviting users to the group requires the invitee’s acceptance.

Troubleshooting: Confirm the group’s operation permissions (permissions field).

25428

RC_GROUP_APPLICATION_ALREADY_HANDLE

The request has already been processed by another admin.

Troubleshooting: Prompt the user as needed.

25429

RC_GROUP_OLD_GROUP_NOT_ENTRUST

Older groups do not support the entrust API. They must be imported first.

25430

RC_GROUP_ID_INVALID

Group ID is invalid. It contains special characters.

Troubleshooting: Modify the group ID to ensure it only contains letters and numbers.

25432

RC_PAGE_TOKEN_PARSING_FAILED

PageToken parsing failed.

Troubleshooting: Check if the PageToken is correct and if it matches the PageToken returned from the previous request.

25460

RC_FRIEND_ALREADY_FRIEND

You are already friends. The operation is invalid.

Troubleshooting: Confirm the friendship.

25461

RC_FRIEND_NEED_ACCEPT

The other party must accept before you can become friends.

Troubleshooting: Friend request permissions can be set at two levels: appkey and user.

1. Appkey level: Set the "Add Friend Permission" in RC Console > App Configuration > IM Service > Information Management Service - Function Settings.
2. User level: Set the friend request permission.

25462

RC_FRIEND_IN_OTHER_BLACK_LIST

You are in the target user’s blacklist and cannot add them as a friend.

Troubleshooting: Remove User from Blacklist as needed.

25463

RC_FRIEND_NOT_IN_OTHER_WHITE_LIST

You are not in the target user’s whitelist and cannot add them as a friend.

Troubleshooting: The user has enabled the whitelist feature. You must be added to the target user’s whitelist to add them as a friend. Refer to User Whitelist Service.

25464

RC_FRIEND_IN_MY_BLACK LIST

The target user is in your blacklist and cannot be added as a friend.

Troubleshooting: Remove User from Blacklist as needed.

25465

RC_FRIEND_NOT_IN_MY_WHITE_LIST

The target user is not in your whitelist and cannot be added as a friend.

Troubleshooting: You have enabled the whitelist feature. Add the target user to your whitelist to add them as a friend. Refer to User Whitelist Service.

25466

RC_FRIEND_APPLICATION_NOT_EXIST

The friend request does not exist or has expired.

Troubleshooting: Check if the user ID is correct. Friend requests are valid for 7 days. Check if the request has expired.

25467

RC_FRIEND_MY_FRIEND_COUNT_EXCEED_LIMIT

Your friend count has exceeded the limit.

Troubleshooting: The maximum number of friends is 3000. Check your friend list.

25468

RC_FRIEND_OTHER_FRIEND_COUNT_EXCEED_LIMIT

The target user’s friend count has exceeded the limit.

Troubleshooting: The maximum number of friends is 3000. Check the target user’s friend list.

25469

RC_FRIEND_NOT_FRIEND

You are not friends. This operation cannot be performed.

Troubleshooting: Check Friendship.

25470

RC_FRIEND_FIELDS_LENGTH_EXCEED_LIMIT

The friend custom attribute limit has been exceeded.

Troubleshooting: The maximum number of custom attributes is 10.

25471

RC_FRIEND_OTHER_NOT_ALLOW_ADD_FRIEND

The target user has disabled friend requests.

Troubleshooting:

25472

RC_FRIEND_NOT_EXIST

The friend does not exist.

Troubleshooting: The user ID does not exist. Register the user first.

25473

RC_FRIEND_NOT_ALLOW_ADD_SELF

You cannot add yourself as a friend.

Troubleshooting:

1. For Server API, check if the userId and targetId are the same.
2. For client API, check if the userId matches the user ID connected to RC.

26001

PUSH_PARAMETER_INVALID

The user-level setting service request parameter is invalid.

Troubleshooting: Submit a ticket with details like App key, user ID, the specific API called, and the parameters used.

26002

USER_SETTING_SYNCED_ERROR

The client version is too low. Sync the version number and submit a ticket to enable user-level configuration.

Troubleshooting: Submit a ticket to enable user-level configuration.

26004

CONVERSATION_TAG_OVERSIZE

The user conversation tag limit has been exceeded. The maximum is 20 tags.

Troubleshooting: The maximum number of tags is 20.

26005

RC_READ_RECEIPT_V4_INVALID

V4 read receipt is not enabled.

Troubleshooting: Submit a ticket.

26007

RC_SERVER_PARAMETER_MESSAGEUIDS_CONFUSED

The message ID order is incorrect.

Troubleshooting: Check the StartMsgId and EndMsgId parameters. Ensure StartMsgId is not earlier than EndMsgId.

26009

RC_SERVER_PARAMETER_MESSAGEUID_INVALID

The message ID is invalid.

Troubleshooting: Check the messageUid parameter.

26010

RC_SERVER_PARAMETER_INVALID

The parameter is invalid.

Troubleshooting: Submit a ticket with details like App key, user ID, the specific API called, and the parameters used.

26020

RC_SUBSCRIBE_ONLINE_SERVICE_UNAVAILABLE

Online status subscription is not enabled.

Troubleshooting: Enable client user online status subscription in RC Console > App Configuration > IM Service > Chat pricing plans.

26021

RC_BESUBSCRIBED_USERIDS_COUNT_EXCEED_LIMIT

The user subscription limit has been exceeded. Refer to the documentation for details.

Troubleshooting: The maximum number of subscriptions per user is 5000.

26022

RC_SUBSCRIBED_USERIDS_EXCEED_LIMIT

The subscription user limit has been exceeded. Refer to the documentation for details.

Troubleshooting: The maximum number of subscriptions is 5000.

26106

RC_FILE_SIZE_EXCEED_LIMIT

The uploaded file exceeds the maximum size limit.

Troubleshooting: The maximum file size is 100 MB.

26107

INVALID_PARAMETER_SIZE_NOT_FOUND

The size parameter is missing when enabling the limit.

Troubleshooting: Pass the size parameter when uploading files. The unit is KB.

30001

RC_NET_CHANNEL_INVALID

The current connection has been released.

Troubleshooting:

1. Use the Events.SUSPEND or Events.DISCONNECT event listener to determine the cause of the connection error.
2. Try reconnecting with a more stable network. If the issue persists, submit a ticket with details like App key, user ID, and the time the issue occurred.

30002

RC_NET_UNAVAILABLE

The current connection is unavailable.

Troubleshooting:

1. Other asynchronous APIs can only be called after connect succeeds.
2. Check the connection status via getConnectionStatus(). A return value of 0 indicates a successful connection.

30003

RC_MSG_RESP_TIMEOUT

The client’s message request timed out on the RC server.

Troubleshooting: The ack response timed out. Try again later or with a more stable network. If the issue persists, submit a ticket with details like App key, user ID, and the time the issue occurred.

30005

RC_HTTP_REQ_FAIL

The request to connect to the navigation address failed.

Troubleshooting: Try again later or with a more stable network. If the issue persists, submit a ticket with details like App key, user ID, and the time the issue occurred.

30007

RC_NAVI_REQ_FAILED

The navigation returned an abnormal result.

Troubleshooting: Try again later or with a more stable network. If the issue persists, submit a ticket with details like App key, user ID, and the time the issue occurred.

30010

RC_SOCKET_NOT_CREATED

Connection creation failed.

Troubleshooting: Multiple CMP addresses failed to connect. Try again later or with a more stable network. If the issue persists, submit a ticket with details like App key, user ID, and the time the issue occurred.

30011

RC_SOCKET_DISCONNECTED

The connection was disconnected.

Troubleshooting: Try again later or with a more stable network. If the issue persists, submit a ticket with details like App key, user ID, and the time the issue occurred.

30012

RC_PING_EXCEED_LIMIT

Ping failed.

Troubleshooting: This is usually caused by network issues. The SDK will automatically reconnect until the network is restored.

30016

RC_MSG_CONTENT_EXCEED_LIMIT

The message size exceeds the limit. The maximum size is 128 KB (after serialization to JSON).

Troubleshooting:

1. A common cause is sending an image message with a thumbnail that’s too large. Ensure the base64 thumbnail does not exceed 80 KB.
2. Ensure the JSON.stringify content length does not exceed 128 KB.

30019

RC_NETWORK_DOWN

The network connection is unavailable.

Troubleshooting: Try again later or with a more stable network. If the issue persists, submit a ticket with details like App key, user ID, and the time the issue occurred.

30021

RC_TCP_DISCONNECTED_NO_RMTP

TCP connection succeeded, but RMTP connection failed.

Troubleshooting: Try again later or with a more stable network. If the issue persists, submit a ticket with details like App key, user ID, and the time the issue occurred.

31000

RC_CONN_ACK_TIMEOUT

Connection ACK timed out.

Troubleshooting: Try again later or with a more stable network. If the issue persists, submit a ticket with details like App key, user ID, and the time the issue occurred.

31001

RC_CONN_PROTO_VERSION_ERROR

The signaling version is incorrect.

Troubleshooting: Submit a ticket with details like App key, user ID, and the time the issue occurred.

31002

RC_CONN_IDENTIFIER_REJECTED

The client info field format is incorrect.

Troubleshooting:

1. The correct format is: {platform type}-{device info}-{sdk version}, where device info is: {phone type}|{phone model}|{network type, 4G/WIFI}|{operator, China Mobile/China Telecom/China Unicom}.
2. Submit a ticket with details like App key, user ID, and the time the issue occurred.

31003

RC_CONN_SERVER_UNAVAILABLE

Mini Program (or desktop) service is not enabled.

Troubleshooting: Enable the service in RC Console > App Configuration > IM Service > Mini Program Service Settings (Desktop Service Settings).

31004

RC_CONN_TOKEN_INCORRECT

The Token is invalid; the AppKey and Token do not match; or the Token has expired.

Troubleshooting:

1. Ensure the appkey passed during app initialization matches the appkey used to get the Token on the server.
2. Check the Token’s validity period in RC Console > App Configuration > Basic Info.
3. Get a new Token for connection verification.

31006

RC_CONN_REDIRECTED

The connection was redirected.

Troubleshooting:

1. This usually occurs during service scaling when the endpoint has changed, and the userId is connected to an old node.
2. The SDK automatically reconnects by requesting navigation to get the CMP address.

31008

RC_CONN_APP_BLOCKED_OR_DELETED

The AppKey is blocked or deleted.

Troubleshooting: 用户可以在RC Console > App Configuration > Basic Info申请恢复。

31009

RC_CONN_USER_BLOCKED

Connection failed—user blocked.

Troubleshooting: Unblock the user if needed. See Unblock User.

31010

RC_DISCONN_KICK

User kicked offline.

Troubleshooting:

1. By default, a user can only be online on one device at a time.
2. For multi-device login (e.g., multiple web tabs), see Multi-Device Online.

31011

RC_DISCONN_EXCEPTION

IM connection disconnected—user blocked.

Troubleshooting: Unblock the user if needed. See Unblock User.

31020

RC_CONN_TOKEN_EXPIRED

Token expired.

Troubleshooting:

1. 请检查融云控制台 > 应用配置 > 基本信息设置 token 的有效期。
2. 建议在融云控制台 > 北极星 > Server Api 调试重新获取一个 token 验证连接。

31022

RC_CONN_HOSTNAME_ERROR

Page domain not in the safe domain whitelist.

Troubleshooting: Check if the domain is in the Safe Domain Configuration. Add it if needed.

31023

RC_DISCONN_SAME_CLIENT_ON_LINE

Same client type already online—reconnection not allowed.

Troubleshooting: See Reconnection and Kick Policy.

31024

RC_LISCENSE_COUNT_OUT_OF_LIMIT

Connection limit exceeded—private cloud only.

Troubleshooting:

1. Check the connection limit in the private cloud management backend.
2. To adjust the limit, change the AppKey.

31029

RC_ACCOUNT_CANCELLATION

User account canceled.

Troubleshooting:

1. Check if the user is canceled via Query Canceled Users.
2. Reactivate the user if needed. See Reactivate User.

31030

RC_LICENSE_EXPIRED

Private Cloud license check failed; App license expired.

Troubleshooting:

1. Check if the Identification Code and License in the Private Cloud backend are expired.
2. If expired, contact your sales rep.
3. If using the HarmonyOS SDK, contact your sales rep.

32001

RC_QUERY_ACK_NO_DATA

Protocol layer internal error; data error during query, upload, or download.

Troubleshooting: Submit a ticket with details like App Key, User ID, and issue time.

32002

RC_MSG_DATA_INCOMPLETE

Protocol layer internal error.

Troubleshooting: Submit a ticket with details like App Key, User ID, and issue time.

32011

RC_UDP_DISCONNECTED

Server actively disconnected (only under QUIC Protocol).

Troubleshooting: Submit a ticket with details like App Key, User ID, and issue time.

32054

RC_TCP_RESET

Connection interrupted by the server; SDK will auto-reconnect.

Troubleshooting: Retry later or switch networks. If the issue persists, submit a ticket with details like App Key, User ID, and issue time.

32061

CONNECTION_REFUSED

Connection refused.

Troubleshooting: SDK will auto-retry navigation to get the CMP Address and reconnect.

33000

PROTOCOL_MESSAGE_SAVED_ERROR

Failed to save the message to the local database.

Troubleshooting:

1. Check device memory.
2. Ensure the connect operation succeeded.
3. If the issue persists, submit a ticket with details like App Key, User ID, and issue time.

33001

BIZ_ERROR_CLIENT_NOT_INIT

Not initialized.

Troubleshooting Suggestion: Check if the init interface was called.

33002

BIZ_ERROR_DATABASE_ERROR

Database error.

Troubleshooting Suggestion:

1. Check if init and connect were called successfully.
2. If the issue persists, submit a ticket with necessary information.

33003

BIZ_ERROR_INVALID_PARAMETER

Invalid parameter passed during developer API call.

Troubleshooting Suggestion: Check if the parameter format matches the interface documentation.

33004

BIZ_ERROR_NO_CHANNEL

Invalid channel.

Troubleshooting Suggestion: Retry later or switch to a stable network. If the issue persists, submit a ticket with necessary information.

33006

BIZ_ERROR_CONNECTING

Connection in progress; subsequent connect calls are rejected.

Troubleshooting Suggestion: Check for duplicate connect calls.

33007

MSG_ROAMING_SERVICE_UNAVAILABLE

Historical message cloud storage service not enabled.

Troubleshooting Suggestion:

1. Check if the service is enabled in RC Console > App Configuration > IM Service > Chat pricing plans.
2. If enabled recently, try uninstalling and reinstalling the app.

33008

MSG_INSERT_ERROR

Failed to save message to local database.

Troubleshooting Suggestion:

1. Check if init and connect were called successfully.
2. Ensure the device has sufficient memory.
3. If the issue persists, submit a ticket with necessary information.

33009

MSG_DEL_ERROR

Chatroom recycled.

Troubleshooting Suggestion: Confirm chatroom status.

33100

TAG_NOT_EXIST

Tag does not exist.

Troubleshooting Suggestion:

1. Check if the tag exists by retrieving the tag list. Refer to documentation.
2. If it doesn’t exist, create it as needed. Refer to documentation.

33101

TAG_EXISTS

Tag already exists.

Troubleshooting Suggestion: Check if the tag exists by retrieving the tag list. Refer to documentation.

33102

NO_TAG_IN_CONVER

Tag not in conversation.

Troubleshooting Suggestion: Check if the tag exists in the conversation by retrieving all tags. Refer to documentation.

34001

RC_CONNECTION_EXIST

Connection already exists.

Troubleshooting Suggestion: No need to call connect again.

34005

PACKAGE_ENVIRONMENT_ERROR

Incorrect connection environment.

Troubleshooting Suggestion:

1. This error applies to private cloud; public cloud users can ignore it.
2. Using public cloud SDK in a private cloud environment triggers this error.
3. Private cloud SDKs carry an enterprise identifier.
4. Contact your sales representative if unsure.

34006

CONNECTION_TIMEOUT

Connection timeout.

Troubleshooting Suggestion:

1. Check connection status via connection state listener.
2. Retry later or switch to a stable network. If the issue persists, submit a ticket with necessary information.

34008

MESSAGE_KV_NOT_SUPPORT

Message cannot be expanded; only single group chats are supported.

Troubleshooting Suggestion: Ensure the canIncludeExpansion property is set to true before sending. Refer to sendMessage interface documentation.

34010

EXPANSION_LIMIT_EXCEET

Message expansion size exceeds limit.

Troubleshooting Suggestion: Default expansion key length is 32 characters, value length is 4096 characters, and no more than 300 key-value pairs.

34011

UPLOAD_FAIL

Media file HTTP upload failed.

Troubleshooting Suggestion: Retry later or switch to a stable network. If the issue persists, submit a ticket with necessary information.

34013

CONVER_OUT_LIMIT_ERROR

Number of conversations added/removed from tag exceeds limit.

Troubleshooting Suggestion: Maximum of 1000 conversations supported.

34014

READ_RECEIPT_ERROR

Group read receipt version not supported.

Troubleshooting Suggestion: Web sendReadReceiptResponseV2 handles this based on navigation values; public and private clouds won’t return this error.

34016

PUSH_CONTENT_CONFIG_SERVICE_UNAVAILABLE

User-level settings not enabled.

Troubleshooting Suggestion: Submit a ticket.

34018

MEDIA_EXCEPTION

Media file upload exception; file missing or size is 0.

Troubleshooting Suggestion:

1. Use instanceof to check if the file is a File object:

  // Assuming file is obtained from your business layer
  file instanceof File

2. If using RongIMLib.sendImageMessage, ensure the file type is image:

  // Assuming file is obtained from your business layer
  file.type.match(/^image\//)

3. If using RongIMLib.sendHQVoiceMessage, ensure the file type is audio:

  // Assuming file is obtained from your business layer
  file.type.match(/^audio\//)

34022

METHOD_NOT_SUPPORT

Interface does not support ultra group conversations.

Troubleshooting Suggestion: Check if conversationType is 10. Refer to documentation.

34201

CONVERSATION_TYPE_NOT_SUPPORT

Interface does not support the passed conversation type.

Troubleshooting Suggestion: Check if the parameter format matches the interface documentation.

34202

INVALID_PARAMETER_TIMESTAMP

Invalid timestamp passed during developer API call.

Troubleshooting Suggestion: Check parameter type via API DOC.

34203

INVALID_PARAMETER_MESSAGE_UID

Invalid uid (server message unique ID) passed during developer API call.

Troubleshooting Suggestion: Check parameter type via API DOC.

34204

INVALID_PARAMETER_MESSAGE_ID

Invalid messageId passed during developer API call or corresponding message not found.

Troubleshooting Suggestion: Check parameter type via API DOC.

34205

INVALID_PARAMETER_MESSAGE_CONTENT

Invalid Message or MessageContent passed during developer API call.

Troubleshooting Suggestion: Check parameter type via API DOC.

34206

MSG_LIMIT_ERROR

Invalid messageList passed during developer API call.

Troubleshooting Suggestion: Check parameter type via API DOC.

34207

INVALID_PARAMETER_MEDIA_TYPE

Invalid mediaType passed during developer API call.

Troubleshooting Suggestion: Check if the parameter belongs to FileType enum.

34209

INVALID_PARAMETER_CONVERSATION_TYPE

Invalid ConversationType passed during developer API call.

Troubleshooting Suggestion: Check parameter type via API DOC.

34210

INVALID_PARAMETER_TARGET_ID

Invalid targetId passed during developer API call.

Troubleshooting Suggestion: Check parameter type via API DOC.

34211

INVALID_PARAMETER_CHANNEL_ID

Invalid channelId passed during developer channel-related API call.

Troubleshooting Suggestion: Ensure the parameter is of type {String}, with a length between 0-20 characters, and no underscores.

34212

INVALID_PARAMETER_TAG_ID

The tagId in the API call is invalid.

Troubleshooting: Ensure the parameter is a String and its length is between 1-10 characters.

34213

INVALID_PARAMETER_TAG_NAME

The tagName in the API call is invalid.

Troubleshooting: Ensure the parameter is a String and its length is between 1-15 characters.

34214

INVALID_PARAMETER_USER_ID

The userId in the API call is invalid.

Troubleshooting: Check the parameter type in the API DOC.

34215

INVALID_PARAMETER_USERIDLIST

The userIdList in the API call is invalid.

Troubleshooting: Check the parameter type in the API DOC.

34217

INVALID_PARAMETER_DOWNLOADMEDIAFILENAME

The downloadMediaFileName in the API call is invalid.

Troubleshooting: Check the parameter type in the API DOC.

34220

INVALID_PARAMETER_MESSAGE_EXPANSION

The MessageExpansion in the API call is invalid.

Troubleshooting: Check the parameter type in the API DOC.

34225

INVALID_PARAMETER_CONVERSATION

The conversation parameter is invalid.

Troubleshooting: Check if the parameter belongs to the IConversationOption type.

34228

INVALID_PARAMETER_NOTIFICATION_LEVEL

The PushNotificationLevel is invalid.

Troubleshooting: Check the parameter type in the API DOC.

34229

INVALID_PARAMETER_MESSAGE_ARRAY

The messageIds parameter in the API call is invalid.

Troubleshooting: Check the parameter type in the API DOC.

34230

INVALID_PARAMETER_RECEIVED_STATUS

The ReceivedStatus parameter in the API call is invalid.

Troubleshooting:

1. If the parameter is receivedStatus, check if it belongs to the ReceivedStatus enum.
2. If the parameter is receivedStatusInfo, check if it belongs to the IReceivedStatusInfo type.

34231

INVALID_PARAMETER_CHANNEL_TYPE

The UltraGroupChannelType is invalid.

Troubleshooting: Check if the parameter belongs to the UltraGroupChannelType enum.

34232

INVALID_PARAMETER_COUNT

The count in the API call is invalid.

Troubleshooting: Check the parameter type in the API DOC.

34235

INVALID_PARAMETER_MEDIA_URL

The mediaUrl in the API call is invalid.

Troubleshooting: Check the parameter type in the API DOC.

34236

INVALID_PARAMETER_UNIQUE_ID

The uniqueId in the API call is invalid.

Troubleshooting: Check the parameter type in the API DOC.

34238

INVALID_PARAMETER_PROXY

The proxy configuration is invalid. RongIMProxy is empty or invalid.

Troubleshooting: Check the parameter type in the API DOC.

34239

INVALID_PARAMETER_TESTHOST

The proxy test service in the API call testProxy is invalid.

Troubleshooting: Check the parameter type in the API DOC.

34242

INVALID_PARAMETER_CONVERSATIONS

The conversations parameter in the API call is invalid.

Troubleshooting:

1. Ensure the parameter is an Array.
2. The array length must be greater than 0.
3. Each element in the array must be of the IConversationOption type.

34244

INVALID_PARAMETER_SENT_STATUS

The Message.SentStatus parameter in the API call is invalid.

Troubleshooting: Check if the parameter belongs to the SentStatus enum.

34245

RC_CONN_PROXY_UNAVAILABLE

The proxy address is unavailable.

Troubleshooting: The user is currently connected. It’s recommended to call disconnect first and then retry.

34259

INVALID_PARAMETER_RTCROOMID

The rtcRoomID parameter is invalid.

Troubleshooting: Check the parameter type in the API DOC.

34260

INVALID_PARAMETER_KEY

The key parameter is invalid.

Troubleshooting: Check the parameter type in the API DOC.

34261

INVALID_PARAMETER_KEYS

The keys parameter is invalid.

Troubleshooting: Check the parameter type in the API DOC.

34262

INVALID_PARAMETER_VALUE

The value parameter is invalid.

Troubleshooting: Check the parameter type in the API DOC.

34263

INVALID_PARAMETER_ENTRIES

The entries parameter is invalid.

Troubleshooting: Check the parameter type in the API DOC.

34264

INVALID_PARAMETER_NOTIFICATION_EXTRA

The notificationExtra parameter is invalid.

Troubleshooting:

1. Ensure the parameter is a String.
2. The string length must not exceed 2048 characters.

34272

INVALID_PARAMETER_BEFORE

The before parameter is invalid.

Troubleshooting:

1. Check the parameter type in the API DOC.
2. The parameter must be an integer and greater than or equal to 0.

34273

INVALID_PARAMETER_AFTER

The after parameter is invalid.

Troubleshooting:

1. Check the parameter type in the API DOC.
2. The parameter must be an integer and greater than or equal to 0.

34274

INVALID_PARAMETER_KEYWORD

The keyword parameter is invalid.

Troubleshooting: Check the parameter type in the API DOC.

34276

INVALID_PARAMETER_OFFSET

The offset parameter is invalid.

Troubleshooting:

1. Check the parameter type in the API DOC.
2. The parameter must be an integer and greater than or equal to 0.

34277

INVALID_PARAMETER_START_TIME

The start time parameter is invalid.

Troubleshooting: Check the parameter type in the API DOC.

34278

INVALID_PARAMETER_END_TIME

The end time parameter is invalid.

Troubleshooting: Check the parameter type in the API DOC.

34279

INVALID_PARAMETER_LIMIT

The limit parameter is invalid.

Troubleshooting: Check the parameter type in the API DOC.

34280

INVALID_MESSAGE_DIRECTION

The MessageDirection is invalid.

Troubleshooting: Check if the parameter belongs to the MessageDirection type.

34284

INVALID_PARAMETER_CONVERSATION_TYPE_LIST

The ConversationType list parameter is invalid.

Troubleshooting:

1. Ensure the parameter is an Array.
2. The array elements must be of the ConversationType enum.

34287

INVALID_PARAMETER_CONVERSATION_LIST

The conversationList array in the API call is invalid.

Troubleshooting:

1. Ensure the parameter is an Array.
2. The array length must be between 1-100.
3. Each element in the array must be of the IConversationOption type.

34288

INVALID_PARAMETER_CLEAR_MESSAGE_OPTION_LIST

The ClearMessageOption array in the API call is invalid.

Troubleshooting:

1. Ensure the parameter is an Array.
2. The array length must be between 1-20.
3. Each element in the array must be of the IClearMessageOption type.

34289

INVALID_PARAMETER_START_MESSAGE_UID

The startMessageUID parameter is invalid.

Troubleshooting: Check the parameter type in the API DOC.

34290

INVALID_PARAMETER_END_MESSAGE_UID

Invalid endMessageUID parameter.

Troubleshooting: Verify the parameter type via API DOC.

34291

READ_RECEIPT_V4_NOT_SUPPORT

V4 read receipt not supported.

Troubleshooting:

1. Only Global IM UIKit supports V4 read receipts.
2. If you're using Global IM UIKit and still encounter this issue, submit a ticket for assistance.

34296

RC_DIRECTIONAL_MESSAGE_INVALID_CONVERSATION_TYPE

Unsupported conversation type for directional messages.

Troubleshooting: Only GROUP and ULTRA_GROUP conversation types are supported. Refer to the documentation for details.

34306

INVALID_PARAMETER_SUBSCRIBE_TYPE

Invalid subscription type.

Troubleshooting: Ensure the subscribeType belongs to the SubscribeType enum.

34307

INVALID_PARAMETER_SUBSCRIBE_EXPIRY

Invalid subscription duration [60s ~ 30 days].

Troubleshooting: The value must be a timestamp between 60 and 30 * 24 * 60 * 60.

34308

INVALID_PARAMETER_SUBSCRIBE_PUBLISHER_USERIDS

Invalid or empty subscription user list.

Troubleshooting:

1. Ensure the parameter is an Array.
2. Length must be between 1 and 200.
3. Elements must be strings with lengths between 1 and 64.

34309

INVALID_PARAMETER_SUBSCRIBE_PAGESIZE

Invalid page size.

Troubleshooting:

1. Ensure the parameter is a Number.
2. Value must be between 1 and 200.

34310

SUB_PROCESS_EXIT

Subprocess terminated unexpectedly. SDK will auto-reconnect if connected.

Troubleshooting:

1. Set runInMainProcess to true during electron main process initialization. Refer to the Electron initialization documentation.
2. If a crash occurs, take a screenshot and submit it via a ticket for troubleshooting.

34311

ADDON_NOT_EXIST

Addon module missing.

Troubleshooting:

1. Check if the .node file exists in node_modules/@rongcloud/electron/binding. If not, reinstall dependencies.
2. If SDK version is below 5.8.3, upgrade to the latest version. Refer to the version description for details.

34312

INVALID_PARAMETER_USER_PROFILE

Invalid userProfile parameter.

Troubleshooting: Ensure the parameter belongs to the IUserProfileInfo type.

34313

INVALID_PARAMETER_USER_PROFILE_VISIBILITY

Invalid userProfileVisibility parameter.

Troubleshooting: Ensure the parameter belongs to the UserProfileVisibility enum.

34314

INVALID_PARAMETER_EXTRA

Invalid extra parameter.

Troubleshooting: Ensure the parameter is a string with a length between 0 and 128.

34318

INVALID_PARAMETER_GROUP_INFO

Invalid GroupInfo parameter.

Troubleshooting: Ensure the parameter belongs to the IGroupInfoOption type.

34319

INVALID_PARAMETER_GROUP_ID

Invalid groupId parameter.

Troubleshooting:

1. Ensure the parameter is a string.
2. Length must be between 1 and 64 after removing spaces and line breaks.

34320

INVALID_PARAMETER_GROUP_NAME

Invalid groupName parameter.

Troubleshooting:

1. Ensure the parameter is a string.
2. Length must be between 1 and 64 after removing spaces and line breaks.

34321

INVALID_PARAMETER_GROUP_IDS

Invalid groupIds parameter.

Troubleshooting:

1. Ensure the parameter is an Array.
2. Length must be between 1 and 200.
3. Elements must be strings with lengths between 1 and 64 after removing spaces and line breaks.

34322

INVALID_PARAMETER_GROUP_MEMBER_ROLE

Invalid GroupMemberRole parameter.

Troubleshooting: Ensure the parameter belongs to the GroupMemberRole enum.

34323

INVALID_PARAMETER_GROUP_APPLICATION_STATUS

Invalid GroupApplicationStatus parameter.

Troubleshooting:

1. Ensure the parameter is an Array.
2. Length must not be 0.
3. Elements must conform to the GroupApplicationStatus enum definition.

34324

INVALID_PARAMETER_GROUP_APPLICATION_DIRECTION

Invalid GroupApplicationDirection parameter.

Troubleshooting:

1. Ensure the parameter is an Array.
2. Length must not be 0.
3. Elements must conform to the GroupApplicationDirection enum definition.

34325

INVALID_PARAMETER_NICK_NAME

Invalid nickname parameter.

Troubleshooting:

1. Ensure the parameter is a string.
2. Length must be between 1 and 64 after removing spaces and line breaks.

34326

INVALID_PARAMETER_REASON

Invalid reason parameter.

Troubleshooting:

1. Ensure the parameter is a string.
2. Length must be between 0 and 128 after removing spaces and line breaks.

34327

INVALID_PARAMETER_REMARK

Invalid remark parameter.

Troubleshooting:

1. Ensure the parameter is a string.
2. Length must be between 0 and 64 after removing spaces and line breaks.

34328

INVALID_PARAMETER_PAGING_QUERY_OPTION

Invalid PagingQueryOption parameter.

Troubleshooting: Ensure the parameter belongs to the IPagingQueryOption type.

34330

INVALID_PARAMETER_QUERY_FRIENDS_DIRECTION_TYPE

Invalid QueryFriendsDirectionType parameter.

Troubleshooting: Ensure the parameter belongs to the QueryFriendsDirectionType enum.

34331

INVALID_PARAMETER_DIRECTION_TYPE

Invalid DirectionType parameter.

Troubleshooting: Ensure the parameter belongs to the DirectionType enum.

34332

INVALID_PARAMETER_FRIEND_APPLICATION_TYPE

Invalid FriendApplicationType parameter.

Troubleshooting: Ensure the parameter belongs to the FriendApplicationType enum.

34333

INVALID_PARAMETER_FRIEND_APPLICATION_STATUS

Invalid FriendApplicationStatus parameter.

Troubleshooting: Ensure the parameter belongs to the FriendApplicationStatus enum.

34334

INVALID_PARAMETER_FRIEND_ADD_PERMISSION

Invalid FriendAddPermission parameter.

Troubleshooting: Ensure the parameter belongs to the FriendAddPermission enum.

34335

INVALID_PARAMETER_FRIEND_INFO_EXT_FIELDS

Invalid extProfile parameter.

Troubleshooting:

1. Ensure the parameter is an object.
2. Values must be strings.

35001

GROUP_SYNC_ERROR

(Deprecated) Group info abnormal.

35002

GROUP_MATCH_ERROR

(Deprecated) Matched group info abnormal.

35004

NOT_SUPPORT

Method not supported.

Troubleshooting: This method is exclusive to @rongcloud/electron. Refer to the Integration Guide (Electron) documentation for details.

35005

MAIN_PROCESS_ERROR

Main process method error.

Troubleshooting: Submit a ticket for assistance. Include App key, user ID, called interface and parameters, and the time the issue occurred.

35007

CAN_NOT_RECONNECT

(Deprecated) Already connected or in the process of internal reconnection. Reconnection is not allowed until the disconnect method is called.

35008

SERVER_UNAVAILABLE

No available IM server address.

Troubleshooting: Retry later or switch to a stable network. If the issue persists, submit a ticket for assistance. Include App key, user ID, and the time the issue occurred.

35009

HOSTNAME_ERROR

(Deprecated) Connecting domain not within the secure domain range after setting a secure domain on the web.

35010

HAS_OHTER_SAME_CLIENT_ON_LINE

(Deprecated) A client of the same type is already online. Connection prohibited.

35011

METHOD_NOT_AVAILABLE

Ultra group-related functions unavailable until the full list of ultra group conversations is retrieved after initial IM connection.

Troubleshooting: The SDK event listener includes Events.ULTRA_GROUP_ENABLE, indicating ultra group conversation list synchronization is complete. Refer to the event listener documentation for details.

35014

METHOD_ONLY_SUPPORT_ULTRA_GROUP

This feature is only supported for ultra groups.

35015

DRAFT_SAVE_ERROR

Failed to save draft.

Troubleshooting: Submit a ticket for assistance. Include App key, user ID, passed parameters, and the time the issue occurred.

35016

DRAFT_REMOVE_ERROR

Failed to delete draft.

Troubleshooting: Submit a ticket for assistance. Include App key, user ID, passed parameters, and the time the issue occurred.

35020

CONVER_REMOVE_ERROR

Failed to delete conversation.

Troubleshooting: Submit a ticket for assistance. Include App key, user ID, passed parameters, and the time the issue occurred.

35021

CONVER_GET_ERROR

Failed to get conversation.

Troubleshooting:

1. The specified conversation data is not in the SDK memory state.
2. Call the getConversationList method to get the conversation list and check if the conversation exists.

35022

SEARCH_PROPS_LIMIT_ERROR

Invalid search field for message.

Troubleshooting: Ensure the parameter is a string with a length greater than 0.

35024

INVALID_PARAMETER_MESSAGE_TYPE

Invalid message type.

Troubleshooting: Verify the parameter type via API DOC.

35025

INVALID_PARAMETER_ORDER

Invalid order parameter.

Troubleshooting: Ensure the parameter value is 0 or 1.

35028

INVALID_PARAMETER_DRAFT

Invalid draft parameter.

Troubleshooting: Verify the parameter type via API DOC.

35029

INVALID_PARAMETER_MESSAGE

Invalid message parameter. Message must be an object or a subclass of BaseMessage.

Troubleshooting: Verify the parameter type via API DOC.

35030

INVALID_PARAMETER_PUSH_CONTENT

Invalid pushContent parameter.

Troubleshooting: Verify the parameter type via API DOC.

35031

INVALID_PARAMETER_SENDOPTIONS

Invalid sendOptions parameter.

Troubleshooting: Verify the parameter type via API DOC.

35032

INVALID_PARAMETER_CONTENT_DISPOSITION

Invalid contentDisposition parameter.

Troubleshooting:

1. Ensure the parameter value is inline or attachment.
2. inline for online preview, attachment for download.
3. attachment for download attachment.

35033

INVALID_PARAMETER_SAVE_NAME

Invalid saveName parameter.

Troubleshooting: Verify the parameter type via API DOC.

35034

INVALID_PARAMETER_SERVER_TYPE

Invalid serverType parameter.

Troubleshooting:

1. Ensure the parameter is a Number.
2. Supported values are 1 | 2 | 3 | 4 | 5, corresponding to Qiniu, Alibaba Cloud, Amazon, STC, and Minio uploads.

35035

INVALID_PARAMETER_CLEAN_SPACE

Invalid cleanSpace parameter.

Troubleshooting: Verify the parameter type via API DOC.

35036

INVALID_PARAMETER_CAN_INCLUDE_EXPANSION

Invalid canIncludeExpansion parameter.

Troubleshooting: Verify the parameter type via API DOC.

35037

INVALID_PARAMETER_DISABLE_NOTIFICATION

Invalid disableNotification parameter.

Troubleshooting: Verify the parameter type via API DOC.

35038

INVALID_PARAMETER_CHECK_DUPLICATE

Invalid checkDuplicate parameter.

Troubleshooting: Verify the parameter type via API DOC.

35039

INVALID_PARAMETER_IS_AUTO_DELETE

Invalid isAutoDelete parameter.

Troubleshooting: Verify the parameter type via API DOC.

35040

INVALID_PARAMETER_IS_SEND_NOTIFICATION

Invalid isSendNotification parameter.

Troubleshooting: Verify the parameter type via API DOC.

35041

INVALID_PARAMETER_IS_FORCE

Invalid isForce parameter.

Troubleshooting: Verify the parameter type via API DOC.

35042

INVALID_PARAMETER_IS_TOP

The isTop passed by the developer is invalid.

Troubleshooting suggestion: Check the interface parameter type via API DOC.

35043

INVALID_PARAMETER_IS_UPDATE_TIME

The isUpdateTime passed by the developer is invalid.

Troubleshooting suggestion: Check the interface parameter type via API DOC.

35044

INVALID_PARAMETER_CONTAIN_MUTED

The containMuted passed by the developer is invalid.

Troubleshooting suggestion: Check the interface parameter type via API DOC.

35045

INVALID_PARAMETER_IS_STATUS_MESSAGE

The isStatusMessage passed by the developer is invalid.

Troubleshooting suggestion: Check the interface parameter type via API DOC.

35046

INVALID_PARAMETER_IS_MENTIONED

The isMentioned passed by the developer is invalid.

Troubleshooting suggestion: Check the interface parameter type via API DOC.

35047

INVALID_PARAMETER_IS_VOIP_PUSH

The isVoipPush passed by the developer is invalid.

Troubleshooting suggestion: Check the interface parameter type via API DOC.

35048

INVALID_PARAMETER_MENTIONED_TYPE

The mentionedType passed by the developer is invalid.

Troubleshooting suggestion: Ensure the parameter value is 1 or 2.

35049

INVALID_PARAMETER_PUSH_CONFIG

The pushConfig passed by the developer is invalid.

Troubleshooting suggestion: Check the interface parameter type via API DOC.

35050

INVALID_PARAMETER_PUSH_DATA

The pushData passed by the developer is invalid.

Troubleshooting suggestion: Check the interface parameter type via API DOC.

36001

CHATROOM_ID_ISNULL

【Deprecated】The chatroom ID is empty when joining.

36002

CHARTOOM_JOIN_ERROR

【Deprecated】Failed to join the chatroom.

36003

CHATROOM_HISMESSAGE_ERROR

【Deprecated】Failed to retrieve chatroom history messages.

36004

CHATROOM_KV_NOT_FOUND

【Deprecated】Chatroom KV not found.

37001

BLACK_ADD_ERROR

【Deprecated】Exception when adding to the blacklist.

37002

BLACK_GETSTATUS_ERROR

【Deprecated】Exception when retrieving the status of a specified person in the blacklist.

37003

BLACK_REMOVE_ERROR

【Deprecated】Exception when removing from the blacklist.

38001

DRAF_GET_ERROR

【Deprecated】Failed to retrieve the draft.

41002

QNTKN_GET_ERROR

【Deprecated】Failed to retrieve the Qiniu token.