Status Codes

SDK Status Codes

-1

UNKNOWN

Unknown error.

Troubleshooting Suggestions:

1. This error occurs when the method to get remote push language settings returns an incorrect type, or when methods like updating session information or read status fail.
2. If the issue persists, submit a ticket with the user's appkey, user ID, and timestamp for our technical team to analyze client logs. Alternatively, provide local adb logs for analysis.

-2

IPC_DISCONNECT

The IPC process terminated unexpectedly. This can happen when the system reclaims resources and then calls the interface. The SDK will automatically reconnect. It can also occur if libRongIMLib.so or libsqlite.so is missing or crashes.

Troubleshooting Suggestions:

1. The Android IMLib SDK defaults to multi-process mode. When the app is in the background, the system may kill the IPC process due to resource limits. The SDK will restart the IPC process when the app returns to the foreground. If you're using SDK version 5.3.0 or later, switch to single-process mode to avoid this issue. Refer to the documentation for setting single-process mode.
2. Provide the user's appkey, user ID, and timestamp for our technical team to analyze client logs. Alternatively, provide local adb logs.

-4

APP_NOT_CONNECT

The app didn't call the connect() method before calling business methods. Call this method after a successful connection.

Troubleshooting Suggestions:

1. Ensure the connection method is called and returns a successful connection before calling business methods. For example, call RC's connection method before joining a chatroom.

0

SUCCESS

Success.

Troubleshooting Suggestions:

405

REJECTED_BY_BLACKLIST

The message failed to send because the recipient has blocked you.

Troubleshooting Suggestions: Depending on your business needs, you can unblock the user. Refer to the documentation.

20109

RC_CONVERSATION_NOT_SUPPORT_MESSAGE

The system conversation doesn't support this message type.

Troubleshooting Suggestions: System conversations only support RC:SRSMsg type messages. Other message types are not 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's 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's server API on the app server. When integrating the client, pass the corresponding region code or manually set the SDK's server address.

20604

MSG_SEND_OVERFREQUENCY

The message sending frequency is too high. Only 5 messages per second are allowed.

Troubleshooting Suggestions: Delay the interface call on the client side to prevent exceeding the frequency limit.

20606

RC_OPERATION_NOT_SUPPORT

The operation isn't supported. This is only valid for private clouds, as the server has disabled this operation.

Troubleshooting Suggestions: Submit a ticket to contact us.

20607

RC_REQUEST_OVERFREQUENCY

The request exceeded the call frequency limit. Please try again later.

Troubleshooting Suggestions: The default limit for query-type signaling calls is 50 times per second. Ensure the client's interface call frequency is within this limit.

21406

NOT_IN_DISCUSSION

Not in the discussion group.

Troubleshooting Suggestions: This error code has been deprecated.

21501

RC_MSG_BLOCKED_SENSITIVE_WORD

The message was blocked due to containing sensitive words, and the sender can't send the message.

Troubleshooting Suggestions:

1. Check the sensitive words configuration in the backend at RC Console > App Configuration > Security & Audit > Sensitive Words Settings.
2. The filtering method is to block messages.
3. The business layer can delete sensitive words or send messages that don't contain sensitive words as needed.

21502

RC_MSG_REPLACED_SENSITIVE_WORD

The sensitive words in the message have been replaced, and the recipient can receive the modified message.

Troubleshooting Suggestions:

1. Check the sensitive words configuration in the backend at RC Console > App Configuration > Security & Audit > Sensitive Words Settings.
2. The filtering method is to replace sensitive words.
3. The business layer can delete sensitive words or send messages that don't contain sensitive words as needed.

22201

RC_ORIGINAL_MESSAGE_NOT_EXIST

Ultra group extension message, but the original message doesn't exist.

Troubleshooting Suggestions:

1. Ultra group history 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

RC_ORIGINAL_MESSAGE_CANT_EXPAND

Ultra group extension message, but the original message doesn't support extension.

Troubleshooting Suggestions: A message supports extension only if canIncludeExpansion is set to true when sending the message.

22203

RC_MESSAGE_EXPAND_FORMAT_ERROR

Ultra group extension message, but the extension content format is incorrect.

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

22204

RC_MESSAGE_EXPAND_NOT_AUTHORIZED

Ultra group extension message, but there's no operation permission.

Troubleshooting Suggestions: The conversation type passed in is incorrect. Check if the conversation type value 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 returns this error, submit a ticket to contact us.

22408

FORBIDDEN_IN_GROUP

Muted in the group.

Troubleshooting Suggestions: The business layer can unmute the group/ultra group as needed. Refer to the group mute service documentation for details.

23406

NOT_IN_CHATROOM

Not in the chatroom.

Troubleshooting Suggestions:

1. Chatrooms have an automatic destruction mechanism and an offline member auto-exit mechanism. Refer to the chatroom destruction mechanism and quit chatroom documentation. The business layer can observe if these mechanisms are causing the issue.
2. You can also query or join the chatroom.
3. If the user is in the chatroom but the server returns this error, submit a ticket to contact us.

23407

GET_USER_INFO_ERROR

The chatroom mute whitelist exceeds the limit (maximum 5). When creating a chatroom, the mute whitelist user list supports batch setting, with a maximum of 20 users.

Troubleshooting Suggestions: Refer to the chatroom mute service documentation for details.

23408

FORBIDDEN_IN_CHATROOM

Muted in the chatroom.

Troubleshooting Suggestions:

1. Mute status includes: set chatroom-wide mute, globally mute user, mute specific chatroom user.
2. The business layer can unmute as needed based on the above mute status: unmute chatroom-wide, unmute globally muted user, unmute specific chatroom user.

23409

KICKED_FROM_CHATROOM

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

Troubleshooting Suggestions: The business layer can unban as needed. Refer to the unban chatroom user documentation for details.

23410

RC_CHATROOM_NOT_EXIST

The chatroom doesn't exist.

Troubleshooting Suggestions:

1. Chatrooms have an automatic destruction mechanism and an offline member auto-exit mechanism. Refer to the chatroom destruction mechanism and quit chatroom documentation. The business layer can observe if these mechanisms are causing the issue.
2. You can also query or join the chatroom.

23411

RC_CHATROOM_IS_FULL

The chatroom member limit has been exceeded. Developers can submit a ticket to request a change in the chatroom member limit.

Troubleshooting Suggestions:

1. By default, chatrooms have no member limit, but a limit can be configured. Confirm if a member limit has been configured.
2. If you need to adjust the chatroom member limit, submit a ticket to contact us.

23412

RC_CHATROOM_ILLEGAL_ARGUMENT

The chatroom interface parameter is invalid. Confirm if the parameter is empty or valid.

Troubleshooting Suggestions:

1. Check if the parameter is empty or valid according to the interface documentation.
2. If the issue persists after checking the parameter, submit a ticket to contact us, providing necessary information such as the interface name, interface parameters, and the time the issue occurred.

23414

ROAMING_SERVICE_UNAVAILABLE_CHATROOM

The {Cloud Storage Service for Chatroom} is not enabled.

Troubleshooting: Enable the {Cloud Storage Service for Chatroom Messages} in the {RC Console} under {Configuration} > {Chat settings} > {Chat pricing plans} here.

23423

EXCEED_MAX_KV_SIZE

The number of {KV Attributes of Chatroom} exceeds the limit.

Troubleshooting: The {Default Limit for a Single Chatroom} is 100.

23424

TRY_OVERWRITE_INVALID_KEY

You don’t have permission to modify existing attribute values in the chatroom.

Troubleshooting: The {Business Layer} can’t modify KV attribute values set by others. Use the {Forced Setting Interface} to set them. For details, refer to the {Chatroom Attribute Management (KV)} documentation here.

23425

EXCEED_MAX_CALL_API_SIZE

(Deprecated) Exceeded the {State Setting Frequency in Chatroom}. A single chatroom can set and delete states up to 100 times per second.

23426

KV_STORE_NOT_AVAILABLE

The {Custom Attribute Setting Service for Chatroom} is not enabled.

Troubleshooting: Enable the {Custom Attribute Setting Service for Chatroom} in the {RC Console} under {Configuration} > {Chat settings} > {Free Basic Features} here.

23427

KEY_NOT_EXIST

The {Chatroom Attribute Does Not Exist}.

Troubleshooting: Submit a {Support Ticket} here to contact us.

23428

KV_STORE_NOT_ALL_SUCCESS

Batch Set or Delete Key-Value in Chatroom was not fully successful.

Troubleshooting: Submit a ticket to contact us.

23429

KV_STORE_OUT_OF_LIMIT

Batch Set or Delete Key-Value in Chatroom Quantity Exceeds Limit (max 10 at a time).

Troubleshooting: The quantity range is 1-10 and cannot be adjusted.

23431

RC_KV_CONCURRENT_SET_ERROR

(Deprecated) Failed to set Key-Value in Chatroom due to simultaneous operations. Wait and retry to avoid conflicts.

23437

RC_CHATROOM_EXTRA_SIZE_LIMIT_EXCEED

Extra Information length exceeds the limit when joining a Chatroom.

Troubleshooting: Configurable on the server side, default max length is 128 characters.

24360

RC_USER_PROFILE_KEY_NOT_ALLOW_SDK_SET

No permission to set this User Trusteeship Attribute.

Troubleshooting:

1. The Client doesn’t allow setting the uniqueId parameter. Check if uniqueId is set when calling updateMyUserProfile.
2. Use the Server API to set uniqueId if needed.

24361

RC_USER_PROFILE_KEY_NOT_EXIST

This key doesn’t exist in the User Trusteeship Basic Attributes key list.

Troubleshooting: The key for modifying User Trusteeship Information doesn’t exist.

24362

RC_USER_PROFILE_EXT_KEY_NOT_EXIST

This key doesn’t exist in the User Trusteeship Extended Attributes key list.

Troubleshooting: The key for extended user information needs to be set via the RC Console.

24363

RC_USER_PROFILE_EXT_KV_COUNT_EXCEED_LIMIT

Exceeded the Maximum Limit of User Trusteeship Extended Attributes.

Troubleshooting: The Maximum Limit is 20.

24364

RC_USER_PROFILE_VALUE_LENGTH_EXCEED_LIMIT

The Value of User Trusteeship Basic or Extended Attributes exceeds the max character limit.

Troubleshooting: The max length is 256 characters.

24365

RC_USER_PROFILE_QUERY_COUNT_EXCEED_LIMIT

Batch Query User Trusteeship Information Quantity Exceeds Limit.

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 doesn’t exist.

Troubleshooting: The User ID isn’t registered. Register User and try again.

24367

RC_USER_PROFILE_VALUE_CAN_ONLY_BE_NUMBERS

Value of This User Trusteeship Attribute Can Only Be Numbers.

Troubleshooting: Gender, Role, and Level must be Integer Type.

24368

RC_USER_PROFILE_VALUE_EXCEED_RANGE

Value of This User Trusteeship Attribute Exceeds the Set Value Range.

Troubleshooting: When updating user information, the Value must not exceed the set Value Range.

24369

RC_USER_PROFILE_SERVICE_UNAVAILABLE

User Information Trusteeship Function Not Enabled.

Troubleshooting: Enable the User Information Trusteeship Service in the RC Console > Application Configuration > IM Service > Information Trusteeship Service > Function Settings.

24401

RC_ULTRA_GROUP_DISABLED

Ultra Group Function Not Enabled.

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

24402

RC_ULTRA_GROUP_SERVICE_ABNORMAL

Ultra Group Service Exception.

Troubleshooting: Submit a ticket to contact us.

