Status Codes

SDK Status Codes

-1

ERRORCODE_UNKNOWN

Unknown error.

Troubleshooting Suggestions: API request timed out. Try again later. If the issue persists after multiple attempts, submit a Ticket with necessary details like App Key, User ID, and Time of Issue.

-3

OPERATION_MEDIA_NOT_FOUND

Failed to cancel pause.

Troubleshooting Suggestions: The file has already been downloaded. The Business Side can verify this via the Download Callback. For more details, refer to Download Media Message.

0

RC_SUCCESS

Success.

405

REJECTED_BY_BLACKLIST

Message sending failed as you’ve been added to the recipient’s blocklist.

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

20106

FORBIDDEN_IN_PRIVATE

Muted in One-to-One Chat.

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

20109

SYS_CONVERSATION_NOT_SUPPORT_MESSAGE

The System Conversation does not support sending this Message Type.

Troubleshooting Suggestions: System Conversations only allow sending RC:SRSMsg type messages. Other Message Types are not supported.

20512

CLOUD_DATA_CENTER_INVALID

The Data Center of the App Key does not match the requested Cloud Control Data Center.

Troubleshooting Suggestions:

1. If you’ve selected a domestic Data Center, use the domestic API Address when integrating the RC Server API on the App server. The client defaults to connecting to the domestic Data Center.
2. If you’ve selected an overseas Data Center (e.g., Singapore, North America, or Saudi Arabia), use the corresponding Overseas API Address when integrating the RC Server API on the App server.
3. Check which Data Center your app belongs to on the RC Console > App Configuration > Basic Info > AppKey Configuration page.
4. When integrating the client, pass the corresponding Area Code or manually configure the server address.

20604

SEND_FREQUENCY_TOO_FAST

Message Sending Frequency Too High. Only 5 messages are allowed per second.

Troubleshooting Suggestions: Delay the interface call on the client to avoid errors caused by excessive frequency.

20606

OPERATION_NOT_SUPPORT

Operation not supported. Only valid for Private Cloud. The Server Disabled the Operation.

Troubleshooting Suggestions: This only applies to Private Cloud environments. Public Cloud users can ignore this.

20607

REQUEST_OVER_FREQUENCY

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

Troubleshooting Suggestions: The Query Command Exceeded Limit. The default limit is 50 calls per second. Keep the client’s interface call frequency within 50 calls per second.

22201

MESSAGE_EXPAND_NOT_EXIST

Ultra group Expanded Message, but the Original Message does not exist.

Troubleshooting Suggestions:

1. Ultra group History Messages are stored for 7 days by default. Messages older than 7 days are deleted. Check the Sent Time to determine if the message is older than 7 days.
2. The original message may have been manually deleted.

22202

MESSAGE_EXPAND_NOT_SUPPORT

Ultra group Expanded Message, but the Original Message does not support expansion.

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

22203

MESSAGE_EXPAND_FORMAT_ERROR

Ultra group Expanded Message, but the expansion content format is incorrect.

Troubleshooting Suggestions: The server failed to parse the expansion content. The expansion content must be in JSON String Format, e.g., {"key":"value"}.

22204

MESSAGE_EXPAND_NOT_AUTHORIZED

Ultra group Expanded Message, but no operation permission.

Troubleshooting Suggestions: The Conversation Type Parameter Error. Check if the passed conversation type value is 10.

22406

NOT_IN_GROUP

Not in the Group.

Troubleshooting Suggestions:

1. Check if the user is in the Group. You can query or join the Group.
2. If the user is in the Group but the server still returns this error, submit a Ticket with necessary details like App Key, User ID, Group ID, and Time of Issue.

22408

FORBIDDEN_IN_GROUP

Muted in the Group.

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

23406

NOT_IN_CHATROOM

Not in the Chatroom.

Troubleshooting Suggestions:

1. You can query or join the Chatroom.
2. Chatrooms have an Automatic Destruction Mechanism and an Automatic Exit Mechanism for Offline Members. Triggering these mechanisms may also result in the user not being in the Chatroom. You can get detailed information from Chatroom Status Synchronization.
3. If the user is in the Chatroom but the server still returns this error, submit a Ticket with necessary details like App Key, User ID, Chatroom ID, and Time of Issue.

23407

GET_USERINFO_ERROR

Chatroom Mute Whitelist Exceeded Limit.

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

1. When adding a user to the Chatroom Whitelist, the passed User ID exceeds the limit (max 5). For interface details, refer to Add User to Chatroom Whitelist.
2. When adding a user to the Chatroom Global Mute Whitelist, the passed User ID exceeds the limit (max 20). For interface details, refer to Add User to Chatroom Global Mute Whitelist.

23408

FORBIDDEN_IN_CHATROOM

Muted in the Chatroom.

Troubleshooting Suggestions:

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

23409

RC_CHATROOM_USER_KICKED

Kicked and banned from joining the Chatroom. The ban duration depends on the time passed when the server called the kick interface.

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

23410

RC_CHATROOM_NOT_EXIST

Chatroom Does Not Exist.

Troubleshooting Suggestions:

1. Chatrooms have an Automatic Destruction Mechanism and an Automatic Exit Mechanism for Offline Members. For details, refer to Chatroom Destruction Mechanism and Exit Chatroom documentation. The business layer can observe if these mechanisms caused the issue.
2. You can also query or create the Chatroom.

23411

RC_CHATROOM_IS_FULL

Chatroom Member Exceeded Limit. Developers can submit a Ticket to request a change in the Chatroom member limit.

Troubleshooting Suggestions:

1. Chatroom business defaults to no member limit, but a limit can be configured. Confirm if a member limit has been configured.
2. To adjust the Chatroom member limit, submit a Ticket.

23412

RC_CHATROOM_PATAMETER_INVALID

Chatroom Interface Parameter Invalid. Confirm if the parameters are empty or valid.

Troubleshooting Suggestions:

1. Check if the parameters are empty or valid based on the interface documentation.
2. If the issue persists after checking the parameters, submit a Ticket with necessary details like interface name, interface parameters, and Time of Issue.

23413

CHATROOM_GET_HISTORYMSG_ERROR

Query Chatroom History Messages Exception.

Troubleshooting Suggestions: Submit a Ticket with necessary details like App Key, User ID, Chatroom ID, and query time.

23414

CHATROOM_NOT_OPEN_HISTORYMSG_STORE

Chatroom Cloud Storage Service Not Enabled.

Troubleshooting Suggestions: Enable the Chatroom Message Cloud Storage Service on the RC Console > App Configuration > IM Service > Chat pricing plans page.

23423

CHATROOM_KV_EXCEED

Chatroom KV Attributes Exceeded Limit.

Troubleshooting Suggestions: The default limit for a single Chatroom is 100.

23424

CHATROOM_KV_OVERWRITE_INVALID

No permission to modify existing attribute values in the Chatroom.

Troubleshooting Suggestions: The business layer does not have permission to modify KV attribute values set by others. To set, call the forced setting interface. For details, refer to Chatroom Attribute Management (KV) documentation.

23425

CHATROOM_SET_PROPERTY_OVER_FREQUENCY

(Deprecated) Exceeded the Chatroom status setting frequency. A Chatroom can set and delete status up to 100 times per second.

23426

CHATROOM_KV_STORE_NOT_OPEN

Chatroom Attribute Customization Service Not Enabled.

Troubleshooting Suggestions: Enable the Chatroom Attribute Customization on the RC Console > App Configuration > IM Service > Free Basic Features page.

23427

CHATROOM_KEY_NOT_EXIST

Chatroom Attribute Does Not Exist.

Troubleshooting Suggestions:

1. Confirm if the attribute exists by Query Chatroom Attribute.
2. When a Chatroom is destroyed, its custom attributes are also destroyed.
3. When setting an attribute, the autoDelete parameter set to 1 means the attribute is automatically deleted when the operating user exits the Chatroom.
4. If the business layer excludes active deletion and wants to understand why the attribute does not exist, submit a Ticket with necessary details like App Key, User ID, Chatroom ID, attribute KV, and Time of Issue.

23428

CHATROOM_KV_STORE_NOT_ALL_SUCCESS

Chatroom Batch Set or Delete KV Partially Unsuccessful.

Troubleshooting Suggestions: Submit a Ticket with necessary details like App Key, User ID, Chatroom ID, and Time of Issue.

23429

CHATROOM_KV_STORE_OUT_LIMIT

Chatroom Batch Set or Delete KV Exceeded Limit (max 10 per batch).

