Rongyun integration error code summary

Rongyun integration error code summary

Rongyun integration error code summary

Recently integrated Rongyun IM SDK, an error code was encountered during the process, then you need to go to the SDK header file to find the corresponding error code to check the reason. I have sorted out the following for everyone, I hope to help you, if you have any questions, you can contact Rongyun technology:

30007: The navigation HTTP request failed. Suggestion: Change the network environment. If it cannot be solved, contact the server for troubleshooting (especially private cloud)':

31002: AppKey is wrong. Please check whether the AppKey you are using is correct

30010: Failed to create Socket connection. Suggestion: Generally, the network is not good, you need to change the network to try.

31004: Token is invalid. Suggestions: 1. the token is wrong, please check whether the AppKey used by the client to initialize and the AppKey used by your server to obtain the token are consistent; the second is the token expired because you set the token expiration time in the developer background, and you need to request your The server obtains the token again and establishes a connection with the new token again

31005: AppKey and Token do not match. Suggestion: Please check whether the AppKey and Token you use are correct and match. There are generally three reasons. The first is the token error. Please check whether the AppKey used by the client to initialize and the AppKey used by your server to obtain the token are the same; the second is the token expired because you set the token expiration time in the developer background, and you need to request your server to restart Get the token and use the new token again. The third is that the App verification failed because you have set the App verification in the developer background to establish a connection.

31007: The BundleID is incorrect. Suggestion: Please check whether the BundleID of your App is correct

31008: AppKey is blocked or deleted. Suggestion: Please check whether the AppKey you are using is blocked or deleted.

31009: The user is banned. Suggestion: Check whether the Token you are using is correct, and whether the corresponding UserId is blocked

31010: The user was kicked offline. Suggestion: The current user logged in on another device, and this device was kicked offline'

31023: The user logs in on other devices. Suggestion: The current user logs in on other devices during the reconnection process

33001: SDK is not initialized. Suggestion: Before using any function of the SDK, you must first init

33003: The parameter passed in when the developer interface is called is incorrect. Suggestion: Please check the parameter types and values passed in when calling the interface

34001: Connection already exists. Suggestion: After calling connect, you only need to call connect again when the token is wrong or kicked off or the user logs out. In other cases, the SDK will automatically reconnect, and the application does not need to call connect multiple times to maintain the connection

34005: The connection environment is incorrect. Recommendation: Rongyun public cloud SDK cannot connect to the private cloud environment. Please confirm the environment to be connected and use the correct SDK version

34006: Connection timed out. Suggestion: When calling the connectWithToken:timeLimit:dbOpened:success:error: interface and timeLimit is a valid value, the SDK returns this error if it has not successfully connected within the timeLimit time

30011: The Socket is disconnected. Suggestion: Socket connection is disconnected. There are two main situations. One is that the Socket is disconnected by the server after the user actively calls disconnect; the other is that the Socket is disconnected due to intermediate routing reasons.

30008: Navigation HTTP return data format is wrong. Suggestion: The SDK will automatically reconnect the temporary error code for establishing a connection, and the developer does not need to deal with it.

30004: Navigation HTTP sending failed, whether to set ATS. Suggestion: If this error occurs occasionally, the SDK will automatically reconnect, and the developer does not need to deal with it. If this error persists, it should be that you have not set up the ATS. ATS only uses the HTTPS protocol by default. When the HTTP protocol is forbidden, the SDK will always give 30004 errors. You can refer to the ATS setting instructions in the iOS development documentation. The link is as follows: support.rongcloud.cn/ks/OTQ1

30012: PING failed. Suggestion: The SDK will automatically reconnect the temporary error code for establishing a connection, and the developer does not need to deal with it.

30013: PING timeout. Suggestion: The SDK will automatically reconnect the temporary error code for establishing a connection, and the developer does not need to deal with it.

30014: Failed to send signaling. Suggestion: The SDK will automatically reconnect the temporary error code for establishing a connection, and the developer does not need to deal with it.

31000: Connection ACK timed out. Suggestion: The SDK will automatically reconnect the temporary error code for establishing a connection, and the developer does not need to deal with it.

31001: The signaling version is wrong. Suggestion: ask Rongyun's technical staff

31003: The server is currently unavailable. Suggestion: The SDK will automatically reconnect the temporary error code for establishing a connection, and the developer does not need to deal with it.

31006: Connection redirection. Suggestion: The SDK will automatically reconnect the temporary error code for establishing a connection, and the developer does not need to deal with it.

32061': Connection refused. Suggestion: The SDK will automatically reconnect the temporary error code for establishing a connection, and the developer does not need to deal with it.

20604: The frequency of sending messages is too high. Only 5 messages are allowed to be sent in 1 second. Suggestion: add a delay when sending multiple messages