24403

RC_ULTRA_GROUP_PARAMETER_ERROR

Ultra Group Parameter Error.

Troubleshooting: Check if the parameter format is correct.

24404

RC_ULTRA_GROUP_UNKNOWN_ERROR

Ultra Group Unknown Exception.

Troubleshooting: Submit a ticket to contact us.

24406

RC_NOT_IN_ULTRA_GROUP

Not an Ultra Group Member.

Troubleshooting: Query, join, and perform other actions in the Ultra Group module via RC Console > North Star > Server API Debugging.

24408

FORBIDDEN_IN_ULTRA_GROUP

Ultra Group Member Muted.

Troubleshooting:

24410

RC_ULTRA_GROUP_NOT_EXIST

Ultra Group Doesn’t Exist.

Troubleshooting: Create an Ultra Group via RC Console > North Star > Server API Debugging.

24412

RC_ULTRA_GROUP_NUMBER_EXCEED_LIMIT

User Joins Ultra Group Quantity Exceeds Limit.

Troubleshooting: The max limit for joining Ultra Groups is 100.

24413

RC_ULTRA_GROUP_CHANNELS_EXCEED_LIMIT

Create Ultra Group Channel, Channel Quantity Exceeds Limit.

Troubleshooting: The max limit for creating Ultra Group Channels is 50.

24414

RC_ULTRA_GROUP_CHANNEL_ID_NOT_EXIST

Ultra Group Channel ID Doesn’t Exist.

Troubleshooting:

1. Create Ultra Group Channels as needed via RC Console > North Star > Server API Debugging.

24415

ULTRA_GROUP_MESSAGE_SENT_OVER_FREQUENCY

Ultra Group Channel Sends Messages Exceeds Limit.

Troubleshooting: Each Ultra Group Channel has a Message Sending Frequency Limit, defaulting to 20 messages per second. Delay or retry sending if the limit is exceeded.

24416

RC_ULTRA_GROUP_USER_NOT_IN_PRIVATE_CHANNEL

User Not in Ultra Group Private Channel.

Troubleshooting:

25101

RC_RECALL_PARAMETER_INVALID

Recall Message Parameter Invalid. Confirm if the Recall Message parameters are correctly filled.

Troubleshooting: Submit a ticket to contact us.

25102

MESSAGE_STORAGE_SERVICE_UNAVAILABLE

Single and Group Chat Cloud Storage Service Not Enabled.

Troubleshooting: Enable the Single and Group Chat Cloud Storage Service in the RC Console > Application Configuration > IM Service > Chat pricing plans.

25104

RC_SERVER_UNKNOWN_ERROR

Unknown Exception.

Troubleshooting: Submit a ticket to contact us.

25107

RC_RECALL_MESSAGE_USER_INVALID

IMLib Recall Message Can Recall Messages Sent by Yourself and Others. The IM service has a switch to control whether only messages sent by yourself can be recalled. When this switch is turned on, recalling messages sent by others will result in this error.

Troubleshooting:

1. By default, the IMLib SDK allows recalling messages sent by any user. After enabling [IMLib SDK Only Allows Recalling Messages Sent by Yourself], only messages sent by yourself can be recalled. Submit a ticket to contact us.
2. When recalling messages via the Server API, no judgment is performed, and all messages can be recalled.

25402

RC_ENTRUST_SERVER_ERROR

Trusteeship Service Exception.

Troubleshooting: Submit a ticket to contact us.

25403

RC_ENTRUST_SERVER_PARAMETER_ERROR

Entrust Service parameter error.

Troubleshooting

1. Check if the correcr parameters are passed.
2. If you have any questions, submit a ticket to contact us.

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 the permission to perform this operation. Confirm the Group Owner ID.

25405

RC_GROUP_AUTHORITY_ERROR

No permission to operate.

Troubleshooting: Confirm the Group 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 interface documentation.
2. If the parameters are valid but the issue persists, provide the corresponding interface and parameter information, and submit a ticket to contact us.

25407

RC_GROUP_PARAMETER_FORMAT_ERROR

Parameter exception, illegal characters.

Troubleshooting: The built-in key for Custom 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 interface documentation.
2. If the parameters are valid but the issue persists, provide the corresponding interface and parameter information, and submit a ticket to contact us.

25409

RC_GROUP_ID_ALREADY_EXIST

Group ID already exists.

Troubleshooting: The Group ID has already been created and does not need to be recreated.

25410

RC_GROUP_ID_NOT_EXIST

Group ID does not exist.

Troubleshooting: The Group ID does not exist, you can create it as needed.

25411

RC_GROUP_MEMBERS_COUNT_EXCEED_LIMIT

Group Members exceed the limit.

Troubleshooting

1. A maximum of 30 users can be invited to join a group at a time.
2. The total number of Group Members cannot exceed 3000.

25412

RC_GROUP_MEMBERS_ALREADY_IN_GROUP

Group Member ID is already in the current group.

Troubleshooting: The user has already successfully joined the group, no need to perform the invitation or join operation again.

25413

RC_GROUP_NOT_ALLOW_SDK_OPERATION

This operation is not allowed via SDK.

Troubleshooting: This attribute cannot be modified by the client. You can view it in RC Console > App Configuration > IM Service > Entrust Service > Custom Group Attributes.

25414

RC_GROUP_NOT_ALLOW_JOIN

No one is allowed to join, unable to join the group.

Troubleshooting: Confirm the Group Permissions (permissions field).

25415

RC_GROUP_EXT_KEY_NOT_EXIST

Extension information key does not exist.

Troubleshooting: You can add it in RC Console > App Configuration > IM Service > Entrust Service > Custom Group Attributes.

25416

RC_GROUP_REQUEST_OVERFREQUENCY

Query frequency exceeds the limit.

Troubleshooting: The Group Entrust > user query related interface has a frequency limit, default is 5 times/s, currently only limited on the web side.

25417

RC_GROUP_OWNER_NOT_ALLOW_QUIT_OR_KICK

Group Owner cannot be kicked out/quit the group.

Troubleshooting: Confirm if the user is the Group Owner.

25418

RC_GROUP_USER_NOT_IN_GROUP

User ID is not in the group.

Troubleshooting: Confirm if the user is in the group.

25419

RC_GROUP_MANAGER_OR_FOLLOW_COUNT_EXCEED_LIMIT

Manager/follow count exceeds the limit.

Troubleshooting

1. The maximum number of group managers is 20.
2. The maximum number of followers is 200.
3. The maximum number of Group Members is 3000.

25420

RC_GROUP_USER_IS_NOT_MANAGER_IN_GROUP

The user is not a manager in the current group.

Troubleshooting: The business layer can set group manager as needed.

25421

RC_GROUP_APPLICATION_NOT_EXIST

No invitation request corresponding to the Group ID and user ID.

Troubleshooting

1. Invitation information is only saved for 7 days, please check if the invitation time has exceeded the validity period.
2. Check if an invitation has been initiated, the business layer can invite others to join the group as needed.

25422

RC_GROUP_QUERY_GROUP_COUNT_EXCEED_LIMIT

Query group information count exceeds the limit.

Troubleshooting

1. Query group information up to 20 at a time.
2. Query Group Members up to 100 at a time.

25423

RC_GROUP_NAME_INVALID

Group name cannot be empty.

Troubleshooting:

25424

RC_GROUP_JOIN_GROUP_NEED_MANAGER_ACCEPT

Application to join the group requires manager approval.

Troubleshooting: Confirm the Group Permissions (permissions field).

25425

RC_GROUP_OWNER_NOT_ALLOW_BE_MANAGER

Group Owner cannot be set as manager.

Troubleshooting: Confirm the user's identity in the group.

25426

RC_GROUP_NO_INVITE_PERMISSION

No permission to invite people to the group.

Troubleshooting

1. Confirm the Group Permissions (permissions field).
2. Confirm the user's identity in the group.

25427

RC_GROUP_NEED_INVITEE_ACCEPT

Invitation to join the group requires invitee's acceptance.

Troubleshooting: Confirm the Group Permissions (permissions field).

25428

RC_GROUP_APPLICATION_ALREADY_HANDLE

When the manager or Group Owner processes the request, another manager has already processed it.

Troubleshooting: The business layer can prompt for processing as needed.

25429

RC_GROUP_OLD_GROUP_NOT_ENTRUST

Old groups do not support calling Entrust interfaces, they need to be imported first.

Troubleshooting:

25430

RC_GROUP_ID_INVALID

Group ID is invalid, 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 is the pagetoken returned from the last request result.

25460

RC_FRIEND_ALREADY_FRIEND

Already friends, operation is invalid.

Troubleshooting: Confirm if they are mutual friends.

25461

RC_FRIEND_NEED_ACCEPT

Need the other party's acceptance to become friends.

Troubleshooting: You can set Friend addition permissions at two levels, appkey level and user level

1. Appkey level: You can set it in RC Console > App Configuration > IM Service > Entrust Service - Function Settings under the Friend function configuration 【Friend Addition Permission Settings】.
2. User level: You can set it via the client method set Friend addition permission.

25462

RC_FRIEND_IN_OTHER_BLACK_LIST

In the target user's Blacklist, cannot add as Friend.

Troubleshooting: The business layer can remove users from the Blacklist as needed.

25463

RC_FRIEND_NOT_IN_OTHER_WHITE_LIST

Not in the target user's Whitelist, cannot add as Friend.

Troubleshooting: The user has enabled the Whitelist function, and needs to be added to the target user's Whitelist to add as a Friend. For details, refer to the user Whitelist service.

25464

RC_FRIEND_IN_MY_BLACK_LIST

Target user is in the current user's Blacklist, cannot add as Friend.

Troubleshooting: The business layer can remove users from the Blacklist as needed.

25465

RC_FRIEND_NOT_IN_MY_WHITE_LIST

Not in the current user's Whitelist, cannot add as Friend.

Troubleshooting: The user has enabled the Whitelist function, and needs to be added to the target user's Whitelist to add as a Friend. For details, refer to the user Whitelist service.

25466

RC_FRIEND_APPLICATION_NOT_EXIST

Operation is invalid, the Friend request does not exist or has expired.

Troubleshooting: Check if the passed user ID is correct, the Friend request is valid for 7 days, please check if it has expired.

25467

RC_FRIEND_MY_FRIEND_COUNT_EXCEED_LIMIT

Current user's Friend count exceeds the limit.

Troubleshooting: The maximum number of Friends is 3000, you can view the total number of Friends.

25468

RC_FRIEND_OTHER_FRIEND_COUNT_EXCEED_LIMIT

Target user's Friend count exceeds the limit.

Troubleshooting: The maximum number of Friends is 3000, you can view the total number of Friends.

25469

RC_FRIEND_NOT_FRIEND

Not a Friend relationship, cannot perform this operation.

Troubleshooting:

25470

RC_FRIEND_FIELDS_LENGTH_EXCEED_LIMIT

Custom Friend Attributes exceed the limit.

Troubleshooting: A maximum of 10 Custom Friend Attributes can be set.

25471

RC_FRIEND_OTHER_NOT_ALLOW_ADD_FRIEND

The other party has set not to allow adding as a Friend.

Troubleshooting:

25403

RC_ENTRUST_SERVER_PARAMETER_ERROR

Entrusted service parameter error.

Troubleshooting:

1. Check if the correct parameters are passed.
2. If in doubt, submit a ticket to contact us.

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 group's operation permissions (permissions field).

25407

RC_GROUP_PARAMETER_FORMAT_ERROR