Troubleshooting Suggestions: The range is 1-10. This range cannot be adjusted.

23431

CHATROOM_KV_SET_ERROR

(Deprecated) Chatroom Set KV Failed. Occurs when two or more ends operate on the same KV simultaneously. If this error occurs, delay the operation to avoid simultaneous operations with other ends.

24001

HAVNODEVICEID

No DeviceId registered, meaning the user hasn’t logged in.

Troubleshooting: Submit a Support Ticket with necessary details like App Key, User ID, and the time the issue occurred.

24002

DEVICEIDISHAVE

The DeviceId already exists.

Troubleshooting: Submit a Support Ticket with necessary details like App Key, User ID, and the time the issue occurred.

24009

FEILD

No corresponding user or token.

Troubleshooting:

1. Check if the user is registered in RC Console > Operations Management > User Management.
2. Regenerate a token.

24011

NULLCHANNELNAME

/[Deprecated/] The channelName is empty.

24015

INTERNALERRROR

Internal server error.

Troubleshooting: Submit a Support Ticket with necessary details like App Key, User ID, and the time the issue occurred.

24360

RC_USER_PROFILE_KEY_NOT_ALLOW_SDK_SET

No permission to set this user’s hosted attribute.

Troubleshooting:

1. The client isn’t allowed to set the uniqueId parameter. Check if it was set when calling the updateMyUserProfile interface.
2. If you need to set uniqueId, use the Server API.

24361

RC_USER_PROFILE_KEY_NOT_EXIST

The key doesn’t exist in the user’s hosted basic attributes list.

Troubleshooting: The key for modifying the user’s hosted info doesn’t exist.

24362

RC_USER_PROFILE_EXT_KEY_NOT_EXIST

The key doesn’t exist in the user’s hosted extended attributes list.

Troubleshooting: The key for modifying the userExtProfile field doesn’t exist. Set the key in RC Console.

24363

RC_USER_PROFILE_EXT_KV_COUNT_EXCEED_LIMIT

Exceeded the maximum limit for user-hosted extended attributes.

Troubleshooting: The maximum limit for user-hosted extended attributes is 20.

24364

RC_USER_PROFILE_VALUE_LENGTH_EXCEED_LIMIT

The value of the user-hosted basic or extended attribute exceeds the maximum length.

Troubleshooting: The maximum length for the value is 256 characters.

24365

RC_USER_PROFILE_QUERY_COUNT_EXCEED_LIMIT

Exceeded the limit for batch querying user-hosted info.

Troubleshooting:

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

24366

RC_USER_PROFILE_USER_NOT_EXIST

The user doesn’t exist.

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

24367

RC_USER_PROFILE_VALUE_CAN_ONLY_BE_NUMBERS

The value of this user-hosted attribute must be a number.

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

24368

RC_USER_PROFILE_VALUE_EXCEED_RANGE

The value of this user-hosted attribute exceeds the allowed range.

Troubleshooting: The value must be within the allowed range when updating user info.

24369

RC_USER_PROFILE_SERVICE_UNAVAILABLE

The user info hosting service isn’t enabled.

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

24401

ULTRA_GROUP_SERVICE_UNAVAILABLE

The Ultra Group service isn’t enabled.

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

24402

ULTRA_GROUP_SERVICE_ERROR

An error occurred with the Ultra Group service.

Troubleshooting: Submit a Support Ticket with necessary details like App Key, User ID, and the time the issue occurred.

24403

ULTRA_GROUP_PARAMETER_ERROR

The Ultra Group parameter is incorrect.

Troubleshooting: Check the parameters.

24404

ULTRA_GROUP_UNKNOWN_ERROR

An unknown error occurred with the Ultra Group.

Troubleshooting: Submit a Support Ticket with necessary details like App Key, User ID, and the time the issue occurred.

24406

NOT_IN_ULTRA_GROUP

You’re not a member of this Ultra Group.

Troubleshooting: Check if you’re a member of the ultra group.

24408

FORBIDDEN_IN_ULTRA_GROUP

You’ve been muted in this Ultra Group.

Troubleshooting:

24410

ULTRA_GROUP_NOT_EXIST

The Ultra Group doesn’t exist.

Troubleshooting: Create the Ultra Group.

24412

ULTRA_GROUP_JOINED_OVERSIZE

The number of Ultra Groups you’ve joined has exceeded the limit.

Troubleshooting: The maximum number of Ultra Groups you can join is 100.

24413

ULTRA_GROUP_CHANNELS_OVERSIZE

The number of Ultra Group channels created has exceeded the limit.

Troubleshooting: The maximum number of Ultra Group channels you can create is 50.

24414

ULTRA_GROUP_CHANNEL_ID_NOT_EXIST

The Ultra Group channel ID doesn’t exist.

Troubleshooting:

1. Create the Ultra Group channel.

24415

ULTRA_GROUP_MESSAGE_SENT_OVER_FREQUENCY

Exceeded the Ultra Group channel message sending frequency limit.

Troubleshooting: Each Ultra Group channel has a message sending frequency limit of 20 messages per second. Delay sending or retry.

24416

ULTRA_GROUP_USER_NOT_IN_PRIVATE_CHANNEL

You’re not in this Ultra Group’s private channel.

Troubleshooting: Add members to the private channel as per your business needs.

25101

RECALL_MESSAGE

Invalid message recall parameters.

Troubleshooting: Submit a Support Ticket with necessary details like App Key, User ID, and the time the issue occurred.

25102

MESSAGE_STORAGE_SERVICE_UNAVAILABLE

The single/group chat cloud storage service isn’t enabled.

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

25104

RC_SERVER_UNKOWN_ERROR

Unknown error.

Troubleshooting: Submit a Support Ticket with necessary details like App Key, User ID, and the time the issue occurred.

25107

RECALL_MESSAGE_USER_INVALID

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

Troubleshooting:

1. By default, IMLib SDK can recall any message. When the "IMLib SDK Only Allows Recalling Own Messages" switch is enabled, only your own messages can be recalled. Submit a Support Ticket to enable this service.
2. The Server API doesn’t perform this check and can recall all messages.

25402

RC_ENTRUST_SERVER_ERROR

An error occurred with the hosting service.

Troubleshooting: Submit a Support Ticket with necessary details like App Key, User ID, and the time the issue occurred.

25403

RC_ENTRUST_SERVER_PARAMETER_ERROR

The hosting service parameter is incorrect.

Troubleshooting:

1. Check the parameters.
2. If in doubt, submit a Support Ticket with necessary details like App Key, User ID, the called interface, and parameters.

25404

RC_GROUP_ILLEGAL_ERROR

Illegal operation. Only the group owner can modify group permissions.

Troubleshooting: Confirm the group owner ID.

25405

RC_GROUP_AUTHORITY_ERROR

No permission to perform this operation.

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

25406

RC_GROUP_PARAMETER_LENGTH_EXCEED_LIMIT

Parameter error. The length exceeds the limit.

Troubleshooting:

1. Check the parameters against the interface documentation.
2. If the parameters are valid but the issue persists, submit a Support Ticket with the interface and parameter info.

25407

RC_GROUP_PARAMETER_FORMAT_ERROR

Parameter error. Contains illegal characters.

Troubleshooting: The built-in key for group attributes doesn’t exist.

25408

RC_GROUP_PARAMETER_VALUE_CAN_ONLY_BE_NUMBERS

The parameter value must be a number.

Troubleshooting:

1. Check the parameters against the interface documentation.
2. If the parameters are valid but the issue persists, submit a Support Ticket with the interface and parameter info.

25409

RC_GROUP_ID_ALREADY_EXIST

The group ID already exists.

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

25410

RC_GROUP_ID_NOT_EXIST

The group ID doesn’t exist.

Troubleshooting: The group ID doesn’t exist. Create it as needed.

25411

RC_GROUP_MEMBERS_COUNT_EXCEED_LIMIT

The group member limit has been exceeded.

Troubleshooting:

1. The maximum number of users you can invite to a group at once is 30.
2. The maximum number of group members is 3000.

25412

RC_GROUP_MEMBERS_ALREADY_IN_GROUP

The group member ID is already in this group.

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

25413

RC_GROUP_NOT_ALLOW_SDK_OPERATION

This operation isn’t allowed via the SDK.

Troubleshooting: This attribute can’t be modified by the client. Check RC Console > App Configuration > IM Service > Info Hosting Service > Group Custom Attributes.

25414