20607: The request exceeds the call frequency limit. Please try again later. Suggestion: Don't call the interface too frequently

21406: The current user is not in the discussion group

22406: The current user is not in the group. Suggestion: Go to the corresponding service of Rongyun Developer's back-end API call module to query

22408: The current user has been banned in the group. Suggestion: ask the developer server staff to confirm whether they are in the group

23406: The current user is not in the chat room. Suggestion: Go to the corresponding service of Rongyun developer's back-end API call module to check and verify

23408: The current user has been banned in this chat room. Suggestion: Go to the corresponding service of Rongyun developer's back-end API call module to check and verify

23409: The current user has been kicked out and banned from joining the chat room. The banned time depends on the time passed in when the server calls the kick-out interface.

23410: The chat room does not exist. Suggestion: Go to the corresponding service of Rongyun developer's back-end API call module to check and verify

23411: The chat room has over-restricted members. By default, there is no limit on the number of people in the chat room. Developers can submit a ticket to limit the number of chat rooms for an Appkey. After setting, if the number of people exceeds the limit, the error code will be displayed

23412: The chat room interface parameter is invalid. Please confirm whether the parameter is empty or valid

23414: The chat room cloud storage service is not activated. Suggestion: go to the Rongyun developer's background

23423: Exceeds the maximum number of state settings for the chat room, a chat room can set up to 100 by default

23424: Illegal overwriting of the status value in the chat room, the status already exists, and there is no permission to overwrite. Suggestion: Only the creator can modify this value. If you must modify it, you need to call the forceSetChatRoomEntry:key:value:sendNotification:autoDelete:notificationExtra:success:error: interface in RCIMClient. For details, please check the API in RCIMClient

23425: Exceeding the frequency of state setting in the chat room, 1 chat room can set and delete the state up to 100 times per second. Recommendation: reduce the frequency of settings and deletions

23426: The chat room status storage function is not activated, please contact Business Opening

23427: The chat room status value does not exist

26002: There is a problem when the operation is synchronized with the server. It may be caused by the operation too frequently. If this error occurs, please delay 0.5s and try again

34004: The chat room status is not synchronized. When you just join the chat room, call the Get KV interface. In extreme cases, the local data and the server may not be synchronized. It is recommended to delay for a while before obtaining it.

30001: The current connection is unavailable (the connection has been released), it can only indicate that the current connection is disconnected, and the specific reason needs to be analyzed by other error codes

30002: The current connection is unavailable. It can only indicate that the current connection is disconnected. The specific reason needs to be analyzed by other error codes. Suggestion: The network may be unavailable, please switch the network to try

30003: The client sends a message request, and the Rongyun server responds with a timeout. Suggestion: There may be a problem with the server

33002: Database error, the reasons for the error: 1. It is necessary to ensure that the connection to the cloud integration is successful and the database is opened before calling the business interface, such as sending a message. 2. The userId contains special characters.

33003: The parameter passed in when the developer interface is called is incorrect. Suggestion: Please check the parameter types and values passed in when calling the interface

33007: Historical message cloud storage service has not been opened. The service can be opened in the Rongyun developer background

30016: The message size exceeds the limit, and the message body (content after serialization into json format) can be up to 128k bytes. Recommendation: reduce the size of the message body to avoid exceeding 128 k

25101: The parameter of the withdrawal message is invalid. Please confirm whether the withdrawal message parameters are filled in correctly

26001: Push setting parameter is invalid. Please confirm whether the push parameter is filled in correctly

20605: Operation is prohibited. This error code has been deprecated

20606: The operation is not supported. Only the private cloud is valid, and this operation is disabled on the server.

21501: The sent message contains sensitive words (the sender fails to send, the receiver will not receive the message)

21502: The sensitive word in the message has been replaced (the receiver can receive the replaced message

34002: The length of the small video exceeds the limit. The default maximum length of the small video is 2 minutes. Recommendation: The video should not exceed 2 minutes

34003: GIF message file size exceeds the limit, the default GIF file size limit is 2 MB

34007: The query public service information does not exist, please confirm whether the query public service type and public service id match

34008: The message cannot be expanded. When the message is sent, the attribute canIncludeExpansion of the RCMessage object can be set to YES to be expanded. Suggestion: Set the property canIncludeExpansion of the RCMessage object to YES

34009: Message extension failure, usually caused by network reasons, please make sure that the network is in good condition and Rongyun SDK is connected normally

34010: The message expansion size exceeds the limit, the default message expansion dictionary key length does not exceed 32, the value length does not exceed 64, the maximum number of extensions for a single setting is 20, and the total number of message extensions cannot exceed 300

34011': media message media file http upload failed