Parameter exception. Invalid 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 as per the interface documentation.
2. If the parameters are valid but the issue persists, provide the corresponding interface and parameter information, and submit a ticket to contact us.

25409

RC_GROUP_ID_ALREADY_EXIST

Group ID already exists.

Troubleshooting: The group ID has already been created and does not need to be recreated.

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 the group at once.
2. The total number of group members cannot exceed 3000.

25412

RC_GROUP_MEMBERS_ALREADY_IN_GROUP

Group member ID is already in the current group.

Troubleshooting: The user has already successfully joined the group. No need to perform the invitation or join operation again.

25413

RC_GROUP_NOT_ALLOW_SDK_OPERATION

This operation is not allowed via SDK.

Troubleshooting: This attribute cannot be modified by the client. Check it in RC Console > App Configuration > IM Service > Information Hosting Service > Group Custom Attributes.

25414

RC_GROUP_NOT_ALLOW_JOIN

No one is allowed to join. Unable to join the group.

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

25415

RC_GROUP_EXT_KEY_NOT_EXIST

Extension information key does not exist.

Troubleshooting: Add it in RC Console > App Configuration > IM Service > Information Hosting Service > Group Custom Attributes.

25416

RC_GROUP_REQUEST_OVERFREQUENCY

Query frequency limit exceeded.

Troubleshooting: The frequency of user query-related interfaces in group hosting is limited to 5 times per second by default. Currently, only the web side is restricted.

25417

RC_GROUP_OWNER_NOT_ALLOW_QUIT_OR_KICK

The group owner cannot be kicked out or quit the group.

Troubleshooting: Confirm if the user is the group owner.

25418

RC_GROUP_USER_NOT_IN_GROUP

User ID is not in the group.

Troubleshooting: Confirm if the user is in the group.

25419

RC_GROUP_MANAGER_OR_FOLLOW_COUNT_EXCEED_LIMIT

The number of managers/followers exceeds the limit.

Troubleshooting:

1. The maximum number of group managers is 20.
2. The maximum number of followers is 200.
3. The maximum number of group members is 3000.

25420

RC_GROUP_USER_IS_NOT_MANAGER_IN_GROUP

The user is not a manager in the current group.

Troubleshooting: The business layer can set group manager as needed.

25421

RC_GROUP_APPLICATION_NOT_EXIST

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

Troubleshooting:

1. Invitation information is only saved for 7 days. Check if the invitation time has exceeded the validity period.
2. Check if an invitation has been initiated. The business layer can invite others to join the group as needed.

25422

RC_GROUP_QUERY_GROUP_COUNT_EXCEED_LIMIT

The number of group information queries exceeds the limit.

Troubleshooting:

1. A maximum of 20 group information queries can be performed at once.
2. A maximum of 100 group member queries can be performed at once.

25423

RC_GROUP_NAME_INVALID

Group name cannot be empty.

Troubleshooting:

25424

RC_GROUP_JOIN_GROUP_NEED_MANAGER_ACCEPT

Application to join the group requires manager 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 a manager.

Troubleshooting: Confirm the user's identity in the group.

25426

RC_GROUP_NO_INVITE_PERMISSION

No permission to invite others to the group.

Troubleshooting:

1. Confirm the group's operation permissions (permissions field).
2. Confirm the user's identity in the group.

25427

RC_GROUP_NEED_INVITEE_ACCEPT

Invitation to join the group requires the invitee's acceptance.

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

25428

RC_GROUP_APPLICATION_ALREADY_HANDLE

When the manager or group owner processes the request, another manager has already handled it.

Troubleshooting: The business layer can prompt for handling as needed.

25429

RC_GROUP_OLD_GROUP_NOT_ENTRUST

Old groups do not support calling the hosting interface. They need to be imported first.

Troubleshooting:

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

Page token parsing failed.

Troubleshooting: Check if the page token is correct and if it is the page token returned from the last request result.

25460

RC_FRIEND_ALREADY_FRIEND

Already friends. The operation is invalid.

Troubleshooting: Confirm if they are friends.

25461

RC_FRIEND_NEED_ACCEPT

Need the other party's acceptance to become friends.

Troubleshooting: Set friend addition permissions from two dimensions: appkey level and user level.

1. Appkey level: Set it in RC Console > App Configuration > IM Service > Information Hosting Service - Function Settings under [Friend Addition Permission Settings].
2. User level: Set it via the client method set friend addition permission.

25462

RC_FRIEND_IN_OTHER_BLACK_LIST

In the target user's blacklist. Cannot add as a friend.

Troubleshooting: The business layer can remove user from blacklist as needed.

25463

RC_FRIEND_NOT_IN_OTHER_WHITE_LIST

Not in the target user's whitelist. Cannot add as a friend.

Troubleshooting: The user has enabled the whitelist function. The target user needs to add them to the whitelist. Refer to the user whitelist service for details.

25464

RC_FRIEND_IN_MY_BLACK_LIST

The target user is in the current user's blacklist. Cannot add as a friend.

Troubleshooting: The business layer can remove user from blacklist as needed.

25465

RC_FRIEND_NOT_IN_MY_WHITE_LIST

Not in the current user's whitelist. Cannot add as a friend.

Troubleshooting: The user has enabled the whitelist function. The target user needs to add them to the whitelist. Refer to the user whitelist service for details.

25466

RC_FRIEND_APPLICATION_NOT_EXIST

The operation is invalid. The friend request does not exist or has expired.

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

25467

RC_FRIEND_MY_FRIEND_COUNT_EXCEED_LIMIT

The current user's friend count exceeds the limit.

Troubleshooting: The maximum number of friends is 3000. Check the total number of friends.

25468

RC_FRIEND_OTHER_FRIEND_COUNT_EXCEED_LIMIT

The target user's friend count exceeds the limit.

Troubleshooting: The maximum number of friends is 3000. Check the total number of friends.

25469

RC_FRIEND_NOT_FRIEND

Not friends. Cannot perform this operation.

Troubleshooting:

25470

RC_FRIEND_FIELDS_LENGTH_EXCEED_LIMIT

Friend custom attributes exceed the limit.

Troubleshooting: A maximum of 10 custom attributes are allowed.

25471

RC_FRIEND_OTHER_NOT_ALLOW_ADD_FRIEND

The other party has set to disallow adding as a friend.

Troubleshooting:

25472

RC_FRIEND_NOT_EXIST

Friend does not exist.

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

25473

RC_FRIEND_NOT_ALLOW_ADD_SELF

Cannot add yourself as a friend.

Troubleshooting:

1. For Server API, check that the userId and targetId passed in the interface are not the same.
2. For client interface, check that the userId passed in is not the same as the user ID currently connected to RC service.

26001

RC_PUSHSETTING_PARAMETER_INVALID

User-level configuration service request parameter is invalid.

Troubleshooting: Submit a ticket to contact us.

26002

RC_SETTING_SYNC_FAILED

Indicates the client version is low and needs to sync the version number. You can submit a ticket to apply for enabling the user-level configuration switch.

Troubleshooting:

1. Submit a ticket to apply for enabling the user-level configuration switch.
2. If the service is already enabled and the issue persists, submit a ticket to contact us.

26003

RC_SERVICE_INTERNAL_ERROR

Internal service error.

Troubleshooting: Submit a ticket to contact us.

26004

RC_TAG_LIMIT_EXCEED

The number of user conversation tags exceeds the limit. A maximum of 20 tags are supported.

Troubleshooting: A maximum of 20 tags are supported.

26005

RC_READ_RECEIPT_V4_INVALID

V4 read receipt is not enabled.

Troubleshooting: Submit a ticket to contact us.

26007

RC_SERVER_PARAMETER_MESSAGEUIDS_CONFUSED

Message ID order is incorrect.

Troubleshooting: Check the StartMsgId and EndMsgId parameters to ensure the StartMsgId time is not earlier than the EndMsgId time.

26009

RC_SERVER_PARAMETER_MESSAGEUID_INVALID

Message ID is invalid.

Troubleshooting: Check the messageUid parameter passed in.

26010

RC_SERVER_PARAMETER_INVALID

Parameter is incorrect.

Troubleshooting: Submit a ticket to contact us.

26020

RC_SUBSCRIBE_ONLINE_SERVICE_UNAVAILABLE

Online status subscription feature is not enabled.

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

26021

RC_BESUBSCRIBED_USERIDS_COUNT_EXCEED_LIMIT

The number of users being subscribed has reached the limit. Refer to the development documentation for details.

Troubleshooting: The maximum number of users being subscribed is 5000.

26022

RC_SUBSCRIBED_USERIDS_EXCEED_LIMIT

The number of subscribed users has reached the limit. Refer to the development documentation for details.

Troubleshooting: The maximum number of subscribed users is 5000.

26106

RC_FILE_SIZE_EXCEED_LIMIT

Uploaded file exceeds the maximum limit.

Troubleshooting: The maximum file upload limit is 100 MB.

26107

INVALID_PARAMETER_SIZE_NOT_FOUND

Size parameter is missing when enabling the limit.

Troubleshooting: When uploading a file, pass the size parameter in bytes.

26200

RC_TRANSLATION_CODE_SUCCESS

Translation successful.

26201

RC_TRANSLATION_CODE_AUTH_FAILED

Translation failed due to RC authentication failure or token expiration.

Troubleshooting: Translation failed due to RC authentication failure, token expiration, or empty token. Please obtain a new authentication token.

26202

RC_TRANSLATION_CODE_SERVER_AUTH_FAILED

Translation failed due to translation service provider authentication failure. RC server issue, token is invalid.

Troubleshooting: Translation failed due to RC authentication failure, token expiration, or empty token. Please obtain a new authentication token.

26203

RC_TRANSLATION_CODE_TRANSLATE_FAILED

Translation failed. The translation service provider returned a failure. Refer to the provider's failure code for details.

Troubleshooting: Submit a ticket to contact us.

26204

RC_TRANSLATION_CODE_SERVICE_UNAVAILABLE

Translation failed. Translation feature is not enabled in RC.

Troubleshooting: Submit a ticket to contact us.

26205

RC_TRANSLATION_CODE_CURRENT_LIMITING

Translation failed due to RC rate limiting.

26206

RC_TRANSLATION_CODE_SERVER_INVALID_AUTH_TOKEN

Translation failed. Server lacks the secret for authentication token. Enable it in RC Console.

Troubleshooting: Enable it in RC Console > App Configuration > IM Service > IM Translation.

26208

RC_TRANSLATION_CODE_SERVER_INVALID_EXTRACT_RESULT

Short audio transcription result is empty. Verify the codec type.

Troubleshooting: Submit a ticket to contact us.

26209

RC_TRANSLATION_CODE_SERVER_INVALID_LANGUAGE

Language setting is incorrect. (Speech-to-text is not yet available).

Troubleshooting: Submit a ticket to contact us.

26210

RC_TRANSLATION_CODE_SERVER_INVALID_ENCODING_TYPE

Encoding format setting is incorrect.

Troubleshooting: Submit a ticket to contact us.

29102

RC_APP_PUBLICSERVICE_DEFFOLLOWED

(Deprecated) Official account is followed by default for the `ConversationType_APP_PUBLIC_SERVICE` conversation type.

29103

RC_APP_PUBLICSERVICE_FOLLOWED

(Deprecated) Official account is followed for the `ConversationType_APP_PUBLIC_SERVICE` conversation type.

29104

RC_APP_PUBLICSERVICE_DEFUNFOLLOWED

(Deprecated) Official account is unfollowed by default for the `ConversationType_APP_PUBLIC_SERVICE` conversation type.