RC_GROUP_NOT_ALLOW_JOIN

No one is allowed to join this group.

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

25415

RC_GROUP_EXT_KEY_NOT_EXIST

The extended info key doesn’t exist.

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

25416

RC_GROUP_REQUEST_OVERFREQUENCY

Exceeded the query frequency limit.

Troubleshooting: The frequency limit for group hosting - user query-related interfaces is 5 times per second. This currently only applies to the web.

25417

RC_GROUP_OWNER_NOT_ALLOW_QUIT_OR_KICK

The group owner can’t be kicked/quit the group/set as an admin.

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

25418

RC_GROUP_USER_NOT_IN_GROUP

The user ID isn’t in this group.

Troubleshooting: Confirm the user’s group membership.

25419

RC_GROUP_MANAGER_OR_FOLLOW_COUNT_EXCEED_LIMIT

The number of admins/followers has exceeded the limit.

Troubleshooting:

1. The maximum number of admins 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 isn’t an admin of this group.

Troubleshooting: Set the group admin as per your business needs.

25421

RC_GROUP_APPLICATION_NOT_EXIST

No corresponding group ID and user ID invitation request.

Troubleshooting:

1. Invitation info is only stored for 7 days. Check if the invitation has expired.
2. Check if an invitation was sent. Resend the invitation as per your business needs. Refer to invite User to Join Group.

25422

RC_GROUP_QUERY_GROUP_COUNT_EXCEED_LIMIT

Exceeded the limit for querying group info.

Troubleshooting:

1. The maximum number of groups you can query at once is 20.
2. The maximum number of group members you can query at once is 100.

25423

RC_GROUP_NAME_INVALID

The group name can’t be empty.

Troubleshooting:

25424

RC_GROUP_JOIN_GROUP_NEED_MANAGER_ACCEPT

The request to join the group requires admin approval.

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

25425

RC_GROUP_OWNER_NOT_ALLOW_BE_MANAGER

The group owner can’t be set as an admin.

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

25426

RC_GROUP_NO_INVITE_PERMISSION

No permission to invite users to the group.

Troubleshooting:

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

25427

RC_GROUP_NEED_INVITEE_ACCEPT

The invitation to join the group requires the invitee’s approval.

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

25428

RC_GROUP_APPLICATION_ALREADY_HANDLE

The request has already been handled by another admin.

Troubleshooting: Prompt the admin to handle the request as per your business needs.

25429

RC_GROUP_OLD_GROUP_NOT_ENTRUST

Old groups don’t support hosting interfaces. They must be imported first.

Troubleshooting:

25430

RC_GROUP_ID_INVALID

The 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

Failed to parse the pageToken.

Troubleshooting: Check if the pageToken is correct and matches the one returned from the previous request.

25460

RC_FRIEND_ALREADY_FRIEND

You’re already friends. The operation is invalid.

Troubleshooting: Confirm the friendship.

25461

RC_FRIEND_NEED_ACCEPT

The other party must approve before you can become friends.

Troubleshooting: Set the friend request permission at the App Key level or user level:

1. App Key level: Set in RC Console > App Configuration > IM Service > Info Hosting Service - Function Settings.
2. User level: Set via the client method Set Friend Request Permission.

25462

RC_FRIEND_IN_OTHER_BLACK_LIST

You’re in the target user’s blacklist. Can’t add as a friend.

Troubleshooting: Remove the user from the blacklist as per your business needs. Refer to Remove User from Blacklist.

25463

RC_FRIEND_NOT_IN_OTHER_WHITE_LIST

You’re not in the target user’s whitelist. Can’t add as a friend.

Troubleshooting: The target user has enabled the whitelist feature. You must be added to their whitelist to become friends. Refer to User Whitelist Service.

25464

RC_FRIEND_IN_MY_BLACK_LIST

The target user is in your blacklist. Can’t add as a friend.

Troubleshooting: Remove the user from your blacklist as per your business needs. Refer to Remove User from Blacklist.

25465

RC_FRIEND_NOT_IN_MY_WHITE_LIST

The target user isn’t in your whitelist. Can’t add as a friend.

Troubleshooting: You’ve enabled the whitelist feature. Add the target user to your whitelist to become friends. Refer to User Whitelist Service.

25466

RC_FRIEND_APPLICATION_NOT_EXIST

The friend request doesn’t exist or has expired.

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

25467

RC_FRIEND_MY_FRIEND_COUNT_EXCEED_LIMIT

Exceeded your friend limit.

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

25468

RC_FRIEND_OTHER_FRIEND_COUNT_EXCEED_LIMIT

Exceeded the target user’s friend limit.

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

25469

RC_FRIEND_NOT_FRIEND

You’re not friends. Can’t perform this operation.

Troubleshooting: Check the friendship.

25470

RC_FRIEND_FIELDS_LENGTH_EXCEED_LIMIT

Exceeded the limit for custom friend attributes.

Troubleshooting: The maximum number of custom friend attributes is 10.

25471

RC_FRIEND_OTHER_NOT_ALLOW_ADD_FRIEND

The other party doesn’t allow friend requests.

Troubleshooting:

25472

RC_FRIEND_NOT_EXIST

The friend doesn’t exist.

Troubleshooting: The User ID doesn’t exist. Register the user first.

25473

RC_FRIEND_NOT_ALLOW_ADD_SELF

Can’t add yourself as a friend.

Troubleshooting:

1. For the Server API, check if the userId and targetId are the same. They must be different.
2. For the client interface, check if the userId matches the User ID connected to RC. They must be different.

26001

PUSH_PARAMETER_INVALID

The user-level setting service request parameter is invalid.

Troubleshooting: Submit a Support Ticket with necessary details like App Key, User ID, the called interface, and parameters.

26002

USER_SETTING_SYNCED_ERROR

The client version is too low. Sync the version or submit a Support Ticket to enable the user-level configuration switch.

Troubleshooting: Submit a Support Ticket to enable the user-level configuration switch.

26004

CONVERSATION_TAG_OVERSIZE

Exceeded the limit for user conversation tags. The maximum is 20.

Troubleshooting: The maximum number of tags is 20.

26005

RC_READ_RECEIPT_V4_INVALID

The v4 read receipt feature isn’t enabled.

Troubleshooting: Submit a Support Ticket.

26007

RC_SERVER_PARAMETER_MESSAGEUIDS_CONFUSED

The message ID order is incorrect.

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

26009

RC_SERVER_PARAMETER_MESSAGEUID_INVALID

The message ID is invalid.

Troubleshooting: Check the messageUid parameter.

26010

RC_SERVER_PARAMETER_INVALID

The parameter is incorrect.

Troubleshooting: Submit a Support Ticket with necessary details like App Key, User ID, the called interface, and parameters.

26020

RC_SUBSCRIBE_ONLINE_SERVICE_UNAVAILABLE

The online status subscription feature isn’t enabled.

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

26021

RC_BESUBSCRIBED_USERIDS_COUNT_EXCEED_LIMIT

Exceeded the limit for user subscriptions.

Troubleshooting: The maximum number of user subscriptions is 5000.

26022

RC_SUBSCRIBED_USERIDS_EXCEED_LIMIT

Exceeded the limit for subscribed users.

Troubleshooting: The maximum number of subscribed users is 5000.

26106

RC_FILE_SIZE_EXCEED_LIMIT

The uploaded file exceeds the maximum size limit.

Troubleshooting: The maximum file size is 100 MB.

26107

INVALID_PARAMETER_SIZE_NOT_FOUND

The size parameter is missing when enabling the limit.

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

30001

RC_CHANNEL_INVALID

The current connection has been released.

Troubleshooting:

1. Use IMLib’s RCConnectionStatusChangeDelegate to monitor the connection status.
2. Try switching to a more stable network. If the issue persists, submit a Support Ticket with necessary details like App Key, User ID, and the time the issue occurred.

30002

RC_NETWORK_UNAVAILABLE

The current connection is unavailable.

Troubleshooting:

1. Other asynchronous API interfaces can only be called after the connect connection is successful.
2. Use IMLib’s RCConnectionStatusChangeDelegate to monitor the connection status. The ConnectionStatus_Connected value indicates a successful connection.

30003

RC_MSG_RESPONSE_TIMEOUT

The client’s message request timed out.

Troubleshooting: Retry later or switch to a more stable network. If the issue persists, submit a Support Ticket with necessary details like App Key, User ID, and the time the issue occurred.

30005

RC_NAVIGATION_REQUEST_TIMEOUT

