Why do I encounter error code 30001?
There are several possible reasons for the occurrence of error code 30001:
1. A request parameter is invalid.
2. User A initiates a friend request to user B, but user B is already in user A’s friend list.
3. User A initiates a friend deletion request to user B, but user B is not in user A’s friend list.
4. User A initiates a friend update request to update friend B’s contacts data, but friend B is not in user A’s friend list.
5. User A initiates a request to fetch the contacts data of friend B, but friend B is not in user A’s friend list.
6. User A initiates a blocklist request to user B, but user B is already in user A’s blocklist.
7. User A initiates a request to remove user B from the blocklist, but user B is not in user A’s blocklist.
When the Chat backend returns an error code, it also returns the detailed error information, and users can identify the cause of the error based on the error information.
What should I do if error code 30004/40004 is returned when the RESTful API of the profile/contacts system is called?
The request packet of the profile/contacts system contains a From_Account field, which is used to indicate the request sender. If the value of the From_Account field in the request packet is inconsistent with the actual sender, the Chat backend considers that the request was initiated by the app backend. In this case, the backend checks whether the request sender has app admin permissions. If the actual sender is not an admin, error 30004/40004 is returned.
To allow non-friend users to send messages, disable the contacts for one-to-one chat message verification in the Chat console. To forbid non-friend users to send messages, enable the verification. It takes 5 minutes for the setting to take effect. Why don't non-friend avatar or nickname updates reflect in real time in own session list and message list?