29105

RC_APP_PUBLICSERVICE_UNFOLLOWED

(Deprecated) (Mini Program) Official account is unfollowed for the `ConversationType_APP_PUBLIC_SERVICE` conversation type.

29106

RC_APP_PUBLICSERVICE_UNFOLLOW

(Deprecated) (Mini Program) Official account is not followed for the `ConversationType_APP_PUBLIC_SERVICE` conversation type.

29201

RC_PUBLICSERVICE_ERROR_TYPE

(Deprecated) Invalid Public Service Account. (The Public Service Account session identified by Conversation Type and ID is invalid). For the `ConversationType_PUBLIC_SERVICE` conversation type.

29202

RC_PUBLICSERVICE_DEFFOLLOWED

(Deprecated) Public Service Account is followed by default. For the `ConversationType_PUBLIC_SERVICE` conversation type.

29203

RC_PUBLICSERVICE_FOLLOWED

(Deprecated) Public Service Account is followed. For the `ConversationType_PUBLIC_SERVICE` conversation type.

29204

RC_PUBLICSERVICE_DEFUNFOLLOWED

(Deprecated) Public Service Account is unfollowed by default. For the `ConversationType_PUBLIC_SERVICE` conversation type.

29205

RC_PUBLICSERVICE_UNFOLLOWED

(Deprecated) Public Service Account is unfollowed. For the `ConversationType_PUBLIC_SERVICE` conversation type.

29206

RC_PUBLICSERVICE_UNFOLLOW

(Deprecated) Public Service Account is not followed. For the `ConversationType_PUBLIC_SERVICE` conversation type.

30001

RC_NET_CHANNEL_INVALID

The current connection has been terminated.

Troubleshooting:

1. Check the error code returned by Connection Status Monitoring to identify the issue.
2. Switch to a stable network and reconnect. If the issue persists, submit a Support Ticket.

30002

RC_NET_UNAVAILABLE

The current connection is unavailable.

Troubleshooting:

1. Ensure the connection is successful before making other API calls.
2. Check the error code returned by Connection Status Monitoring.
3. If the issue persists, submit a Support Ticket.

30003

RC_MSG_RESP_TIMEOUT

The client sent a message request, but the RC server timed out.

Troubleshooting: Retry later or switch to a stable network. If the issue persists, submit a Support Ticket with details like App key, user ID, and issue time.

30004

RC_HTTP_SEND_FAIL

HTTP Request failed during Navigation Operation.

Troubleshooting: Retry later or switch to a stable network. If the issue persists, submit a Support Ticket with details like App key, user ID, and issue time.

30005

RC_HTTP_REQ_TIMEOUT

Failed to connect to the Navigation Address.

Troubleshooting: Retry later or switch to a stable network. If the issue persists, submit a Support Ticket with details like App key, user ID, and issue time.

30006

RC_HTTP_RECV_FAIL

HTTP Request reception failed during Navigation Operation.

Troubleshooting: Retry later or switch to a stable network. If the issue persists, submit a Support Ticket with details like App key, user ID, and issue time.

30007

RC_NAVI_RESOURCE_ERROR

Navigation returned an abnormal result.

Troubleshooting: Retry later or switch to a stable network. If the issue persists, submit a Support Ticket with details like App key, user ID, and issue time.

30008

RC_NODE_NOT_FOUND

Navigation HTTP returned incorrect data format.

Troubleshooting: Retry later or switch to a stable network. If the issue persists, submit a Support Ticket with details like App key, user ID, and issue time.

30009

RC_DOMAIN_NOT_RESOLVE

No valid IP Address found after parsing Navigation Data.

Troubleshooting: Submit a Support Ticket with details like App key, user ID, and issue time.

30010

RC_SOCKET_NOT_CREATED

Failed to create a connection.

Troubleshooting: Retry later or switch to a stable network. If the issue persists, submit a Support Ticket with details like App key, user ID, and issue time.

30011

RC_SOCKET_DISCONNECTED

Connection disconnected.

Troubleshooting: Retry later or switch to a stable network. If the issue persists, submit a Support Ticket with details like App key, user ID, and issue time.

30012

RC_PING_SEND_FAIL

PING failed.

Troubleshooting: Usually caused by network issues. The SDK will attempt to reconnect until the network is restored.

30013

RC_PONG_RECV_FAIL

PING timed out.

Troubleshooting: Usually caused by network issues. The SDK will attempt to reconnect until the network is restored.

30014

RC_MSG_SEND_FAIL

Signaling Transmission failed.

Troubleshooting:

1. If this occurs during connection, switch to a different network.
2. If this occurs while sending media messages, check for upload failures or empty remote addresses.
3. If the issue persists, submit a Support Ticket with details like App key, user ID, and issue time.

30015

RC_CONN_OVERFREQUENCY

Connection frequency is too high.

Troubleshooting: Retry later. If the issue persists, submit a Support Ticket with details like App key, user ID, and issue time.

30016

RC_MSG_SIZE_OUT_OF_LIMIT

Message Size exceeds the limit. The Message Body (content serialized into JSON Format) must not exceed 128k bytes.

Troubleshooting:

1. Ensure the Thumbnail does not exceed 80 KB when sending image messages.
2. Ensure the content length of the RCMessage object does not exceed 128k.

30019

RC_NETWORK_IS_DOWN_OR_UNREACHABLE

Network Connection is unavailable.

Troubleshooting: Retry later or switch to a stable network. If the issue persists, submit a Support Ticket with details like App key, user ID, and issue time.

30021

RC_TCP_DISCONNECTED_NO_RMTP

TCP Connection succeeded, but RMTP Connection failed.

Troubleshooting: Retry later or switch to a stable network. If the issue persists, submit a Support Ticket with details like App key, user ID, and issue time.

31000

RC_CONN_ACK_TIMEOUT

Connection ACK timed out.

Troubleshooting: Submit a Support Ticket with details like App key, user ID, and issue time.

31001

RC_CONN_PROTO_VERSION_ERROR

Signaling Version error.

Troubleshooting: Submit a Support Ticket with details like App key, user ID, and issue time.

31002

RC_CONN_ID_REJECT

Incorrect format in the Client Info Field. Correct format is Platform Type-Device Information-SDK Version. Device Information is Phone Type|Phone Model|Network Type, 4G/WIFI|Carrier Identifier, Mobile/Telecom/Unicom.

Troubleshooting:

1. Correct format: Platform Type-Device Information-SDK Version. Device Information: Phone Type|Phone Model|Network Type, 4G/WIFI|Carrier Identifier, Mobile/Telecom/Unicom.
2. Submit a Support Ticket with details like App key, user ID, and issue time.

31003

RC_CONN_SERVER_UNAVAILABLE

Connection service is not enabled. Check if the Mini Program or Desktop Version service is enabled in the backend.

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

31004

RC_CONN_USER_OR_PASSWD_ERROR

Invalid Token; AppKey and Token do not match; Token expired.

Troubleshooting:

1. Ensure the appkey passed during app initialization matches the appkey used to obtain the token on the server.
2. For overseas data centers, confirm if the Region Code is set.
3. Check the token validity period in RC Console > App Configuration > Basic Info.
4. Obtain a new token for verification.

31005

RC_CONN_NOT_AUTHRORIZED

App verification failed (App verification is enabled but failed).

Troubleshooting: Submit a Support Ticket with details like App key and Package Name Information.

31006

RC_CONN_REDIRECTED

Connection redirected.

Troubleshooting: The SDK will attempt to reconnect and request navigation for CMP Address. If the issue persists, submit a Support Ticket with details like App key and Package Name Information.

31007

RC_CONN_PACKAGE_NAME_INVALID

Package name does not match the backend registration information.

Troubleshooting: Submit a Support Ticket with details like App key and Package Name Information.

31008

RC_CONN_APP_BLOCKED_OR_DELETED

AppKey is blocked or deleted.

Troubleshooting: Apply for recovery in RC Console > App Management.

31009

RC_CONN_USER_BLOCKED

Connection failed, User Blocked (returned when the client actively fails to connect).

Troubleshooting: Unblock User as needed.

31010

RC_DISCONN_KICK

User was kicked offline.

Troubleshooting:

1. By default, the same user account can be online on one device at a time across mobile, web, desktop, and mini program.
2. To log in on multiple devices of the same type, follow the Multiple Devices Online Simultaneously documentation.

31011

RC_DISCONN_USER_BLOCKED

User Blocked, causing IM connection to be passively disconnected.

Troubleshooting: Unblock User as needed.

31011

RC_DISCONN_USER_BLOCKED

The user is blocked, causing the IM connection to be passively disconnected.

Troubleshooting suggestions: The business layer should unblock the user as needed here.

31012

RC_CONN_ENCRYPT_AUTH_FAILURE

Connection encryption authentication failed.

Troubleshooting suggestions: Submit a ticket here to contact us, and include necessary information such as App key and package information.

31020

RC_CONN_TOKEN_EXPIRE

The token has expired.

Troubleshooting suggestions:

1. Check the token validity period in the RC Console > application configuration > basic information here.

31023

RC_CONN_OTHER_DEVICE_LOGIN

After enabling the switch to prevent kicking online clients offline, this error code indicates that a client of the same type is already online.

Troubleshooting suggestions: For details, refer to the document on reconnection mechanism and reconnection and kick here.

31024

CONCURRENT_LIMIT_ERROR

The total number of connections exceeds the concurrency limit set by the service (exclusive to private cloud).

Troubleshooting suggestions:

1. The connection limit can be viewed in the private cloud management backend > application configuration > application information.
2. This limit applies to the Appkey. If the user needs to modify the limit, a new identifier must be used.

31025

RC_CONN_CLUSTER_ERROR

The client connected to the wrong environment, causing the connection to be rejected; for example, using a development environment Appkey to connect to the production environment.

Troubleshooting suggestions: Submit a ticket here to contact us, and include necessary information such as App key and package information.

31026

RC_CONN_APP_AUTH_FAILED

After enabling the AppServer joint authentication feature, authentication to the AppServer failed.

Troubleshooting suggestions: Submit a ticket here to contact us, and include necessary information such as App key and package information.

31027

RC_CONN_DISPOSABLE_TOKEN_USED

The token has already been used and cannot be used for connection. A disposable token can only be used once, and subsequent attempts will result in this error.

Troubleshooting suggestions: Submit a ticket here to contact us, and include necessary information such as App key and package information.

31029

RC_CONN_USER_ABANDON

The user has undergone account closure.

Troubleshooting suggestions:

1. Check if the user has been deactivated. For details, refer to the document on query deactivated users here.
2. If the user has been deactivated, reactivate user ID as needed. For details, refer to the document on reactivate user ID here.

31030

RC_CONN_APP_LICENSE_EXPIRED

The private cloud license check failed; the App license has expired.

Troubleshooting suggestions:

1. Check if the identifier and license information in the private cloud management backend have expired.
2. If they have expired, contact the business contact.
3. If you are using the HarmonyOS SDK, contact the business contact.

32001

RC_QUERY_ACK_NO_DATA

Internal error in the protocol layer; data error occurred during query, upload, or download.

Troubleshooting suggestions: Submit a ticket here to contact us, and include necessary information such as App key, user ID, and the time the issue occurred.

32002

RC_MSG_DATA_INCOMPLETE

Internal error in the protocol layer.

Troubleshooting suggestions: Submit a ticket here to contact us, and include necessary information such as App key, user ID, and the time the issue occurred.

32011

RC_UDP_DISCONNECTED