Failed to request the navigation address.

Troubleshooting: Retry later or switch to a more stable network. If the issue persists, submit a Support Ticket with necessary details like App Key, User ID, and the time the issue occurred.

30006

RC_NAVIGATION_RESPONSE_ERROR

Failed to receive the HTTP response during navigation.

Troubleshooting: Retry later or switch to a more stable network. If the issue persists, submit a Support Ticket with necessary details like App Key, User ID, and the time the issue occurred.

30007

RC_NAVI_RESPONSE_ERROR

The navigation response is abnormal.

Troubleshooting: Retry later or switch to a more stable network. If the issue persists, submit a Support Ticket with necessary details like App Key, User ID, and the time the issue occurred.

30009

RC_DOMAIN_NOT_FOUND

No valid IP address found after parsing the navigation data.

Troubleshooting: Submit a Support Ticket with necessary details like App Key, User ID, and the time the issue occurred.

30015

RC_CONNECT_OVER_FREQUENCY

The connection frequency is too high.

Troubleshooting: This is not currently used on iOS.

30016

RC_MSG_SIZE_OUT_OF_LIMIT

The message size exceeds the limit. The message body (serialized into JSON format) must not exceed 128 KB.

Troubleshooting:

1. A common cause is when sending image messages, the thumbnail is too large. Ensure the base64 thumbnail doesn’t exceed 80 KB.
2. Ensure the RCMessage object’s content length doesn’t exceed 128 KB.

30019

RC_NETWORK_IS_DOWN_OR_UNREACHABLE

The network connection is unavailable.

Troubleshooting: Retry later or switch to a more stable network. If the issue persists, submit a Support Ticket with necessary details like App Key, User ID, and the time the issue occurred.

30021

RC_RMTP_CONNECTED_ERROR

TCP connection succeeded, but RMTP connection failed.

Troubleshooting Suggestions: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 occurrence time.

31000

RC_CONN_ACK_TIMEOUT

Connection ACK timeout.

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 occurrence time.

31002

RC_CONN_ID_REJECT

Client INFO field format error. Correct format is {Platform type}-{Device info}-{SDK version}. Device info is {Phone type}|{Phone model}|{Network type, 4G/WiFi/}|{Carrier, China Mobile/China Telecom/China Unicom}.

Troubleshooting:

1. Correct format: {Platform type}-{Device info}-{SDK version}. Device info: {Phone type}|{Phone model}|{Network type, 4G/WiFi}|{Carrier, China Mobile/China Telecom/China Unicom}.
2. Submit a ticket with details like App key, user ID, and issue occurrence time.

31004

RC_CONN_TOKEN_INCORRECT

Invalid token; App key and token mismatch; Token expired.

Troubleshooting:

1. Ensure the App key passed during app initialization matches the one used to get the token.
2. For overseas data centers, confirm the region code is set.
3. Check the token's validity period in RC Console > App Configuration > Basic Info.
4. Revalidate the connection by getting a new token.

31005

RC_CONN_NOT_AUTHRORIZED

App verification enabled but verification failed.

Troubleshooting: Submit a ticket with details like App key and package name.

31007

RC_CONN_PACKAGE_NAME_INVALID

Package name does not match RC console registration.

Troubleshooting: Submit a ticket with details like App key and package name.

31008

RC_CONN_APP_BOCKED_OR_DELETED

App key blocked or deleted.

Troubleshooting: Request recovery in RC Console > App Management.

31009

RC_CONN_USER_BLOCKED

Client-initiated connection failed, user blocked.

Troubleshooting: Unblock as needed.

31010

RC_DISCONN_KICK

User kicked offline.

Troubleshooting:

1. By default, the same user account can only be online on one device across mobile, web, desktop, and mini-program.
2. For multi-device login (e.g., multiple web tabs), follow the multi-platform online documentation.

31020

RC_CONN_TOKEN_EXPIRE

Token expired.

Troubleshooting:

1. Check the token's validity period in RC Console > App Configuration > Basic Info.
2. Revalidate the connection by getting a new token.

31023

RC_CONN_OTHER_DEVICE_LOGIN

Error code indicates same type of client already online after enabling switch to prevent kicking online clients.

Troubleshooting: Refer to the reconnection and kick mechanism documentation.

31024

CONCURRENT_LIMIT_ERROR

Total connections exceed service-configured concurrency limit (private cloud only).

Troubleshooting:

1. Check the connection limit in the private cloud management backend under the app's configuration.
2. To modify the limit, a new identifier must be used.

31025

RC_CONN_CLUSTER_ERROR

Client connected to wrong environment, causing connection rejection; e.g., using a development App key to connect to production.

Troubleshooting: Submit a ticket with details like App key and package name.

31026

RC_CONN_APP_AUTH_FAILED

App Server joint authentication failed after enabling App Server joint authentication.

Troubleshooting: Submit a ticket with details like App key and package name.

31029

RC_CONN_USER_ABANDON

User account deactivated.

Troubleshooting:

1. Check if the account is deactivated. Refer to the query deactivated users documentation.
2. If deactivated, reactivate the user ID as needed. Refer to the reactivate user ID documentation.

31030

RC_CONN_APP_LICENSE_EXPI

Private cloud license check failed, app license expired.

Troubleshooting:

1. Please check if the Identifier and License information in the private cloud management console have expired.
2. If they have expired, please contact the business department.
3. If you are using the HarmonyOS SDK, please contact the business department.

32001

RC_QUERY_ACK_NO_DATA

Protocol Layer internal. Error Data error occurred during query, upload, or download.

Troubleshooting: Submit a support ticket and include necessary details like App Key, User ID, and issue occurrence time.

32002

RC_MESSAGE_DATA_INCOMPLETE

Protocol Layer internal error.

Troubleshooting: Submit a support ticket and include necessary details like App Key, User ID, and issue occurrence time.

32011

RC_UDP_DISCONNECTED

Server actively disconnected the connection under Quic protocol.

Troubleshooting: Submit a support ticket and include necessary details like App Key, User ID, and issue occurrence time.

32054

RC_CONNECTION_RESET_BY_PEER

Connection was interrupted by the server, possibly due to the operator considering the connection illegal or invalid. The SDK will automatically trigger a reconnection after this error code, no action is required from the app.

Troubleshooting: Retry later or switch to a stable network and retry. If the issue persists, submit a support ticket and include necessary details like App Key, User ID, and issue occurrence time.

33000

BIZ_SAVE_MESSAGE_ERROR

When sending or inserting a message, the message needs to be stored in the local database. This error code is called back when the storage fails.

Troubleshooting:

1. Check if the user's device has sufficient memory.
2. Ensure the connection process was successful.
3. If the connection is stable and memory is sufficient, submit a support ticket and include necessary details like App Key, User ID, and issue occurrence time.

33001

CLIENT_NOT_INIT

Protocol stack not initialized.

Troubleshooting: Check if the initialization interface has been executed.

33002

DATABASE_ERROR

Database error.

Troubleshooting:

1. Check if the initialization interface has been executed and the connection process was successful.
2. If the issue persists, submit a support ticket and include necessary details like App Key, User ID, and issue occurrence time.

33003

INVALID_PARAMETER

Parameter error passed when calling the developer interface.

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

33007

MSG_ROAMING_SERVICE_UNAVAILABLE

Message Roaming Service not activated.

Troubleshooting:

1. Check if the Message Roaming Service has been activated in RC Console > Application Configuration > IM Service > Chat pricing plans.
2. If it has been activated and it’s been about 2 hours, try uninstalling and reinstalling (the SDK will update the navigation information).

33008

RC_PROTOCOL_MESSAGE_INSERTED_ERROR

Failed to insert message into the local database.

Troubleshooting:

1. Check if the initialization interface has been executed and the connection process was successful.
2. Check if the device has sufficient memory.
3. If the issue persists, submit a support ticket and include necessary details like App Key, User ID, and issue occurrence time.

33009

RC_CHATROOM_RESET

Chatroom has been recycled.

Troubleshooting: Confirm the chatroom information.

33100

RC_TAG_NOT_EXIST

Tag does not exist.

Troubleshooting:

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

33101

RC_TAG_ALREADY_EXISTS

Tag already exists.

Troubleshooting: Confirm if the tag exists by getting the tag list. For details, refer to documentation.

33102

RC_TAG_INVALID_FOR_CONVERSATION

Tag is not in the conversation.

Troubleshooting: Confirm if the tag exists by getting all tags under the specified conversation. For details, refer to documentation.