The server actively disconnected the connection (only triggered under the quic protocol).

Troubleshooting suggestions: Submit a ticket here to contact us, and include necessary information such as App key, user ID, and the time the issue occurred.

32054

RC_CONNECTION_RESET_BY_PEER

The link was interrupted by the server, possibly because the carrier deemed the link illegal or invalid and directly disconnected it. After this error code appears, the SDK will automatically trigger a reconnect, and the App does not need to handle it.

Troubleshooting suggestions: Try again later or after switching to a stable network. If the issue persists, submit a ticket here to contact us, and include necessary information such as App key, user ID, and the time the issue occurred.

32061

RC_CONN_REFUSED

The connection was refused.

Troubleshooting suggestions: Try again later or after switching to a stable network. If the issue persists, submit a ticket here to contact us, and include necessary information such as App key, user ID, and the time the issue occurred.

33000

BIZ_SAVE_MESSAGE_ERROR

Failed to save the message to the local database. When sending or inserting a message, the message needs to be stored in the local database. If the storage fails, this error code will be returned.

Troubleshooting suggestions:

1. Check if the user device has sufficient memory.
2. Ensure that the connect connection was successful.
3. If the connection is normal and there is sufficient memory, and the issue persists, submit a ticket here to contact us, and include necessary information such as App key, user ID, and the time the issue occurred.

33001

BIZ_ERROR_CLIENT_NOT_INIT

The protocol stack was not initialized. The reason may be the SDK initialize interface was not called or the SDK’s so library was not loaded properly.

Troubleshooting suggestions: Check if the initialize interface was executed. The SDK’s so library was not loaded properly.

33002

BIZ_ERROR_DATABASE_ERROR

Database error.

Troubleshooting suggestions:

1. Check if the initialize interface was executed and if the connect connection was successful.
2. If the issue persists, submit a ticket here to contact us, and include necessary information such as App key, user ID, and the time the issue occurred.

33003

PARAMETER_ERROR

The parameter passed when calling the developer interface is incorrect.

Troubleshooting suggestions: Check if the parameter format complies with the relevant instructions in the interface comments.

33004

BIZ_ERROR_NO_CHANNEL

The channel is invalid.

Troubleshooting suggestions: Submit a ticket here to contact us, and include necessary information such as App key, user ID, and the time the issue occurred.

33006

BIZ_ERROR_CONNECTING

The connection is in progress, and calling connect again is refused.

Troubleshooting suggestions: Submit a ticket here to contact us, and include necessary information such as App key, user ID, and the time the issue occurred.

33007

MSG_ROAMING_SERVICE_UNAVAILABLE

The historical message cloud storage service is not enabled.

Troubleshooting suggestions:

1. Check if the historical message cloud storage service is enabled in the RC Console > application configuration > IM service > Chat pricing plans here.
2. If it has been enabled and was just enabled about 2 hours ago, try uninstalling and reinstalling the app (to update the navigation information).

33008

PROTOCOL_MESSAGE_INSERTED_ERROR

Failed to save the message to the local database.

Troubleshooting suggestions:

1. Check if the initialize interface was executed and if the connect connection was successful.
2. Check if the device has sufficient memory.
3. If the issue persists, submit a ticket here to contact us, and include necessary information such as App key, user ID, and the time the issue occurred.

33009

RC_CHATROOM_RESET

The chatroom has been recycled.

Troubleshooting suggestions: Confirm the chatroom information.

33010

DATABASE_ENCRYPT_FAILED

When upgrading the database from a decrypted version to an encrypted version, the first connection will trigger the encrypt migration. This is usually caused by insufficient disk space, and it can generally be automatically recovered after clearing space.

Troubleshooting suggestions:

1. When upgrading the database from an encrypted version to a decrypted version, the first connection will trigger the decrypt migration. This is usually caused by insufficient disk space, and it can generally be automatically recovered after clearing space.
2. If the issue persists, submit a ticket here to contact us, and include necessary information such as App key, user ID, and the time the issue occurred.

33011

DATABASE_DECRYPT_FAILED

When upgrading the database from an encrypted version to a decrypted version, the first connection will trigger the decrypt migration. This is usually caused by insufficient disk space, and it can generally be automatically recovered after clearing space.

Troubleshooting suggestions:

1. When upgrading the database from an encrypted version to a decrypted version, the first connection will trigger the decrypt migration. This is usually caused by insufficient disk space, and it can generally be automatically recovered after clearing space.
2. If the issue persists, submit a ticket here to contact us, and include necessary information such as App key, user ID, and the time the issue occurred.

33012

DATABASE_REMOVE_FAILED

Failed to delete the database. The only possible reason is that the connection has not been interrupted, and the database is still in use.

Troubleshooting suggestions: Check the current link and confirm that the connection is successful when this error code is called. If the issue persists, submit a ticket here to contact us, and include necessary information such as App key, user ID, and the time the issue occurred.

33100

RC_TAG_NOT_EXIST

The tag does not exist.

Troubleshooting suggestions:

1. Confirm if the tag exists by obtaining the tag list. For details, refer to the document here.
2. If it does not exist, create it as needed. For details, refer to the document here.

33101

RC_TAG_ALREADY_EXISTS

The tag already exists.

Troubleshooting suggestions: Confirm if the tag exists by obtaining the tag list. For details, refer to the document here.

33102

RC_TAG_INVALID_FOR_CONVERSATION

The tag is not in the conversation.

Troubleshooting suggestions: Confirm if the tag exists by obtaining all tags under the specified conversation. For details, refer to the document here.

34001

RC_CONNECTION_EXIST

Connection already exists.

Troubleshooting: The connection is already established. No need to reconnect.

34002

RC_SIGHT_MSG_DURATION_LIMIT_EXCEED

Short video duration exceeds the limit.

Troubleshooting: Ensure the short video duration is within 2 minutes.

34003

RC_GIF_MSG_SIZE_LIMIT_EXCEED

GIF message file size exceeds the limit.

Troubleshooting: Ensure the GIF file size is under 2MB.

34004

KV_STORE_NOT_SYNC

Chatroom status not fully synchronized.

Troubleshooting:

1. After joining a chatroom, local and server data may not sync immediately. Wait before retrieving.
2. Ensure the chatroom status is fully synchronized before calling the KV interface.

34005

RC_ENVIRONMENT_ERROR

Incorrect connection environment.

Troubleshooting:

1. This error applies to private cloud users. Public cloud users can ignore it.
2. Using a public cloud SDK in a private cloud environment triggers this error.
3. Private cloud SDKs include an enterprise identifier.
4. If unsure, contact your business representative.

34006

RC_CONNECT_TIMEOUT

Connection timeout.

Troubleshooting:

1. Check if the connection to RC is successful by monitoring the connection status.
2. Retry later or switch to a stable network. If the issue persists, submit a ticket with details like App key, user ID, and issue time.

34007

RC_PUBLIC_SERVICE_PROFILE_NOT_EXIST

The queried public service information does not exist.

Troubleshooting: Ensure the public service type and ID match.

34008

RC_MESSAGE_CANT_EXPAND

Message cannot be expanded.

Troubleshooting:

1. Ensure the canIncludeExpansion property is set to true before sending. Refer to Message Expansion.
2. Message expansion only supports single chat, group chat, and ultra group chat. Check the message type.

34009

RC_MESSAGE_EXPAND_FAIL

Message expansion failed.

Troubleshooting: Ensure the network is stable and the RC SDK is connected. Check the connection status here.

34010

RC_MSG_EXPANSION_SIZE_LIMIT_EXCEED

Message expansion size exceeds the limit.

Troubleshooting: Ensure the key length is under 32 characters, value length under 4096 characters, and the number of key-value pairs is under 300.

34011

RC_FILE_UPLOAD_FAILED

Media file upload failed.

Troubleshooting: Retry later or switch to a stable network. If the issue persists, submit a ticket with details like App key, user ID, and issue time.

34012

RC_CONVERSATION_TAG_INVALID_CONVERSATION_TYPE

The specified conversation type does not support tags.

Troubleshooting: Ensure the conversation type is single chat, group chat, or system conversation. Tags only support these types.

34013

RC_CONVERSATION_TAG_LIMIT_EXCEED

The number of conversations added/deleted in the tag exceeds the limit.

Troubleshooting: Ensure no more than 1000 conversations are added/deleted.

34014

RC_GROUP_READ_RECEIPT_VERSION_NOT_SUPPORT

Group read receipt version not supported.

Troubleshooting: Check if the interface matches the integrated SDK. Refer to Read Receipt for Global IM UIKit/IMLib or documentation for GlobalKit.

34015

RC_VIDEO_COMPRESS_FAILED

Video compression failed.

Troubleshooting: Check the video resource path and permissions. If the issue persists, submit a ticket with details like App key, user ID, and issue time.

34016

RC_USER_SETTING_DISABLED

User-level settings are not enabled.

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

34017

RC_MESSAGE_NULL_EXCEPTION

The message returned by the message interceptor is null.

Troubleshooting: Check the MessageInterceptor protocol methods for cases where the returned message is null.

34018

RC_MEDIA_EXCEPTION

Media file upload exception.

Troubleshooting: Ensure the media file exists and its size is not 0.

34019

RC_MEDIA_FILE_FORMAT_NOT_SUPPORTED

The uploaded media file format is not supported.

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

34020

RC_FILE_EXPIRED

The file has expired or been cleaned up.

Troubleshooting: Short video files are stored for 7 days, others for 6 months. If the issue persists, submit a ticket with details like App key, user ID, and issue time.

34021

RC_MESSAGE_NOT_REGISTERED

The message is not registered.

Troubleshooting:

1. For custom messages, register them first. Refer to Register Custom Message.
2. For SDK built-in messages, ensure the SDK is properly initialized and connected.

34022

RC_ULTRA_GROUP_NOT_SUPPORT

This interface does not support ultra group conversations.

Troubleshooting: Ensure the conversationType is ConversationType_ULTRAGROUP. Refer to the documentation.

34025

RC_MESSAGE_EXPAND_CONVERSATION_TYPE_NOT_MATCH

Message expansion failed due to mismatched conversation types.

Troubleshooting:

1. Ensure the message.conversationType is single chat, group chat, or ultra group chat.
2. Check the interface call: Single/group chat expansion interfaces are in RCCoreClient, while ultra group chat interfaces are in RCChannelClient.

34026

RC_NETWORK_THROWS_IOEXCEPTION

HTTP request throws an IO exception.

Troubleshooting: Retry later or switch to a stable network. If the issue persists, submit a ticket with details like App key, user ID, and issue time.

34027

RC_NETWORK_THROWS_SOCKET_TIMEOUT_EXCEPTION

HTTP request throws a SocketTimeoutException.

Troubleshooting: Retry later or switch to a stable network. If the issue persists, submit a ticket with details like App key, user ID, and issue time.

34100

RC_TRANSLATION_CODE_INVALID_AUTH_TOKEN

The authToken is not set or is empty.

Troubleshooting: Ensure the jwtToken parameter is not empty.

34101

RC_TRANSLATION_CODE_INVALID_TEXT

The text content to be translated is empty.

Troubleshooting: Ensure the text content parameter is not empty.

34102

RC_TRANSLATION_CODE_INVALID_TARGET_LANGUAGE

The target language is empty.

Troubleshooting: Ensure the target language parameter is not empty.

34103

RC_TRANSLATION_CODE_INVALID_SOURCE_LANGUAGE

The source language is empty.

Troubleshooting: Ensure the source language parameter is not empty.

34104

RC_TRANSLATION_CODE_INVALID_SERVER_URL

The translation server address is empty.

Troubleshooting:

1. Ensure the translation service is enabled for this appkey. Try reinstalling.
2. If the issue persists, submit a ticket with details like App key, user ID, and issue time.

34105

RC_TRANSLATION_CODE_INVALID_APP_KEY

The app key is empty.

Troubleshooting: Ensure the appkey parameter is not empty.

34106

RC_TRANSLATION_CODE_INVALID_DATA

Server data is invalid.

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

34129

RC_INVALID_PARAMETER_CONNECTION_OPTION_NULL

The connection option is empty.

Troubleshooting: Ensure the ConnectOption parameter is not empty.

34131

RC_INVALID_PARAMETER_SDK_VERSION

The SDK version parameter is incorrect.

Troubleshooting: Ensure the SDK version is at least 3 digits and an integer. Submit a ticket with the version number.

34200

RC_INVALID_PARAMETER_LANGUAGE

The language parameter is invalid.

Troubleshooting: Ensure the language parameter is not empty.

34201

RC_INVALID_PARAMETER_CONVERSATION_TYPE_NOT_SUPPORT

The interface does not support the passed conversation type.

Troubleshooting:

1. For custom messages, register them first. Refer to Register Custom Message.
2. For SDK built-in messages, ensure the SDK is properly initialized and connected.

34202

RC_INVALID_PARAMETER_TIMESTAMP

The timestamp parameter is invalid.

Troubleshooting:

1. Ensure the timestamp is not less than 0.
2. For getUltraGroupMessageCountByTimeRange or getMessageCountByTimeRange, ensure startTime is less than endTime.

34203

RC_INVALID_PARAMETER_MESSAGE_UID

The **messageUID** passed in the developer interface call is invalid.

Troubleshooting:

1. For interfaces that directly pass a messageUID string, ensure it’s not empty.
2. For interfaces that pass a Message object, check if message.messageUId is empty.

34204

RC_INVALID_PARAMETER_MESSAGE_ID

The **messageId** passed in the developer interface call is invalid or the corresponding **Message** cannot be found.

Troubleshooting:

1. For interfaces that directly pass a messageId string, ensure it’s greater than 0.
2. When calling setMessageSentStatus, ensure Message.SentStatus is not empty and messageId is greater than 0.
3. For interfaces that pass a Message object, check if message.messageId is greater than 0.

34205

RC_INVALID_PARAMETER_MESSAGE_CONTENT

The **Message** or **MessageContent** passed in the developer interface call is invalid.

Troubleshooting:

1. Check if the Message or MessageContent passed to the interface is empty.
2. Verify if the Message or MessageContent type passed is correct.

34206

RC_INVALID_PARAMETER_MESSAGE_LIST

The **messageList** passed in the developer interface call is invalid.

Troubleshooting:

1. Ensure the messageList is not empty and contains valid Message objects.
2. If calling deleteRemoteMessage, ensure the messageList contains no more than 100 items.
3. If calling a getBatch...... interface, ensure the messages or messageUIDs array is within the range [1, 20], and all messages have the same targetId and are from a supergroup conversation.

34207

RC_INVALID_PARAMETER_MEDIA_TYPE

The **mediaType** passed in the developer interface call is invalid.

Troubleshooting: When downloading remote resources, ensure the IRongCoreEnum.MediaType parameter is not empty.

34208

RC_INVALID_PARAMETER_REQUEST_URL

The **requestUrl** passed in the developer interface call is invalid.

Troubleshooting: When checking if a file supports resumable downloads, ensure the mediaUrl parameter is not empty.

34209

RC_INVALID_PARAMETER_CONVERSATION_TYPE

The **ConversationType** passed in the developer interface call is invalid.

Troubleshooting:

1. Ensure the conversationType attribute in the passed parameters is not empty.
2. Refer to the documentation to verify if the called method supports this conversation type.

34210

RC_INVALID_PARAMETER_TARGET_ID

The **targetId** passed in the developer interface call is invalid.

Troubleshooting: Ensure the targetId is not empty and its length is within the range (0, 64).

34211

RC_INVALID_PARAMETER_CHANNEL_ID

The **channelId** passed in the developer’s channel-related interface call is invalid.

Troubleshooting:

1. Ensure channelId is not null—use an empty string instead.
2. When calling supergroup conversation channel-related interfaces, ensure the channelId is a string type and its length is within [0, 20).
3. If calling searchMessagesForChannels, ensure the channelIds parameter meets the condition 0 < number of channels <= 50. If the channelId is invalid (e.g., null or length exceeds 20) or the number of channels doesn’t meet the condition, the errorBlock will return this error code.

34212

RC_INVALID_PARAMETER_TAG_ID

The **tagId** passed in the developer interface call is invalid.

Troubleshooting: Ensure the tag object is not empty, is a string type, and its length is within (0, 10).

34213

RC_INVALID_PARAMETER_TAG_NAME

The **tagName** passed in the developer interface call is invalid.

Troubleshooting: Ensure the tag name object is not empty, is a string type, and its length is within (0, 15).

34214

RC_INVALID_PARAMETER_USER_ID

The **userId** passed in the developer interface call is invalid.

Troubleshooting: Ensure the userId is not empty and its length does not exceed 64.

34215

RC_INVALID_PARAMETER_USERIDLIST

The **userIdList** passed in the developer interface call is invalid.

Troubleshooting: Ensure the userIdList is not empty, contains more than 0 objects, and each user ID is not empty and within the length range (0, 64).

34218

RC_INVALID_PARAMETER_OFFLINE_DURATION

The parameter passed in the **setOfflineMessageDuration** interface call is invalid.

Troubleshooting: Ensure the duration parameter is within the range [1, 7].

34219

RC_INVALID_PARAMETER_HISTORY_MESSAGE_OPTION_COUNT

The **HistoryMessageOption** passed in the developer interface call is invalid.

Troubleshooting: Ensure the count object value in the HistoryMessageOption parameter is greater than 0.

34220

RC_INVALID_PARAMETER_MESSAGE_EXPANSION

The **MessageExpansion** passed in the developer interface call is invalid.

Troubleshooting: If calling the update expansion interface, ensure the expansion object is not empty. It must be a HashMap type, the Map must have content, the key-value pairs in the expansion dictionary must be strings, and the key must be a combination of uppercase/lowercase letters, numbers, or special characters + = - _. Chinese characters are not supported.

34221

RC_INVALID_PARAMETER_ULTRA_GROUP_MESSAGE_EXPANSION_KEY_ARRAY

The **UltraGroupMessageExpansion keyArray** passed in the developer interface call is invalid.

Troubleshooting: When calling removeUltraGroupMessageExpansion, ensure the keyArray object is an ArrayList and is not empty.

34223

RC_INVALID_PARAMETER_NOT_MEDIA_MESSAGE

The Message.content passed in sendMediaMessage is not a Media Message.

Troubleshooting: Use sendMessage for regular messages and sendMediaMessage for Media Messages. If the message doesn’t inherit from MediaMessageContent, you can’t use sendMediaMessage. Verify with if (message.getContent() instanceof MediaMessageContent).

34224

RC_INVALID_PARAMETER_TIME_STRING

The Time (String) parameter is invalid.

Troubleshooting: Ensure the time object is a non-empty string.

34225

RC_INVALID_PARAMETER_CONVERSATION_IDENTIFIER

The RCConversationIdentifier parameter is invalid.

Troubleshooting: Check the time parameter. It can’t be empty.

34228

RC_INVALID_PARAMETER_NOTIFICATION_LEVEL

The PushNotificationLevel is invalid.

Troubleshooting: Check the level parameter. It can’t be empty, and the PushNotificationLevel enum value can’t be NONE.

34229

RC_INVALID_PARAMETER_MESSAGE_ARRAY

The messageIds parameter is empty or the array length is 0.

Troubleshooting: Ensure the messageIds parameter is valid. It can’t be empty, and the array length can’t be 0.

34230

RC_INVALID_PARAMETER_RECEIVED_STATUS

The ReceivedStatus parameter is null.

Troubleshooting: Check the ReceivedStatus parameter. It can’t be empty.

34231

INVALID_PARAMETER_CHANNEL_TYPE

The ultra group Channel Type is invalid.

Troubleshooting: Check the channelType parameter. It can’t be empty.

34232

INVALID_PARAMETER_COUNT

The count parameter is invalid.

Troubleshooting: Review the interface method documentation for the count parameter. The value must comply with the specified limits.

34233

INVALID_PARAMETER_SEND_TIME

The sendTime parameter is invalid.

Troubleshooting: Ensure the sendTime object is greater than or equal to 0.

34234

RC_INVALID_PARAMETER_LOCAL_PATH

The local path address doesn’t exist.

Troubleshooting: Check the file path. Ensure the file exists. For video messages, confirm if the video message type is registered. For UI-less integration, the business side must actively register the video message type.

34235

RC_INVALID_PARAMETER_MEDIA_URL

The mediaUrl address is empty.

Troubleshooting: Check if the mediaUrl value is empty.

34236

RC_INVALID_PARAMETER_UNIQUE_ID

The uniqueId is empty or an empty string.

Troubleshooting: Check if the uniqueId is empty or an empty string.

34237

RC_INVALID_PARAMETER_MSG_TAG

The MessageTag is empty, or MessageTag.value() is empty or an empty string.

Troubleshooting: Check the MessageTag parameter. It can’t be empty, and MessageTag.value() can’t be empty.

34238

INVALID_PARAMETER_PROXY

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

Troubleshooting: The proxy object passed to the testProxy interface must be non-empty. The host proxy address can’t be empty, and the port must be greater than 0.

34239

INVALID_PARAMETER_TEST_HOST

The proxy test service is invalid.

Troubleshooting: Check if the testHost object is non-empty and has a length greater than 0.

34240

INVALID_CONNECT_TEST_HOST_FAILED

Unable to connect when calling the testProxy interface.

Troubleshooting:

1. Confirm if the address is correct, valid, and the network connection is normal.
2. Provide the AppKey, SDK Version, User ID, and issue time. We’ll check the logs for clues.

34241

RC_INVALID_PARAMETER_ULTRA_GROUP_MESSAGE_OBJECT_NAME

Called recallUltraGroupMessage with an unsupported message type.

Troubleshooting: Check if the message type passed to the recallUltraGroupMessage interface is RecallNotificationMessage. This interface doesn’t support recalling RecallNotificationMessage type messages.

34242

RC_INVALID_PARAMETER_CONVERSATIONS

The conversations parameter is null or the conversations array contains null objects.

Troubleshooting: Check the conversations object. This parameter can’t be empty.

34243

RC_INVALID_PARAMETER_MESSAGE

The message parameter is empty.

Troubleshooting: Check if the message object is empty.

34244

RC_INVALID_PARAMETER_SENT_STATUS

The Message.SentStatus parameter is null.

Troubleshooting: Check the Message.SentStatus parameter. It can’t be empty and can’t be in the Message.SentStatus.SENDING state.

34245

RC_CONN_PROXY_UNAVAILABLE

The Proxy Address is unavailable.

Troubleshooting: Submit a ticket with the necessary information, including the user’s AppKey, User ID, and time. Our technical team will analyze the client logs. Alternatively, provide the local adb Log for analysis.

34246

UPDATE_MESSAGE_RECEIPT_STATUS_ERROR

Error updating the message read status.

Troubleshooting: Submit a ticket with the necessary information, including the user’s AppKey, User ID, and time. Our technical team will analyze the client logs. Alternatively, provide the local adb Log for analysis.