34001

RC_CONNECTION_EXIST

Connection already exists.

Troubleshooting: The connection already exists, no need to call the connection again.

34002

RC_SIGHT_MSG_DURATION_LIMIT_EXCEED

Short video duration exceeds the limit.

Troubleshooting: Check the duration of the short video. The maximum duration cannot exceed 2 minutes.

34003

RC_GIF_MSG_SIZE_LIMIT_EXCEED

GIF message file size exceeds the limit.

Troubleshooting: Check the size of the GIF image message. The limit is 2MB.

34004

RC_KV_STORE_NOT_SYNC

Chatroom status not fully synchronized.

Troubleshooting:

1. When just joining the chatroom, calling the get KV interface may result in incomplete synchronization between local data and the server. It is recommended to wait for a while before retrieving.
2. The timing of calling the get chatroom KV is incorrect, or the chatroom has been recycled. Please call after the chatroom status is fully synchronized.

34005

RC_ENVIRONMENT_ERROR

Incorrect connection environment.

Troubleshooting:

1. This error code applies to private cloud. Public cloud users can ignore it.
2. Using a public cloud SDK in a private cloud environment will result in this error.
3. Private cloud SDKs will carry an enterprise identifier.
4. If you are unsure, please contact the business team.

34006

RC_CONNECT_TIMEOUT

Connection timeout.

Troubleshooting:

1. The current connection to RC service is unstable. Users can determine if the connection is successful by monitoring the connection status.
2. Retry later or switch to a stable network and retry. If the issue persists, submit a support ticket and include necessary details like App Key, User ID, and issue occurrence time.

34007

RC_PUBLIC_SERVICE_PROFILE_NOT_EXIST

The queried public service information does not exist.

Troubleshooting: Ensure that the type of the queried public service matches the public service ID.

34008

RC_MESSAGE_CANT_EXPAND

Message cannot be expanded.

Troubleshooting:

1. Check if the message's expandable attribute canIncludeExpansion is set to true before sending. For details, refer to message expansion.
2. Message expansion only supports single chat, group chat, and ultra group conversation types. Check if it is a message of another conversation type.

34009

RC_MESSAGE_EXPAND_FAIL

Message expansion failed.

Troubleshooting: Check if the SDK is properly initialized and connected. Users can determine if the connection is successful by monitoring the connection status.

34010

RC_MSG_EXPANSION_SIZE_LIMIT_EXCEED

Message expansion size exceeds the limit.

Troubleshooting: By default, the message expansion dictionary key length does not exceed 32 characters, the value length does not exceed 4096 characters, and the number of expansion key-value pairs does not exceed 300. A maximum of 20 can be set at a time.

34011

RC_FILE_UPLOAD_FAILED

Media message media file HTTP upload failed.

Troubleshooting: Retry later or switch to a stable network and retry. If the issue persists, submit a support ticket and include necessary details like App Key, User ID, and issue occurrence time.

34012

RC_CONVERSATION_TAG_INVALID_CONVERSATION_TYPE

The specified conversation type does not support the tag feature.

Troubleshooting: Confirm if the conversation type is single chat, group chat, or system conversation. Currently, the tag feature only supports these three conversation types.

34013

RC_CONVERSATION_TAG_LIMIT_EXCEED

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

Troubleshooting: A maximum of 1000 conversations can be added/removed.

34014

RC_Group_Read_Receipt_Version_Not_Support

Group read receipt version not supported.

Troubleshooting: Check if the called interface matches the integrated SDK. If you are integrating IMLib, refer to read receipt. If you are integrating GlobalKit, you need to activate the relevant feature. For details, refer to read receipt.

34015

RC_SIGHT_COMPRESS_FAILED

Video compression failed.

Troubleshooting: This is usually caused by issues with the video resource itself. Check if the video resource path has access permissions or if the resource itself is incorrect. If the issue persists, submit a support ticket and include necessary details like App Key, User ID, and issue occurrence time.

34016

RC_USER_SETTING_DISABLED

User-level settings not activated.

Troubleshooting: Submit a support ticket and include necessary details like App Key, User ID, and issue occurrence time.

34017

RC_MESSAGE_NULL_EXCEPTION

The message returned by the message interceptor processing interface is null.

Troubleshooting: Check the methods implemented in the RCMessageInterceptor protocol to see if there is a case where the returned message is null.

34018

RC_MEDIA_EXCEPTION

Media file upload exception, media file does not exist or file size is 0.

Troubleshooting:

1. Check if the media file path is accessible using [[NSFileManager defaultManager] fileExistsAtPath:localPath].
2. Check the file size using [[[NSFileManager defaultManager] attributesOfItemAtPath:sightContent.localPath error:nil] fileSize].

34019

RC_MEDIA_FILETYPE_INVALID

Uploaded media file format not supported.

Troubleshooting: Submit a support ticket and include necessary details like App Key, User ID, and issue occurrence time.

34020

RC_FILE_EXPIRED

File has expired or been cleaned up.

Troubleshooting: RC's default file service address stores short video files for 7 days and other files for 6 months, after which they are automatically cleaned up. Confirm if this message has expired. If the issue persists, submit a support ticket and include necessary details like App Key, User ID, and issue occurrence time.

34021

RC_MESSAGE_NOT_REGISTERED

Message not registered.

Troubleshooting:

1. If the error is for a custom message, the custom message needs to be registered first. For details, refer to register custom message.
2. If the error is for an SDK built-in message, confirm if the SDK is properly initialized and connected.

34022

RC_ULTRA_GROUP_NOT_SUPPORT

This interface does not support ultra group conversation.

Troubleshooting: Check if the passed conversation type ConversationType is ConversationType_ULTRAGROUP. For details on conversation types, refer to documentation.

34025

RC_MESSAGE_EXPAND_CONVERSATION_TYPE_NOT_MATCH

Message expansion failed because the conversation type in the message does not match the conversation type supported by the interface.

Troubleshooting:

1. Check if the message.conversationType is single chat, group chat, or ultra group conversation. Currently, message expansion only supports these three conversation types.
2. Check the specific interface call. The message expansion related interfaces for single chat and group chat are in the RCCoreClient class, while the message expansion interfaces for ultra group are in the RCChannelClient class, and the interface names contain the UltraGroup field.

34200

INVALID_PARAMETER_LANGUAGE

The language passed during the developer interface call is invalid.

Troubleshooting Suggestions: Check the language information passed to the setPushLanguageCode or setPushLanguage interface. This parameter cannot be empty.

34201

INVALID_PARAMETER_CONVERSATIONTYPENOTSUPPORT

The interface called by the developer does not support the passed ConversationType.

Troubleshooting Suggestions: Check if the passed parameter format complies with the relevant interface documentation.

34202

INVALID_PARAMETER_TIMESTAMP

The timestamp passed during the developer interface call is invalid.

Troubleshooting Suggestions: Verify the interface parameter type through the API DOC.

34203

INVALID_PARAMETER_MESSAGEUID

The UID (Unique Identifier for server messages) passed during the developer interface call is invalid.

Troubleshooting Suggestions: Verify the interface parameter type through the API DOC.

34204

INVALID_PARAMETER_MESSAGEID

The `MessageId` passed during the developer interface call is invalid or the corresponding message cannot be found.

Troubleshooting Suggestions: Verify the interface parameter type through the API DOC.

34205

INVALID_PARAMETER_MESSAGECONTENT

The `Message` or `MessageContent` passed during the developer interface call is invalid.

Troubleshooting Suggestions: Verify the interface parameter type through the API DOC.

34206

INVALID_PARAMETER_MESSAGELIST

The `MessageList` passed during the developer interface call is invalid.

Troubleshooting Suggestions: Verify the interface parameter type through the API DOC.

34207

INVALID_PARAMETER_MEDIATYPE

The `MediaType` passed during the developer interface call is invalid.

Troubleshooting Suggestions: Verify the interface parameter type through the API DOC.

34208

INVALID_PARAMETER_REQUESTURL

The `RequestUrl` passed during the developer interface call is invalid.

Troubleshooting Suggestions: Check if the MediaUrl has a value when calling the interface to download media resource files.

34209

INVALID_PARAMETER_CONVERSATIONTYPE

The `ConversationType` passed during the developer interface call is invalid.

Troubleshooting Suggestions: Check if the ConversationType value in the passed parameters belongs to the RCConversationType enumeration.

34210

INVALID_PARAMETER_TARGETID

The `targetId` passed during the developer interface call is invalid.