34247

CLEAR_MESSAGE_UNREAD_STATUS_ERROR

Error clearing the message unread status.

Troubleshooting: Check if the settings for clearing the message unread status are correct. If everything is correct, submit a ticket with the necessary information, including the user’s AppKey, User ID, and time. Our technical team will analyze the client logs. Alternatively, provide the local adb Log for analysis.

34248

SET_MESSAGE_READ_TIME_ERROR

Error setting the message read time.

Troubleshooting: Check if the message read time is set correctly. If everything is correct, submit a ticket with the necessary information, including the user’s AppKey, User ID, and time. Our technical team will analyze the client logs. Alternatively, provide the local adb Log for analysis.

34251

FILE_SAVED_FAILED

File Save Failed.

Troubleshooting:

1. Get the parent directory of the given File object. Check if the parent directory or file doesn’t exist. Also, check if the device has run out of storage space.
2. Submit a ticket with the necessary information, including the user’s AppKey, User ID, and time. Our technical team will analyze the client logs. Alternatively, provide the local adb Log for analysis.

34257

INVALID_APP_KEY

The App Key is invalid.

Troubleshooting: Confirm if the init interface was called to initialize the SDK before calling the IM connection interface, and ensure the App Key parameter is valid.

34258

INVALID_PARAMETER_JOIN_MODE

The JoinMode parameter is invalid.

Troubleshooting: Check if the JoinMode parameter is valid. This parameter can’t be empty.

34259

INVALID_PARAMETER_RTCROOMID

The rtcRoomID parameter is invalid.

Troubleshooting: Check if the RTCRoomId passed to the bindChatRoomWithRTCRoom interface is a string object and non-empty.

34260

INVALID_PARAMETER_KEY

The key parameter is invalid.

Troubleshooting: Check if the key parameter in the chatroom KV-related interfaces (set, delete) meets the requirements: it must be a string type, with a length between (0, 128], and consist of uppercase and lowercase letters, numbers, and special symbols + = - _ ( "^[A-Za-z0-9+_=-]+$").

34261

INVALID_PARAMETER_KEYS

The keys parameter is invalid.

Troubleshooting: Confirm if the chatroom KV (chatroom attribute collection) and message extension KV are valid. The collection can’t be empty.

34262

INVALID_PARAMETER_VALUE

The value parameter is invalid.

Troubleshooting: Confirm if the value parameter is valid. For chatroom KV, the value parameter can’t be empty and must not exceed 1024 * 4 in size.

34263

INVALID_PARAMETER_ENTRIES

The entries parameter is invalid.

Troubleshooting: Check the entries parameter. This Map collection can’t be empty.

34264

INVALID_PARAMETER_NOTIFICATION_EXTRA

The notificationExtra parameter is invalid.

Troubleshooting: Check the notificationExtra parameter. It can’t be empty and must not exceed 1024 * 2 in length.

34265

INVALID_PARAMETER_CHATROOM_MEMBER_ORDER

The ChatRoomMemberOrder parameter is invalid.

Troubleshooting: Check the ChatRoomMemberOrder parameter. It can’t be empty.

34266

INVALID_PARAMETER_TIMESTAMP_ORDER

The TimestampOrder parameter is invalid.

Troubleshooting: Check the TimestampOrder parameter. It can’t be empty.

34267

INVALID_PARAMETER_MESSAGE_DIRECTION

The MessageDirection parameter is invalid.

Troubleshooting: Check the MessageDirection parameter. It can’t be empty.

34268

INVALID_PARAMETER_STATUS

The status parameter is invalid.

Troubleshooting: Check the status parameter for sending ultra group input status. It can’t be empty.

34269

INVALID_PARAMETER_TITLE

The title parameter is invalid.

Troubleshooting: Check if the title parameter is valid. It can’t be empty.

34270

INVALID_PARAMETER_PORTRAIT

The portrait parameter is invalid.

Troubleshooting: Confirm if the avatar information is empty. When updating conversation information, the avatar can’t be empty.

34271

INVALID_PARAMETER_MESSAGE_OBJECT_NAME

The objectName parameter is invalid.

Troubleshooting: objectName is the message type identifier. When calling methods that require objectName, ensure this parameter exists and is not empty.

34272

INVALID_PARAMETER_BEFORE

The before parameter is invalid.

Troubleshooting: Confirm the before parameter. It must be greater than or equal to 0.

34273

INVALID_PARAMETER_AFTER

The after parameter is invalid.

Troubleshooting: Confirm the after parameter. It must be greater than or equal to 0.

34274

INVALID_PARAMETER_KEYWORD

The keyword parameter is invalid.

Troubleshooting: keyword is the search keyword. Check if it meets the requirements: it can’t be empty and must not exceed 1000 in length.

34275

INVALID_PARAMETER_MESSAGE_OBJECT_NAME_LIST

The objectName list parameter is invalid.

Troubleshooting: objectName is the message type identifier. When calling methods that require an objectName list, ensure this parameter exists and is not empty.

34276

INVALID_PARAMETER_OFFSET

The offset parameter is invalid.

Troubleshooting: Confirm the offset parameter. It must be greater than or equal to 0.

34277

INVALID_PARAMETER_START_TIME

The start time parameter is invalid.

Troubleshooting: Confirm the start time parameter. It must be greater than or equal to 0.

34223

RC_INVALID_PARAMETER_NOT_MEDIA_MESSAGE

The {Message.content} passed in sendMediaMessage is not a media message.

Troubleshooting: Use sendMessage for regular messages and sendMediaMessage for media messages. Ensure the message inherits from MediaMessageContent before calling sendMediaMessage. Verify with if (message.getContent() instanceof MediaMessageContent).

34224

RC_INVALID_PARAMETER_TIME_STRING

Invalid time string parameter passed by the developer.

Troubleshooting: Ensure the time parameter is a non-empty string.

34225

RC_INVALID_PARAMETER_CONVERSATION_IDENTIFIER

Invalid {RCConversationIdentifier} parameter.

Troubleshooting: Verify the time parameter is valid and not empty.

34228

RC_INVALID_PARAMETER_NOTIFICATION_LEVEL

Invalid {PushNotificationLevel}.

Troubleshooting: Ensure the level parameter is not empty and not set to NONE.

34229

RC_INVALID_PARAMETER_MESSAGE_ARRAY

The {messageIds} parameter passed is empty or has a length of 0.

Troubleshooting: Verify the {messageIds} array is not empty and has a valid length.

34230

RC_INVALID_PARAMETER_RECEIVED_STATUS

The {ReceivedStatus} parameter passed is null.

Troubleshooting: Ensure the {ReceivedStatus} parameter is not empty.

34231

INVALID_PARAMETER_CHANNEL_TYPE

Invalid {channelType} for the supergroup channel.

Troubleshooting: Verify the {channelType} parameter is not empty.

34232

INVALID_PARAMETER_COUNT

Invalid {count} parameter passed by the developer.

Troubleshooting: Check the {count} parameter meets the required limits.

34233

INVALID_PARAMETER_SEND_TIME

Invalid {sendTime} parameter passed by the developer.

Troubleshooting: Ensure the {sendTime} parameter is ≥ 0.

34234

RC_INVALID_PARAMETER_LOCAL_PATH

The local path passed does not exist.

Troubleshooting: Verify the file path exists. For short video messages, ensure the message type is registered.

34235

RC_INVALID_PARAMETER_MEDIA_URL

The {mediaUrl} parameter passed is empty.

Troubleshooting: Ensure the {mediaUrl} parameter is not empty.

34236

RC_INVALID_PARAMETER_UNIQUE_ID

The {uniqueId} parameter passed is empty or null.

Troubleshooting: Verify the {uniqueId} parameter is not empty.

34237

RC_INVALID_PARAMETER_MSG_TAG

The {MessageTag} parameter passed is empty or null.

Troubleshooting: Ensure the {MessageTag} parameter and its value are not empty.

34238

INVALID_PARAMETER_PROXY

Invalid proxy configuration. {RongIMProxy} is empty or invalid.

Troubleshooting: Ensure the proxy object passed to testProxy is not empty, with a valid host and port > 0.

34239

INVALID_PARAMETER_TEST_HOST

Invalid test host passed to `testProxy`.

Troubleshooting: Verify the {testHost} parameter is not empty and has a valid length.

34240

INVALID_CONNECT_TEST_HOST_FAILED

Unable to connect to the test host passed to `testProxy`.

Troubleshooting:

1. Confirm the address is correct, valid, and the network is functioning.
2. Provide the AppKey, SDK version, user ID, and timestamp for log analysis.

34241

RC_INVALID_PARAMETER_ULTRA_GROUP_MESSAGE_OBJECT_NAME

Unsupported message type passed to `recallUltraGroupMessage`.

Troubleshooting: Ensure the message type is {RecallNotificationMessage}. This method does not support recalling {RecallNotificationMessage} types.

34242

RC_INVALID_PARAMETER_CONVERSATIONS

The {conversations} parameter passed is null or contains null objects.

Troubleshooting: Verify the {conversations} array is not empty.

34243

RC_INVALID_PARAMETER_MESSAGE

The {message} parameter passed is empty.

Troubleshooting: Ensure the {message} parameter is not empty.

34244

RC_INVALID_PARAMETER_SENT_STATUS

The {Message.SentStatus} parameter passed is null.

Troubleshooting: Verify the {Message.SentStatus} parameter is not empty and not set to SENDING.

34245

RC_CONN_PROXY_UNAVAILABLE

The configured proxy address is unavailable.

Troubleshooting: Submit a ticket with the AppKey, user ID, and timestamp for log analysis.

34246

UPDATE_MESSAGE_RECEIPT_STATUS_ERROR

Error updating message read status.

Troubleshooting: Submit a ticket with the AppKey, user ID, and timestamp for log analysis.

34247

CLEAR_MESSAGE_UNREAD_STATUS_ERROR

Error clearing message unread status.

Troubleshooting: Verify the unread status settings. If correct, submit a ticket with the AppKey, user ID, and timestamp for log analysis.

34248

SET_MESSAGE_READ_TIME_ERROR

Error setting message read time.

Troubleshooting: Verify the read time settings. If correct, submit a ticket with the AppKey, user ID, and timestamp for log analysis.

34251

FILE_SAVED_FAILED

File save failed.

Troubleshooting:

1. Check the parent directory exists and the device has sufficient storage.
2. Submit a ticket with the AppKey, user ID, and timestamp for log analysis.

34257

INVALID_APP_KEY

Invalid App Key.

Troubleshooting: Ensure the SDK is initialized with a valid App Key before connecting.

34258

INVALID_PARAMETER_JOIN_MODE

Invalid {JoinMode} parameter.

Troubleshooting: Verify the {JoinMode} parameter is not empty.

34259

INVALID_PARAMETER_RTCROOMID

Invalid {rtcRoomID} parameter.

Troubleshooting: Ensure the {rtcRoomID} passed to bindChatRoomWithRTCRoom is a non-empty string.

34260

INVALID_PARAMETER_KEY

Invalid {key} parameter.

Troubleshooting: Verify the {key} parameter is a string with a length between 1 and 128, using alphanumeric and specific special characters.

34261

INVALID_PARAMETER_KEYS

Invalid {keys} parameter.

Troubleshooting: Ensure the {keys} array is not empty.

34262

INVALID_PARAMETER_VALUE

Invalid {value} parameter.

Troubleshooting: Verify the {value} parameter is not empty and does not exceed 4096 bytes.

34263

INVALID_PARAMETER_ENTRIES