Troubleshooting Suggestions: Check if the passed parameter is of type NSString and its length is between 0-64 characters.

34211

INVALID_PARAMETER_CHANNELID

The `channelId` passed during the developer's channel-related interface call is invalid.

Troubleshooting Suggestions: Verify the interface parameter type through the API DOC.

34212

INVALID_PARAMETER_TAGID

The `tagId` passed during the developer interface call is invalid.

Troubleshooting Suggestions: Check if the passed parameter is of type NSString and its length is between 0-10 characters.

34213

INVALID_PARAMETER_TAGNAME

The `tagName` passed during the developer interface call is invalid.

Troubleshooting Suggestions: Check if the passed parameter is of type NSString and its length is between 0-15 characters.

34214

INVALID_PARAMETER_USERID

The `userId` passed during the developer interface call is invalid.

Troubleshooting Suggestions: Check if the passed parameter is of type NSString and its length is greater than 0.

34215

INVALID_PARAMETER_USERIDLIST

The `userIdList` passed during the developer interface call is invalid.

Troubleshooting Suggestions: Verify the interface parameter type through the API DOC.

34216

INVALID_PARAMETER_USERONLINESTATUS

The `UserOnlineStatus` passed during the developer interface call is invalid.

Troubleshooting Suggestions: Check if the custom online status customerStatus value is between 1-255.

34217

INVALID_PARAMETER_DOWNLOADMEDIAFILENAME

The `downloadMediaFileName` passed during the developer interface call is invalid.

Troubleshooting Suggestions: Check if the fileName object passed to the interface is non-empty.

34218

INVALID_PARAMETER_SETOFFLINEMESSAGEDURATION

The parameter passed to the `setOfflineMessageDuration` interface is invalid.

Troubleshooting Suggestions: Check if the duration object value passed to the interface is between 0-8.

34219

INVALID_PARAMETER_RCHISTORYMESSAGEOPTION_COUNT

The `HistoryMessageOption` passed during the developer interface call is invalid.

Troubleshooting Suggestions: Check if the count object value in the HistoryMessageOption parameter passed to the interface is greater than 0.

34220

INVALID_PARAMETER_MESSAGEEXPANSION

The `MessageExpansion` passed during the developer interface call is invalid.

Troubleshooting Suggestions: Verify the interface parameter type through the API DOC.

34221

INVALID_PARAMETER_ULTRAGROUPMESSAGEEXPANSION_KEYARRAY

The `KeyArray` passed during the developer interface call for `UltraGroupMessageExpansion` is invalid.

Troubleshooting Suggestions: Check if the KeyArray object passed to the interface is non-empty.

34222

INVALID_PARAMETER_UPLOADVOIPDEVICETOKEN

The `uploadVoIPDeviceToken` interface detected an invalid VoIP DeviceToken.

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

34223

INVALID_PARAMETER_NOTMEDIAMESSAGE

The `Message.content` passed to the `sendMediaMessage` interface is not a multimedia message.

Troubleshooting Suggestions: Check if the Message.content object passed to the interface is an RCMediaMessageContent object.

34224

INVALID_PARAMETER_TIMESTRING

The time parameter passed during the developer interface call is invalid.

Troubleshooting Suggestions: Check if the time object passed to the interface is a non-empty string type.

34225

INVALID_PARAMETER_CONVERSATIONIDENTIFIER

The `RCConversationIdentifier` parameter is invalid.

Troubleshooting Suggestions: Check if the RCConversationIdentifier object passed to the interface is a non-empty object of the correct type.

34226

RC_GETBLOCKPUSH_FAILED

The developer failed to call the `GetBlockPush` interface.

Troubleshooting Suggestions: Check if the targetId value is between 1-255, and ensure the SDK is properly initialized and connected.

34227

RC_DB_QUERY_ERROR

The developer failed to query the database using the database query interface.

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

34228

INVALID_PARAMETER_NOTIFICATION_LEVEL

The `PushNotificationLevel` is invalid.

Troubleshooting Suggestions: Verify the interface parameter type through the API DOC.

34231

INVALID_PARAMETER_CHANNEL_TYPE

The UltraGroup channel type is invalid.

Troubleshooting Suggestions: Check if the passed parameter belongs to the RCUltraGroupChannelType enumeration.

34232

INVALID_PARAMETER_COUNT

The `count` passed during the developer interface call is invalid.

Troubleshooting Suggestions: Verify the interface parameter type through the API DOC.

34233

INVALID_PARAMETER_SEND_TIME

The `sendTime` passed during the developer interface call is invalid.

Troubleshooting Suggestions: Check if the sendTime object value is a valid timestamp greater than or equal to 0.

34235

INVALID_PARAMETER_MEDIA_URL

The `mediaUrl` passed during the developer interface call is empty.

Troubleshooting Suggestions: Check if the mediaUrl object value is non-empty.

34236

INVALID_PARAMETER_UNIQUE_ID

The `uniqueId` passed during the developer interface call is invalid.

Troubleshooting Suggestions: Check if the uniqueId object value is non-empty.

34238

INVALID_PARAMETER_PROXY

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

Troubleshooting Suggestions: Verify the interface parameter type through the API DOC.

34239

INVALID_PARAMETER_TESTHOST

The proxy test service passed during the developer's `testProxy` interface call is invalid.

Troubleshooting Suggestions: Verify the interface parameter type through the API DOC.

34240

INVALID_CONNECT_TESTHOST_FAILED

The developer failed to connect during the `testProxy` interface call.

Troubleshooting Suggestions: Verify the interface parameter type through the API DOC. If the issue persists, submit a ticket.

34241

INVALID_PARAMETER_ULTRA_GROUP_MESSAGE_OBJECT_NAME

The {Developer API} call to {recallUltraGroupMessage} attempted to recall an unsupported {Message Type}.

Troubleshooting: Verify the parameter types in the {API DOC}(https://doc.rongcloud.cn/apidoc/imlibcore-ios/latest/zh_CN/documentation/rongimlibcore?language=objc).

34243

INVALID_PARAMETER_MESSAGE

The {message} parameter passed by the developer is empty.

Troubleshooting: Check the {message} object passed to the interface. Ensure {message.targetId} and {message.content} are non-empty objects.

34245

RC_CONN_PROXY_UNAVAILABLE

The configured {Proxy Address} is unavailable.

Troubleshooting: Submit a {Support Ticket}(https://console.rongcloud.io/agile/formwork/ticket/create) with necessary details like {App Key}, {User ID}, and {Issue Occurrence Time}.

34251

FILE_SAVED_FAILED

File save failed.

Troubleshooting: Check if the {Device Storage Space} is full. If the issue persists, submit a {Support Ticket}(https://console.rongcloud.io/agile/formwork/ticket/create) with necessary details like {App Key}, {User ID}, and {Issue Occurrence Time}.

34252

FILE_NOT_EXIST

File Not Exist.

Troubleshooting: Submit a {Support Ticket}(https://console.rongcloud.io/agile/formwork/ticket/create) with necessary details like {App Key}, {User ID}, and {Issue Occurrence Time}.

34253

FILE_SIZE_ERROR

File Length error.

Troubleshooting: Submit a {Support Ticket}(https://console.rongcloud.io/agile/formwork/ticket/create) with necessary details like {App Key}, {User ID}, and {Issue Occurrence Time}.

34254

DOWNLOAD_URL_INVALID

Download URL is invalid.

Troubleshooting: Submit a {Support Ticket}(https://console.rongcloud.io/agile/formwork/ticket/create) with necessary details like {App Key}, {User ID}, and {Issue Occurrence Time}.

34255

SLICE_INDEX_ERROR

Slice Index error.

Troubleshooting: Submit a {Support Ticket}(https://console.rongcloud.io/agile/formwork/ticket/create) with necessary details like {App Key}, {User ID}, and {Issue Occurrence Time}.

34256

UPLOAD_ID_INVALID

Upload ID is invalid.

Troubleshooting: Submit a {Support Ticket}(https://console.rongcloud.io/agile/formwork/ticket/create) with necessary details like {App Key}, {User ID}, and {Issue Occurrence Time}.

34257

INVALID_APP_KEY

App Key is invalid.

Troubleshooting: Ensure the {initWithAppKey:}(/ios-imlib/init) interface is called to initialize the SDK before connecting to IM, and the passed parameter is valid.

34259

INVALID_PARAMETER_RTCROOMID

The {rtcRoomID} parameter is invalid.

Troubleshooting: Check if the {rtcRoomID} passed to the interface is a non-empty {NSString} object.

34260

INVALID_PARAMETER_KEY

The {key} parameter is invalid.

Troubleshooting: Verify the parameter types in the {API DOC}(https://doc.rongcloud.cn/apidoc/imlibcore-ios/latest/zh_CN/documentation/rongimlibcore?language=objc).

34261

INVALID_PARAMETER_KEYS

The {keys} parameter is invalid.

Troubleshooting: Verify the parameter types in the {API DOC}(https://doc.rongcloud.cn/apidoc/imlibcore-ios/latest/zh_CN/documentation/rongimlibcore?language=objc).

34262

INVALID_PARAMETER_VALUE

The {value} parameter is invalid.

Troubleshooting: Check if the passed parameter is of type {NSString} and its length is between 0-4097 characters.

34263

INVALID_PARAMETER_ENTRIES

The {entries} parameter is invalid.

Troubleshooting: Check if the passed parameter is a non-empty {NSString} object.

34264

INVALID_PARAMETER_NOTIFICATION_EXTRA

The {notificationExtra} parameter is invalid.

Troubleshooting: Check if the passed parameter is of type {NSString} and its length is between 0-2048 characters.

34265

INVALID_PARAMETER_CHATROOM_MEMBER_ORDER

The {ChatRoomMemberOrder} parameter is invalid.

Troubleshooting: Check if the passed parameter belongs to {RC_ChatRoom_Member_Asc} or {RC_ChatRoom_Member_Desc}.

34266

INVALID_PARAMETER_TIMESTAMP_ORDER

The {TimestampOrder} parameter is invalid.

Troubleshooting: Check if the passed parameter belongs to the {RCTimestampOrder Enum}(https://doc.rongcloud.cn/apidoc/imlibcore-ios/latest/zh_CN/documentation/rongimlibcore/rctimestamporder/?language=objc).

34268

INVALID_PARAMETER_STATUS

The {status} parameter is invalid.

Troubleshooting: Check if the passed parameter belongs to the {RCUltraGroupTypingStatus Enum}(https://doc.rongcloud.cn/apidoc/imlibcore-ios/latest/zh_CN/documentation/rongimlibcore/rcultragrouptypingstatus?language=objc).

34271

MESSAGE_OBJECT_NAME_INVALID

The {objectName} parameter is invalid.

Troubleshooting: Check if the passed {objectName} is of type {NSString} and its length is between 0-129 characters.

34274

INVALID_PARAMETER_KEYWORD

The {keyword} parameter is invalid.

Troubleshooting: Check if the passed parameter is of type {NSString} and its length is between 0-1000 characters.

34275

INVALID_PARAMETER_OBJECTNAMELIST

The {objectName List} parameter is invalid.

Troubleshooting: Check if the passed parameter is a non-empty object.

34279

INVALID_PARAMETER_LIMIT

The {limit} parameter is invalid.

Troubleshooting: Verify the parameter types in the {API DOC}(https://doc.rongcloud.cn/apidoc/imlibcore-ios/latest/zh_CN/documentation/rongimlibcore?language=objc).

34280

INVALID_MESSAGE_DIRECTION

The {MessageDirection} parameter is incorrect.

Troubleshooting: Verify the parameter types in the {API DOC}(https://doc.rongcloud.cn/apidoc/imlibcore-ios/latest/zh_CN/documentation/rongimlibcore?language=objc).

34281

INVALID_MESSAGE_SENT_STATUS

The {SentStatus} parameter is incorrect.

Troubleshooting:

1. In a {Private Chat Session}, only messages with {SentStatus} as RECEIVED or READ can retrieve the delivery time.
2. In a {Group Chat Session}, only messages with {SentStatus} as SENT, RECEIVED, or READ can retrieve group message delivery-related methods.

34282

INVALID_PARAMETER_TARGETID_LIST

The {targetId List} parameter is invalid.

Troubleshooting: Check if the passed parameter is of type {NSArray} and its length is between 0-20.

34283

INVALID_PARAMETER_SPAN_MINUTES

The {span minutes} parameter is invalid.

Troubleshooting: Check if the passed parameter value is between 0-1440.

34286

RC_INVALID_ARGUMENT

The URL for navigation request is empty.

Troubleshooting: Submit a {Support Ticket}(https://console.rongcloud.io/agile/formwork/ticket/create) with necessary details like {App Key}, {User ID}, and {Issue Occurrence Time}.

34287

INVALID_PARAMETER_CONVERSATION_IDETIFIER_LIST

The {ConversationIdentifier} passed by the developer is invalid.

Troubleshooting:

1. Check if the passed parameter is of type {NSArray}.
2. The array length should be between 1-20.
3. The array elements should be of {RCConversationIdentifier Type}(https://doc.rongcloud.cn/apidoc/imlibcore-ios/latest/zh_CN/documentation/rongimlibcore/rcconversationidentifier?language=objc).

34288

INVALID_PARAMETER_CLEAR_MESSAGE_OPTION_LIST

The {ClearMessageOption} passed by the developer is invalid.

Troubleshooting:

1. Check if the passed parameter is of type {NSArray}.
2. The array length should be between 1-20.
3. The array elements should be of {RCClearMessageOption Type}(https://doc.rongcloud.cn/apidoc/imlibcore-ios/latest/zh_CN/documentation/rongimlibcore/rcclearmessageoption?language=objc).

34289

INVALID_PARAMETER_START_MESSAGEUID

The {startMessageUID} parameter is invalid.

Troubleshooting: Check if the passed parameter length is between 0-64.

34290

INVALID_PARAMETER_END_MESSAGEUID

The {endMessageUID} parameter is invalid.

Troubleshooting: Check if the passed parameter length is between 0-64.

34291

RC_READ_RECEIPT_V4_NOT_SUPPORT

The {V4 Read Receipt Feature} is not supported.

Troubleshooting:

1. Currently, only {Global IM UIKit} supports the {V4 Read Receipt Feature}.
2. If the issue persists with {Global IM UIKit}, submit a {Support Ticket}(https://console.rongcloud.io/agile/formwork/ticket/create) with necessary details like {App Key}, {User ID}, and {Issue Occurrence Time}.

34292

RC_READ_RECEIPT_V4_UPDATE_NOT_SUPPORT

Updating {V4 Read Receipt Feature} information is not supported.

Troubleshooting: Submit a {Support Ticket}(https://console.rongcloud.io/agile/formwork/ticket/create) with necessary details like {App Key}, {User ID}, and {Issue Occurrence Time}.

34296

RC_DIRECTIONAL_MESSAGE_INVALID_CONVERSATION_TYPE

The {Conversation Type} passed when sending a {Directional Message} is not supported.

Troubleshooting: Currently, only {ConversationType_GROUP} and {ConversationType_ULTRAGROUP} are supported. For details, refer to the documentation.

34300

RC_REQUEST_INTERCEPTOR_NULL_EXCEPTION

The object returned by the {Multimedia Upload} and {Download Interceptor} processing interface is empty.

Troubleshooting: Ensure the {requestHandler} return value in the {RCDownloadInterceptor Protocol} implementation is non-empty.

34301

RC_DB_NOT_INIT

Database Not Initialized.

Troubleshooting: Check if the {SDK Initialization} and connection are successful. If the issue persists, submit a {Support Ticket}(https://console.rongcloud.io/agile/formwork/ticket/create) with necessary details like {App Key}, {User ID}, and {Issue Occurrence Time}.

34303

RC_DB_SQL_ERROR

Database SQL Execution Error.

Troubleshooting: Submit a {Support Ticket}(https://console.rongcloud.io/agile/formwork/ticket/create) with necessary details like {App Key}, {User ID}, and {Issue Occurrence Time}.

34304

RC_DB_DATA_NOT_FOUND

Query data does not exist.

排查建议: Submit a Ticket to contact us, and include necessary information such as App key, 用户 ID, 问题发生时间, etc.

34305

RC_NET_DATA_ERROR

Network data parsing failed.

排查建议: Submit a Ticket to contact us, and include necessary information such as App key, 用户 ID, 问题发生时间, etc.

34306

INVALID_PARAMETER_SUBSCRIBE_TYPE

The subscribeType passed in the subscription event is invalid.

排查建议: Check if the passed subscribeType belongs to the RCSubscribeType enum.

34307

INVALID_PARAMETER_SUBSCRIBE_EXPIRY

The subscription duration passed in the subscription event is invalid.

排查建议: The passed value is a timestamp, with the minimum value being 60 and the maximum value being 30 * 24 * 60 * 60.

34308

INVALID_PARAMETER_SUBSCRIBE_PUBLISHER_USERIDS

The list of subscribed users passed in the subscription event is empty or the data type is invalid.

排查建议:

1. Check if the passed parameter is of type NSArray.
2. The length should be within the range of 0 - 201.
3. The elements in the array must be of type NSString, with a length within the range of 0 - 65.

34309

INVALID_PARAMETER_SUBSCRIBE_PAGESIZE

The page size passed in the subscription event is invalid.

排查建议: Check if the value of the page size passed in the interface is within the range of 0 - 201.

34312

INVALID_PARAMETER_USER_PROFILE

The parameter userProfile is invalid.

排查建议: Check if the RCUserProfile passed in the interface is a non-null object.

34313

INVALID_PARAMETER_USER_PROFILE_VISIBILITY

The parameter userProfileVisibility is invalid.

排查建议: Check if the passed parameter belongs to the RCUserProfileVisibility type.

34314

INVALID_PARAMETER_EXTRA

The parameter extra is invalid.

排查建议: Check if the passed parameter is of type NSString.

34318

INVALID_PARAMETER_GROUP_INFO

The parameter GroupInfo passed in the developer interface call is invalid.

排查建议: Check if the GroupInfo passed in the interface is a non-null object.

34319

INVALID_PARAMETER_GROUP_ID

The parameter groupId passed in the developer interface call is invalid.

排查建议:

1. Check if the passed groupId is of type NSString.
2. It should consist of letters (case-insensitive), numbers, and the symbols +, =, -, _, |, :, with a length within the range of 0 - 65.

34320

INVALID_PARAMETER_GROUP_NAME

The parameter groupName passed in the developer interface call is invalid.

排查建议:

1. Check if the passed groupName is of type NSString.
2. After removing spaces and line breaks, the length should be within the range of 0 - 65.

34321

INVALID_PARAMETER_GROUP_IDS

The parameter groupIds passed in the developer interface call is invalid.

排查建议:

1. Check if the passed groupIds is of type NSArray, and if the objects stored inside are of type NSString.
2. The length should be within the range of 0 - 65.
3. It should consist of letters (case-insensitive), numbers, and the symbols +, =, -, _, |, :, with a length within the range of 0 - 65.

34322

INVALID_PARAMETER_GROUP_MEMBER_ROLE

The parameter GroupMemberRole passed in the developer interface call is invalid.

排查建议: Check if the passed parameter belongs to the RCGroupMemberRole type.

34323

INVALID_PARAMETER_GROUP_APPLICATION_STATUS

The parameter GroupApplicationStatus passed in the developer interface call is invalid.

排查建议:

1. Check if the passed parameter is of type NSArray, and if the objects stored inside are of type NSNumber.
2. The length should not be 0.
3. The elements in the array must conform to the RCGroupApplicationStatus enum definition.

34324

INVALID_PARAMETER_GROUP_APPLICATION_DIRECTION

The parameter GroupApplicationDirection passed in the developer interface call is invalid.

排查建议:

1. Check if the passed parameter is of type NSArray, and if the objects stored inside are of type NSNumber.
2. The length should not be 0.
3. The elements in the array must conform to the RCGroupApplicationDirection enum definition.

34325

INVALID_PARAMETER_NICK_NAME

The parameter nickname passed in the developer interface call is invalid.

排查建议:

1. Check if the passed parameter is of type NSString.
2. After removing spaces and line breaks, the length should be within the range of 0 - 65.

34326

INVALID_PARAMETER_REASON

The parameter reason passed in the developer interface call is invalid.

排查建议:

1. Check if the passed parameter is of type NSString.
2. After removing spaces and line breaks, the length should be within the range of 0 - 129.

34327

INVALID_PARAMETER_REMARK

The parameter remark passed in the developer interface call is invalid.

排查建议:

1. Check if the passed parameter is of type NSString.
2. After removing spaces and line breaks, the length should be within the range of 0 - 65.

34328

INVALID_PARAMETER_PAGING_QUERY_OPTION

The parameter PagingQueryOption passed in the developer interface call is invalid.

排查建议: Check if the RCPagingQueryOption passed in the interface is a non-null object.

34329

NET_DATA_IS_SYNCHRONIZING

Data is being synchronized.

排查建议: Based on the actual situation of the business layer data, delay the call to get the corresponding content again. If the issue persists, submit a Ticket to contact us, and include necessary information such as App key, 用户 ID, 问题发生时间, etc.

34330

INVALID_PARAMETER_QUERY_FRIENDS_DIRECTION_TYPE

The parameter QueryFriendsDirectionType passed in the developer interface call is invalid.

排查建议: Check if the passed parameter belongs to the RCQueryFriendsDirectionType type.

34331

INVALID_PARAMETER_DIRECTION_TYPE

The parameter DirectionType passed in the developer interface call is invalid.

排查建议: Check if the passed parameter belongs to the RCDirectionType type.

34332

INVALID_PARAMETER_FRIEND_APPLICATION_TYPE

The parameter FriendApplicationType passed in the developer interface call is invalid.

排查建议:

1. Check if the passed parameter is of type NSArray, and if the objects stored inside are of type NSNumber.
2. The elements in the array must conform to the RCFriendApplicationType enum definition.

34333

INVALID_PARAMETER_FRIEND_APPLICATION_STATUS

The parameter FriendApplicationStatus passed in the developer interface call is invalid.

排查建议:

1. Check if the passed parameter is of type NSArray, and if the objects stored inside are of type NSNumber.
2. The elements in the array must conform to the RCFriendApplicationType enum definition.

34334

INVALID_PARAMETER_FRIEND_ADD_PERMISSION

The parameter FriendAddPermission passed in the developer interface call is invalid.

排查建议: Check if the passed parameter belongs to the RCFriendAddPermission type.

APNs Push Notification Status Codes

Below are the error codes, causes, and troubleshooting steps you may encounter during the push notification testing process after uploading the APNs push certificate in the Console.

Error Code	Cause	Action
5, 8	Incorrect deviceToken information.	Check if the device is jailbroken, ensure the parameters passed to setDeviceToken are correct, and verify that the provisioning profile used by Xcode during packaging matches the current environment.
52	The UserId does not exist in the current environment. Confirm if the server connection is successful and if the App Key used in init corresponds to the correct environment.	The success Block of connectWithToken will return the currently logged-in UserId. Verify if it matches the one used in your push test.
53	The uploaded push certificate is empty.	Check and re-upload the certificate, and ensure the BundleID matches the one in the certificate.
54, 62	Issues with the uploaded certificate or its password.	Verify the certificate password, check and re-upload the certificate, and ensure the BundleID matches the one in the certificate.
55	The userId is not currently logged in on an iOS device.	Check if the login was successful on an iOS device and if there is multi-device login for the same userId.
57	Failed to send Apple Push.	SSL parsing error, re-upload the certificate.
2, 56	The userId has no deviceToken information set.	Check if the device is jailbroken, if the user has allowed notifications for the app, if remote push permissions were requested, and if setDeviceToken was set correctly.
58	Failed to parse the original parameters.	Contact us to resolve the issue promptly.
60	Socket exception.	Internal error, resend.
61	The userId has push notifications blocked.	Check if the client has blocked push functionality (if you have multiple clients or apps using the same AppKey, verify all client codes to ensure push is not blocked).
3, 4, 6, 7, 64	Network issues caused the push to fail. Please try again.	Network issue, retry.
0, 1, 10, 255, 59	Apple APNS server service exception.	Try again after some time.
66	The uploaded certificate does not match the current environment.	Check and re-upload the certificate.
67	The password for the uploaded certificate is incorrect. Verify your certificate and password.	Check the certificate and password, re-upload the certificate, or enter the correct password.
68	The Bundle ID in the developer platform does not match the one in the certificate. Please check.	Verify the BundleID in the certificate and the one entered.
70	VoIP Push Token is empty.	Confirm if the VoIP Push Token is empty.
73	No user information found. This userId has not obtained a RC Token.	Reacquire the user Token.
74	The uploaded certificate's package name does not match the configured package name.	Check if the uploaded certificate's package name matches the configured package name.
75	The uploaded certificate contains a BundleId with a wildcard.	According to Apple's requirements, apps using wildcards cannot use APNs remote push.
1050	APNS timeout. You may receive the push message with a delay or it may fail.	Network issue, retry.