Invalid {entries} parameter.

Troubleshooting: Ensure the {entries} map is not empty.

34264

INVALID_PARAMETER_NOTIFICATION_EXTRA

Invalid {notificationExtra} parameter.

Troubleshooting: Verify the {notificationExtra} parameter is not empty and does not exceed 2048 bytes.

34265

INVALID_PARAMETER_CHATROOM_MEMBER_ORDER

Invalid {ChatRoomMemberOrder} parameter.

Troubleshooting: Ensure the {ChatRoomMemberOrder} parameter is not empty.

34266

INVALID_PARAMETER_TIMESTAMP_ORDER

Invalid {TimestampOrder} parameter.

Troubleshooting: Verify the {TimestampOrder} parameter is not empty.

34267

INVALID_PARAMETER_MESSAGE_DIRECTION

Invalid {MessageDirection} parameter.

Troubleshooting: Ensure the {MessageDirection} parameter is not empty.

34268

INVALID_PARAMETER_STATUS

Invalid {status} parameter.

Troubleshooting: Verify the {status} parameter is not empty.

34269

INVALID_PARAMETER_TITLE

Invalid {title} parameter.

Troubleshooting: Ensure the {title} parameter is not empty.

34270

INVALID_PARAMETER_PORTRAIT

Invalid {portrait} parameter.

Troubleshooting: Verify the {portrait} parameter is not empty.

34271

INVALID_PARAMETER_MESSAGE_OBJECT_NAME

Invalid {objectName} parameter.

Troubleshooting: Ensure the {objectName} parameter is not empty.

34272

INVALID_PARAMETER_BEFORE

Invalid {before} parameter.

Troubleshooting: Verify the {before} parameter is ≥ 0.

34273

INVALID_PARAMETER_AFTER

Invalid {after} parameter.

Troubleshooting: Ensure the {after} parameter is ≥ 0.

34274

INVALID_PARAMETER_KEYWORD

Invalid {keyword} parameter.

Troubleshooting: Verify the {keyword} parameter is not empty and does not exceed 1000 characters.

34275

INVALID_PARAMETER_MESSAGE_OBJECT_NAME_LIST

Invalid {objectName} list.

Troubleshooting: Ensure the {objectName} list is not empty.

34276

INVALID_PARAMETER_OFFSET

Invalid {offset} parameter.

Troubleshooting: Verify the {offset} parameter is ≥ 0.

34277

INVALID_PARAMETER_START_TIME

Invalid {startTime} parameter.

Troubleshooting: Ensure the {startTime} parameter is ≥ 0 and < {endTime}.

34278

INVALID_PARAMETER_END_TIME

Invalid {endTime} parameter.

Troubleshooting: Verify the {endTime} parameter is ≥ 0.

34279

INVALID_PARAMETER_LIMIT

Invalid {limit} parameter.

Troubleshooting: Ensure the {limit} parameter is > 0.

34280

INVALID_MESSAGE_DIRECTION

MessageDirection error.

Troubleshooting: Ensure the message direction is "send". Use getGroupMessageDeliverList to validate this field. Only messages with a UID in the local database and a direction of {@link Message.MessageDirection#SEND} that have been received by the recipient are queried.

34281

INVALID_MESSAGE_SENT_STATUS

SentStatus error.

Troubleshooting:

1. For one-to-one chats, only messages with a status of RECEIVED or READ can retrieve delivery time.
2. For group chats, only messages with a status of SENT, RECEIVED, or READ can use group message delivery methods.

34282

INVALID_PARAMETER_TARGETID_LIST

Invalid {targetId} list.

Troubleshooting: Verify the {targetId} list is not empty and does not exceed 20 items.

34283

INVALID_PARAMETER_SPAN_MINUTES

Invalid {spanMinutes} parameter.

Troubleshooting: Ensure the interval between start and end times for Do Not Disturb is > 0 and ≤ 1440.

34284

INVALID_PARAMETER_CONVERSATION_TYPE_LIST

Invalid {ConversationType} list.

Troubleshooting: Verify the {ConversationType} list is not empty and does not exceed 300 items.

34285

MESSAGE_HANDLER_INVALID

MessageHandler invalid.

Troubleshooting: The message is missing a {MessageHandler}. When customizing messages, configure the {MessageHandler} as in ImageMessage. If this occurs with short video messages, ensure the message type is registered.

34287

INVALID_PARAMETER_CONVERSATION_IDENTIFIER_LIST

Invalid {ConversationIdentifier} array passed by the developer.

Troubleshooting: Verify the {ConversationIdentifier} array is not empty, has a length between 1 and 20, and does not contain null or invalid objects.

34288

INVALID_PARAMETER_CLEAR_MESSAGE_OPTION_LIST

Invalid {ClearMessageOption} array passed by the developer.

Troubleshooting: Ensure the {ClearMessageOption} array is not empty, has a length between 1 and 20, and does not contain null or invalid objects.

34289

INVALID_PARAMETER_START_MESSAGE_UID

Invalid {startMessageUID} parameter.

Troubleshooting: Verify the {startMessageUID} parameter is not empty and does not exceed 64 characters.

34290

INVALID_PARAMETER_END_MESSAGE_UID

Invalid {endMessageUID} parameter.

Troubleshooting: Ensure the {endMessageUID} parameter is not empty and does not exceed 64 characters.

34296

RC_DIRECTIONAL_MESSAGE_INVALID_CONVERSATION_TYPE

Unsupported {ConversationType} passed when sending a {directionalMessage}.

Troubleshooting: Ensure the {ConversationType} is one of {GROUP}, {ULTRA_GROUP}, {DISCUSSION}, or {RTC_ROOM}.

34300

RC_REQUEST_INTERCEPTOR_NULL_EXCEPTION

The {multimediaUploadDownloadInterceptor} returned a null {HttpURLConnection}.

Troubleshooting: Ensure the {HttpURLConnection} returned in setHttpDownloadInterceptor is not null.

34306

INVALID_PARAMETER_SUBSCRIBE_TYPE

Invalid {SubscribeType} passed for the subscription event.

Troubleshooting: Verify the {SubscribeType} passed in {SubscribeEventRequest} and SubscribeEventRequest.getSubscribeType() is not null.

34307

INVALID_PARAMETER_SUBSCRIBE_EXPIRY

Invalid {subscribeExpiry} passed for the subscription event [60s ~ 2592000s].

Troubleshooting: Ensure the {subscribeExpiry} is > 60s and < 2592000s.

34308

INVALID_PARAMETER_SUBSCRIBE_PUBLISHER_USERIDS

Invalid or empty {subscribePublisherUserIds} list passed for the subscription event.

Troubleshooting: Verify the {subscribePublisherUserIds} list is not empty and each user ID does not exceed 64 characters.

34309

INVALID_PARAMETER_SUBSCRIBE_PAGESIZE

Invalid {pageSize} passed for the subscription event.

Troubleshooting: Ensure the {pageSize} parameter is between 1 and 200.

34312

INVALID_PARAMETER_USER_PROFILE

Invalid {userProfile} parameter.

Troubleshooting: The {userProfile} entity passed when updating user information is null. Check the parameter.

34313

INVALID_PARAMETER_USER_PROFILE_VISIBILITY

Invalid {userProfileVisibility} parameter.

Troubleshooting: The {userProfileVisibility} parameter passed when updating user information permissions is null. Check the parameter.

34315

RC_DB_UPGRADE_FAILED

Database upgrade failed.

Troubleshooting: Submit a ticket with the AppKey, user ID, and timestamp for analysis.

34316

INVALID_PARAMETER_CHATROOM_RECEIVE_MESSAGE_CONFIG

Invalid {ChatRoomReceiveMessageConfig} passed by the developer.

Troubleshooting: Ensure the {ChatRoomReceiveMessageConfig} parameter is not null.

34317

RC_EXCCED_CHATROOM_RECEIVE_MESSAGE_CONFIG_SIZE

Exceeded the limit for setting or retrieving chatroom message levels. The maximum is 100.

Troubleshooting: Verify the {ChatRoomReceiveMessageConfig} array does not exceed 100 items.

34318

INVALID_PARAMETER_GROUP_INFO

Invalid {GroupInfo} passed by the developer.

Troubleshooting: Ensure the {GroupInfo} parameter is not null.

34319

INVALID_PARAMETER_GROUP_ID

Invalid {groupId} passed by the developer.

Troubleshooting: Verify the {groupId} parameter is not empty and has a length between 1 and 64 after trimming.

34320

INVALID_PARAMETER_GROUP_NAME

Invalid {groupName} passed by the developer.

Troubleshooting: Ensure the {groupName} parameter is not empty and has a length between 1 and 64 after trimming.

34321

INVALID_PARAMETER_GROUP_IDS

Invalid {groupIds} passed by the developer.

Troubleshooting: Verify the {groupIds} array is not empty, has a length between 1 and 20, and each {groupId} is a string with a length between 1 and 64.

34322

INVALID_PARAMETER_GROUP_MEMBER_ROLE

Invalid {GroupMemberRole} passed by the developer.

Troubleshooting: Ensure the {GroupMemberRole} parameter is within the defined enum range.

34323

INVALID_PARAMETER_GROUP_APPLICATION_STATUS

Invalid {GroupApplicationStatus} passed by the developer.

Troubleshooting: Verify the {GroupApplicationStatus} array is not empty and each object is within the defined enum range.

34324

INVALID_PARAMETER_GROUP_APPLICATION_DIRECTION

Invalid {GroupApplicationDirection} passed by the developer.

Troubleshooting: Ensure the {GroupApplicationDirection} array is not empty and each object is within the defined enum range.

34325

INVALID_PARAMETER_NICK_NAME

Invalid {nickname} passed by the developer.

Troubleshooting: Verify the {nickname} parameter has a length between 1 and 64 after trimming.

34326

INVALID_PARAMETER_REASON

Invalid {reason} passed by the developer.

Troubleshooting: Ensure the {reason} parameter is not empty and has a length between 1 and 128 after trimming.

34327

INVALID_PARAMETER_REMARK

Invalid {remark} passed by the developer.

Troubleshooting: Verify the {remark} parameter is not empty and has a length between 1 and 64 after trimming.

34328

INVALID_PARAMETER_PAGING_QUERY_OPTION

Invalid {PagingQueryOption} passed by the developer.

Troubleshooting: Ensure the {PagingQueryOption} parameter is not null.

34330

INVALID_PARAMETER_QUERY_FRIENDS_DIRECTION_TYPE

Invalid {QueryFriendsDirectionType} passed by the developer.

Troubleshooting: Verify the {QueryFriendsDirectionType} parameter is within the defined enum range.

34331

INVALID_PARAMETER_DIRECTION_TYPE

Invalid {DirectionType} passed by the developer.

Troubleshooting: Ensure the {DirectionType} parameter is within the defined enum range.

34332

INVALID_PARAMETER_FRIEND_APPLICATION_TYPE

Invalid {FriendApplicationType} passed by the developer.

Troubleshooting: Verify the {FriendApplicationType} parameter is within the {RCFriendApplicationType} enum range.

34333

INVALID_PARAMETER_FRIEND_APPLICATION_STATUS

Invalid {FriendApplicationStatus} passed by the developer.

Troubleshooting: Ensure the {FriendApplicationStatus} parameter is within the defined enum range.

34334

INVALID_PARAMETER_FRIEND_ADD_PERMISSION

Invalid {FriendAddPermission} passed by the developer.

Troubleshooting: Verify the {FriendAddPermission} parameter is within the defined enum range.