Class

• When to call: Before calling other member functions, you must call this API to create a ZIM example.

Usage restrictions: Currently only one instance is supported, repeated calls will return [null].

Precautions:

1. Currently, the [Create] function can only create one instance at most. If it is called multiple times, only the first one will return a valid instance, and the rest will be [null]. The developer should save the ZIM instance by himself, and ensure that the life cycle of the instance is available in the process of using the ZIM business function; or after calling [Create], he can use [GetInstance] to obtain its singleton object and call other member functions.

2. If you use this function to create an instance, you must pass in both AppID and AppSign (exclude Web platform).

Scope of Impact: Failure to call this function will prevent other member functions from being called.

Platform difference: When calling this function on the Android platform, in addition to the AppID, the Application class object must also be passed in.

• Use cases: 1. When the SDK is running, the developer finds that it does not match the expected situation and submits the problem and related logs to the ZEGO technical staff for locating. The ZEGO technical staff may need the information of the engine version to assist in locating the problem.

2. Developers can also collect this information as the version information of the engine used by the app, so that the SDK corresponding to each version of the app on the line.

When to call : It can be called at any time.

• When to call: You must call [Create] to create an instance before calling this function to obtain a singleton object, otherwise it will return [null].

Related interface: [Create].

• Default value: /storage/Android/data/[Application ID]/files/ZIMLogs
• When to call: It must be called before [Create].

If the developer calls after [Create], the SDK will save this configuration until the next time [create] takes effect.

Life cycle: Set before calling [Create], and take effect when calling [Create]. If the developer does not set a new log configuration in the next [create], the previous configuration will still take effect.

Platform difference: The default path of different platforms is different, please refer to the default value.

Related reference: For details, please refer to https://doc-zh.zego.im/faq/IM_sdkLog?product=IM&platform=all.

• Default value: Android：/storage/Android/data/[packageName]/files/ZIMCaches iOS：/Library/Caches/ZIMCaches macOS：（sandbox）/Library/Containers/[Bundle ID]/Data/Library/Caches/ZIMCaches / ~/Library/Caches/ZIMCaches Windows：C:\Users[Your UserName]\AppData[App Name]ZEGO.SDK\ZIMCaches

Call timing: It must be called before [create].

If the developer calls after [create], the SDK saves the configuration until it takes effect the next time [Create] is invoked.

• Related callbacks: In addition to getting the login result in the callback parameter, the developer will also receive the [onConnectionStateChanged] callback during the login request and after the login is successful/failed to determine the current user's login status.

Life cycle: Set before calling [create] and takes effect when calling [create]. If the developer does not set the new caches configuration the next time [create] is created, the previous configuration will still take effect.

Platform difference: The default path varies with platforms. Please refer to the default value.

• Related callbacks: In addition to getting the login result in the callback parameter, the developer will also receive the [onConnectionStateChanged] callback during the login request and after the login is successful/failed to determine the current user's login status.

FAQ: How is the RTC login different from ZEGO's? RTC login refers to the login to the room, ZIM login to the account.

Related reference: For details, please refer to Authentication (https://docs.zegocloud.com/article/13772).

• Related callbacks: In addition to getting the login result in the callback parameter, the developer will also receive the [OnConnectionStateChanged] callback during the login request and after the login is successful/failed to determine the current user's login status.

• Use cases: When you need to create a multi-person chat scene, you can create and join a room by this API.
• When to call: This function must be called through the instance after calling [Create] to create the instance.
• Caution: After the developer receives the [OnTokenWillExpire] callback, the developer needs to request the authentication server to regenerate a token in time.

• When to call /Trigger: It is available only after calling [Create] to create the instance and then calling [Login] to login.
• Related callbacks: [ZIMUsersInfoQueriedCallback].

Usage restrictions: No more than 10 userids can be queried by invoking the interface at a time. If the interface is invoked multiple times within 10 seconds, the total number of userids queried cannot exceed 10.

• When to call: After the user is logged in.

This interface does not support modifying user names in rooms.

• Privacy reminder: Try not to pass in sensitive information involving personal privacy, including but not limited to mobile phone numbers, ID numbers, passport numbers, real names, etc.
• Related callbacks: [ZIMUserNameUpdatedCallback].
• Related APIs: [updateUserExtendedData] and [QueryUsersInfo].

• When to call: After the user is logged in.
• Privacy reminder: Try not to pass in sensitive information involving personal privacy, including but not limited to mobile phone numbers, ID numbers, passport numbers, real names, etc.
• Related callbacks: [ OnUserNameUpdatedCallback ].
• Related APIs: [ UpdateUserName] and [ QueryUsersInfo ].

• Related callbacks: Developers can get the upload results through the callback parameter.

• Use cases: This function must be called from the instance after it has been created by calling [Create].
• When to call: After invoking [Logout], you can no longer use ZIM's chat, room, send and receive, and other functions. To use the ZIM service again, the developer must call [Login] to login again.
• Caution: Upon logout, the developer will receive the [OnConnectionStateChanged] callback with the login state being [Disconnected].

• When to call: It can be called after creating a ZIM instance through [create].

The call invitation has a timeout period, and the call invitation will end when the timeout period expires.

• Related callbacks: [ZIMCallInvitationSentCallback].

• When to call: It can be called after creating a ZIM instance through [Create].

Canceling the call invitation after the timeout period of the call invitation expires will fail.

• Related callbacks: [ZIMCallCancelSentCallback].

• When to call: It can be called after creating a ZIM instance through [Create].

The callee will fail to accept an uninvited callid.

• Related callbacks: [ZIMCallAcceptanceSentCallback].

• When to call: It can be called after creating a ZIM instance through [Create].

The callee will fail to reject the uninvited callid.

• Related callbacks: [ZIMCallRejectionSentCallback].

• When to call: After a call is established, users whose call status is accept can call this interface.

The callee will fail to quit the uninvited callid.

• Related callbacks: [ZIMCallQuitSentCallback].

• When to call: The call was in advanced mode and the user status was Accepted.

User calls that are not in the call will fail. ZIM SDK Does not have service logic after the call ends, and developers can customize the development logic after the end.

• Related callbacks: [ZIMCallEndSentCallback].

• When to call: After calling [callInvite] to initiate a call invitation in advanced mode or after the called party accepts the advanced mode call invitation.

User calls that are not in the call will fail. ZIM SDK has no relevant business logic after accepting. Developers can customize the development logic after adding calls. By default, a call can contain a maximum of 9 users.

• Related callbacks: [ZIMCallingInvitationSentCallback].

• When to call: Run [Create] to create a ZIM instance, which can be invoked after login.
• Related callbacks: [ZIMCallInvitationListQueriedCallback].

• Use cases: You can use this interface to create a chat scenario and join a group.
• When to call: After you create a ZIM instance with [create] and login with [login].
• Impacts on other APIs: You can use [JoinGroup] to join a group, [LeaveGroup] to leave a group, or [DismissGroup] to dismiss a group.
• Related callbacks: The result of creating the group is obtained through the [ZIMGroupCreatedCallback] callback.
• Related APIs: Call [JoinGroup] to join a group, call [LeaveGroup] to leave a group, call [DismissGroup] to dismiss a group.

• Related callbacks: [ZIMGroupsSearchedCallback].

• Related callbacks: [ZIMGroupMembersSearchedCallback].

• Use cases: You can use this interface to create a chat scenario and join a group.
• When to call /Trigger: The ZIM instance can be invoked after being created by [create] and logged in.
• Caution: Available after login, unavailable after logout. UserIDs can have a maximum of 100 users and a group can have a maximum of 500 users.
• Related callbacks: The result of creating the group is obtained through the [ZIMGroupCreatedCallback] callback.
• Related APIs: You can use [JoinGroup] to join a group, [LeaveGroup] to leave a group, or [DismissGroup] to dismiss a group.

• Use cases: This interface is used to join a group in a chat scenario.
• When to call /Trigger: The ZIM instance can be invoked after being created by [create] and logged in.
• Caution: Available after login, unavailable after logout. If you have joined a group, the join succeeds.
• Related callbacks: To get the result of joining the room, call [ZIMGroupJoinedCallback].
• Related APIs: You can use [CreateGroup] to create a group, [LeaveGroup] to leave a group, or [DismissGroup] to dismiss a group.

• Use cases: This interface is used to exit a chat group.
• When to call /Trigger: It can be invoked after a ZIM instance is created through [create] and logged in.
• Caution: When the group owner quits the group, the identity of the group owner will be automatically transferred to the earliest member who joined the group. When all members exit the group, the group is automatically dissolved.
• Impacts on other APIs: You can use [CreateGroup] to create a group, [JoinGroup] to join a group, or [DismissGroup] to dismiss a group.
• Related callbacks: The result of leaving the room can be obtained by the [ZIMGroupLeftCallback] callback.

• Use cases: After you create a chat group, you do not need to use this interface to dissolve the group.
• When to call /Trigger: This parameter can be called after a group is created by using [CreateGroup].
• Caution: A non-group owner cannot dissolve a group.
• Related callbacks: Through callback can get [ZIMGroupDismissedCallback] dissolution results of the room, through [onGroupStateChanged] listen callback can get the room status.
• Related APIs: You can use [CreateGroup] to create a group, [JoinGroup] to join a group, and [LeaveGroup] to leave a group.

• Use cases: You can use this method to remove one or more users from the group.
• When to call /Trigger: The ZIM instance can be invoked after being created by [Create] and logged in.
• Caution: This interface does not require the peer's consent or the peer's online status. It cannot accept group-related callbacks after being kicked out. History messages and sessions remain after being kicked out and can still enter the group.
• Related callbacks: Through the callback [ZIMGroupMemberKickedCallback] can get the user kicked out the results of the group.
• Related APIs: You can invite a target user into a group through [InviteUsersIntoGroup].

• Use cases: You can use this method to invite one or more users to the group.
• When to call /Trigger: The ZIM instance can be invoked after being created by [create] and logged in.
• Caution: This interface does not require the peer's consent or the peer's online status.
• Related callbacks: Through the callback [ZIMGroupUsersInvitedCallback] can get the user invited to the results of the group.
• Related APIs: You can kick out a target user into a group through [KickGroupMembers].

• Use cases: In a group chat scenario, you can transfer the group master through this interface.
• When to call /Trigger: The ZIM instance can be invoked after being created by [Create] and logged in.
• Related callbacks: Through the callback [ZIMGroupOwnerTransferredCallback] can get the result of the transfer of the group manager.

• Use cases: After creating a group, you need to change the group name.
• When to call /Trigger: The ZIM instance can be invoked after being created by [Create] and logged in.
• Related callbacks: Through the callback [ZIMGroupNameUpdatedCallback] can get the result of the change of name, through [OnGroupNoticeUpdated] can get update group name information.

• Related callbacks: The result of changing the group name can be obtained through the [ZIMGroupAvatarUrlUpdatedCallback] callback, and the updated group avatar information can be obtained through the [OnGroupAvatarUrlUpdated] callback.

• Use cases: You need to update the group bulletin in the group.
• When to call /Trigger: The ZIM instance can be invoked after being created by [create] and logged in.
• Related callbacks: Through callback [ZIMGroupNoticeUpdateCallback] can get update group of the results announcement, announcement by [OnGroupNoticeUpdated] can get update group information.

• Use cases: You need to obtain group information for display.
• When to call /Trigger: The ZIM instance can be invoked after being created by [Create] and logged in.
• Related callbacks: Through the callback [ZIMGroupInfoQueriedCallback] can query the result of the group information.

• Use cases: You need to get a list of groups to display.
• When to call /Trigger: The ZIM instance can be invoked after being created by [Create] and logged in.
• Related callbacks: Through the callback [ZIMGroupListQueiedCallback] can get a check list of all current group results.

• Use cases: Added extended field information about group description, such as group family, label, and industry category.
• When to call /Trigger: The ZIM instance can be invoked after being created by [Create] and logged in.
• Related callbacks: Through the callback [ZIMGroupAttributesOperatedCallback] can get the result of the set of attributes.
• Related APIs: [DeleteGroupAttributes] can be used to deleteGroupAttributes, [QueryGroupAttributes] can be used to queryGroupAttributes, [QueryAllGroupAttributes] can be used to queryAllGroupAttributes.

• Use cases: Deleted the extended field of the group description.
• When to call /Trigger: The ZIM instance can be invoked after being created by [create] and logged in.
• Related callbacks: Through the callback [ZIMGroupAttributesOperatedCallback] can delete the result of the group of attributes.
• Related APIs: You can use [SetGroupAttributes] to setGroupAttributes, [QueryGroupAttributes] to queryGroupAttributes, and [QueryAllGroupAttributes] to queryAllGroupAttributes.

• Use cases: You need to query the scenarios to display the specified group attributes.
• When to call /Trigger: After creating a ZIM instance with [Create] and logging in with [Login].
• Related callbacks: Through the callback [ZIMGroupAttributesQuriedCallback] can get query attributes of the specified group of results.
• Related APIs: [QueryAllGroupAttributes] Queries all group attributes.

• Use cases: Scenarios where all group attributes need to be queried.
• When to call /Trigger: The ZIM instance can be invoked after being created by [Create] and logged in.
• Related callbacks: Through callback can get query [ZIMGroupAttributesQuriedCallback] all the results of the group of attributes.
• Related APIs: [QueryGroupAttributes] Queries the attributes of the specified group.

• Use cases: The ZIM instance can be invoked after being created by [Create] and logged in.
• When to call /Trigger: If the primary role of a group is 1 and the default role of other members is 3, you can invoke this interface to change the role.
• Caution: The role of the group owner is 1, the role of the administrator is 2, and the role of the normal member is 3. You can modify it by calling this interface, but the role cannot be changed to 1. If you need to customize the role, it is recommended to set the value to 100 or higher, and its permissions will be the same as those of normal members.
• Related callbacks: Through the callback [ZIMGroupMemberRoleUpdatedCallback] can be set up to get the results of the group of members of the role.

• Use cases: Nicknames need to be set for group members.
• When to call /Trigger: The ZIM instance can be invoked after being created by [Create] and logged in.
• Caution: A group member nickname can contain a maximum of 100 characters.
• Related callbacks: Through the callback [ZIMGroupMemberNicknameUpdatedCallback] can be set up to get the results of the group members nickname.

• Use cases: You need to obtain the specified group member information for display or interaction.
• When to call /Trigger: The ZIM instance can be invoked after being created by [Create] and logged in.
• Related callbacks: Through the callback [ZIMGroupMemberInfoQueriedCallback] can get the query specifies the result of group membership information.

• Use cases: You need to obtain the specified group member list for display or interaction.
• When to call /Trigger: The ZIM instance can be invoked after being created by [Create] and logged in.
• Related callbacks: Through the callback [ZIMGroupMemberListQueriedCallback] can query the result of the group member list.

• When to call: The ZIM instance can be invoked after being created by [Create] and logged in.
• Related callbacks: [ZIMGroupMemberCountQueriedCallback].

• Use cases: When you need to know the relevant information of the specified conversation, you can call this interface to obtain the data source.
• When to call /Trigger: Can be invoked after login.
• Related callbacks: [ZIMConversationQueriedCallback].

• Use cases: This interface can be invoked to get the data source when you need to display an existing message session after logging in.
• When to call /Trigger: Can be invoked after login.
• Caution: NextConversation is the riveting point of the query message, which can be null for the first query. In subsequent query, the earliest conversation can be used as nextConversation to query earlier sessions. In paging query, Count in [ZIMConversationQueryConfig] fill each pull the number of sessions.
• Related callbacks: [ZIMConversationListQueriedCallback].
• Related APIs: [DeleteConversation] Deletes the session. [ClearConversationUnreadMessageCount] clear session readings.

• Use cases: This interface can be invoked to get the data source when you need to display an existing pinned message conversation after logging in.
• When to call /Trigger: Can be invoked after login.
• Caution: NextConversation is the riveting point of the query message, which can be null for the first query. In subsequent query, the earliest conversation can be used as nextConversation to query earlier sessions. In paging query, Count in [ZIMConversationQueryConfig] fill each pull the number of sessions.

• Use cases: You can call this interface when you need to modify the pinned state of a conversation.
• When to call /Trigger: Can be invoked after login.
• Related callbacks: [ZIMConversationPinnedStateUpdatedCallback].

• Use cases: You can invoke this interface implementation to delete an entire session when it is no longer needed.
• When to call /Trigger: his parameter is invoked when a session needs to be deleted and can be invoked after a ZIM instance is created. The call takes effect after login and becomes invalid after logout.
• Impacts on other APIs: A successful call triggers the DeleteConversation callback. If the deleted conversation contains unread messages, the [onConversationTotalUnreadMessageCountUpdated] callback is triggered.
• Related callbacks: [ZIMConversationDeletedCallback]

• Use cases: This interface is called when a chat page is entered from a session and the original message readings of the session need to be cleared.
• When to call /Trigger: Called when a target needs to be cleared without readings.
• Impacts on other APIs: Calling this method will trigger a total readings not updated callback [OnConversationTotalUnreadMessageCountUpdated], would trigger a session to update callbacks [OnConversationChanged].
• Related callbacks: [ZIMConversationUnreadMessageCountClearedCallback].
• Related APIs: [OnConversationTotalUnreadMessageCountUpdated]、[OnConversationChanged].

• Use cases: If the user selects MESSAGE DO not Disturb (DND), the user can call the corresponding method.
• Default value: Message DND is disabled by default.
• When to call /Trigger: If the target session exists after login, invoke this interface if you want to enable the DND status of the target session.
• Impacts on other APIs: After the DND state is enabled, receiving messages is not triggered [OnConversationTotalUnreadMessageCountUpdated]。
• Related callbacks: [ZIMConversationNotificationStatusSetCallback]。
• Related APIs: [OnConversationTotalUnreadMessageCountUpdated]。

• Related APIs: [QueryHistoryMessage], [DeleteAllMessage], [DeleteMessages],[SendMediaMessage].

• Impacts on other APIs: Using this method will trigger the [ReceivePeerMessage] / [ReceiveRoomMessage] / [ReceiveGroupMessage] callback of the message receiver, and will trigger the [ConversationChanged] callback of the sender and receiver. Fires the [ConversationTotalUnreadMessageCountUpdated] callback.

pushconfig only needs to be filled in when you need to use the offline push function. Sending media messages to the room does not support offline push, nor does it support the callbacks [ConversationChanged] and [ConversationTotalUnreadMessageCountUpdated].

• Related callbacks: [ZIMMessageSentResult], [ZIMMediaUploadingProgress], [ReceivePeerMessage], [ReceiveRoomMessage], [ReceiveGroupMessage], [ConversationChanged], [ConversationTotalUnreadMessageCountUpdated].
• Related APIs: [QueryHistoryMessage], [DeleteAllMessage], [DeleteMessages]

• Use cases: The developer can combine the system message type, and convert the callback notification (for example, invite someone into the group, remove someone from the group, etc.) to the system message type on the client side and insert it into the local DB to achieve the effect of the system prompt .
• When to call: It can be called after login.
• Caution: Inserting "command" messages is not supported. To insert a "room" message, upgrade the SDK to 2.13.0 and above.
• Related callbacks: [ZIMMessageInsertedCallback].
• Related APIs: [QueryHistoryMessage], [DeleteAllMessage], [DeleteMessages].

• Use cases: Set all received receipt messages in the entire conversation to be read, and the sender of the message receipt in the conversation will receive the [OnConversationMessageReceiptChanged] callback from ZIMEventHandler.
• When to call: It can be called after login. It is recommended to call before entering the message list page. In the message list page, it is recommended to call [SendMessageReceiptsRead] to batch set the messages that need to be read.
• Caution: Only single chat conversation are allowed.

Related callback: [ZIMConversationMessageReceiptReadSentCallback].

• Related APIs: [SendMessageReceiptsRead], [SendMessage].

• Use cases: Developers can use this method to set a batch of messages with receipts that have been read. If the sender is online, it will receive the [OnMessageReceiptChanged] callback.
• When to call: Callable after login. It is recommended to set the settings for the messages that need to be read on the message list page. It is not recommended to mix with [SendConversationMessageReceiptRead].
• Related callbacks: [ZIMMessageReceiptsReadSentCallback].
• Related APIs: [SendMessage].

• Use cases: If you need to query the receipt status of the message, the number of unread users and the number of read users, you can call this interface.
• When to call: Callable after login. If you need to query the detailed member list, you can query through the interface [QueryGroupMessageReceiptReadMemberList] or [QueryGroupMessageReceiptUnreadMemberList].
• Related callbacks: [ZIMMessageReceiptsInfoQueriedResult].
• Related APIs: [QueryGroupMessageReceiptReadMemberList] , [QueryGroupMessageReceiptUnreadMemberList].

• Use cases: Developers can use this method to query the specific read member list of a message they send.
• When to call: Callable after login.
• Related callbacks: [ZIMGroupMessageReceiptMemberListQueriedCallback].
• Related APIs: If you need to query the receipt status of a certain message or only need to query the read/unread count, you can query through the interface [QueryMessageReceiptsInfo].

• Use cases: Developers can use this method to query the specific unread member list of a message they send.
• When to call: Callable after login.
• Related callbacks: [ZIMGroupMessageReceiptMemberListQueriedCallback].
• Related APIs: If you need to query the receipt status of a certain message or only need to query the read/unread count, you can query through the interface [QueryMessageReceiptsInfo].

• Related callbacks: [ZIMMessagesSearchedCallback].

• Related callbacks: [ZIMConversationsSearchedCallback].

• Related callbacks: [ZIMMessagesGlobalSearchedCallback].

• Related APIs: [queryHistoryMessage], [sendMessage], [sendMediaMessage].

• Related callbacks: [ZIMMediaDownloadedCallback], [ZIMMediaDownloadingProgress].

• Related callbacks: [ZIMMediaDownloadedCallback], [ZIMMediaDownloadingProgress].

• Related callbacks: [ZIMMessageQueriedCallback].

• Related callbacks: [ZIMPinnedMessageListQueriedCallback].

• Use cases: The user needs to recall a message. This method can be used when the user does not want other users to see the message.
• When to call: Called when the message needs to be revoked.

Room message revoke is not supported.

• Related callbacks: If the revoked message is the latest message of the session, the [OnConversationChanged] callback will be triggered, and if the message is unread, the [OnConversationTotalUnreadMessageCountUpdated] callback will be triggered.

• Impacts on other APIs: If the deleted message is the latest message of the session, the [OnConversationChanged] callback will be triggered, and if the message is unread, the [OnConversationTotalUnreadMessageCountUpdated] callback will be triggered.
• Related callbacks: [ZIMMessageDeletedCallback]、[OnConversationChanged]、[OnConversationTotalUnreadMessageCountUpdated].

• Use cases: Users need to express their position on a certain message, such as liking, and this method can be used to express their position.

Room message reaction is not supported.

• Related callbacks: If the addition is successful, the [OnMessageReactionsChanged] callback will be triggered. If the reaction is made to the latest message in the conversation, the [OnConversationChanged] callback will be triggered when the addition is successful.

• Use cases: Users need to delete the status of a message that has already been stated, which can be done using this method.

Room message reaction is not supported.

• Related callbacks: If the deletion is successful, the [OnMessageReactionsChanged] callback will be triggered. If the reaction is deleted from the latest message in the conversation, the [OnConversationChanged] callback will be triggered when the deletion is successful.

• Use cases: When it is necessary to obtain specific user information under a certain state of a message, this interface can be called to query state user messages in a paginated manner.

• Impacts on other APIs: The [OnConversationChanged] callback is triggered, and if there are unread messages, the [OnConversationTotalUnreadMessageCountUpdated] callback is triggered.
• Related callbacks: [ZIMMessageDeletedCallback].

• When to call: After the user is logged in.
• Privacy reminder: Please avoid passing sensitive personal information, including but not limited to phone numbers, ID card numbers, passport numbers, real names, etc.
• Related callbacks: [ ZIMMessageLocalExtendedDataUpdatedCallback ].

• Use cases: When you need to create a multi-person chat scene, you can create and join a room by this API.
• When to call: It can be called after creating a ZIM instance through [Create].
• Caution: When everyone leaves the room, the room will be automatically destroyed. If the room already exists, an error will occur when calling this API. For details, please refer to the returned error code handling.
• Related callbacks: The result of the room creation can be obtained through the [OnRoomCreated] callback.
• Related APIs: You can join the room through [JoinRoom] and leave the room with [LeaveRoom].

• Use cases: When you need to know the user information in the specified room, you can call this interface to obtain the data source.
• When to call /Trigger: Can be invoked after login.

• Use cases: Use this interface when you need to specify that you want to query some room users.
• Related callbacks: [ZIMRoomMembersAttributesQueriedCallback].
• Related APIs: [SetRoomMembersAttributes]、[QueryRoomMemberAttributesList].
• Runtime lifecycle: It is available after logging in and joining the corresponding room, but unavailable after leaving the corresponding room.

• Use cases: This interface is used when you need to query all room users.
• Related callbacks: [ZIMRoomMemberAttributesListQueriedCallback].
• Related APIs: [SetRoomMembersAttributes]、[QueryRoomMembersAttributes].
• Runtime lifecycle: It is available after logging in and joining the corresponding room, but unavailable after leaving the corresponding room.

• When to call: It can be called after logging in.

When everyone leaves the room, the room will be automatically destroyed, and a user can be in a maximum of 5 rooms at the same time. [enterRoom] is equivalent to [createRoom] and [joinRoom], so you only need to choose one of the APIs.

• Related callbacks: The result of entering the room can be obtained through the [onRoomEntered] callback.
• Related APIs: You can enter the room through [enterRoom], and leave the room through [leaveRoom].

• Use cases: In a multi-person chat scenario, users can call this interface to enter the room when they need to join the room.
• When to call: It can be called after creating a ZIM instance through [create].
• Caution: When everyone leaves the room, the room will be automatically destroyed.
• Related callbacks: The result of joining the room can be obtained through the [ZIMRoomJoinedCallback] callback.
• Related APIs: You can create a room with [CreateRoom] and leave the room with [LeaveRoom].

• Use cases: In the multi-person chat scenario, when users in the room need to leave the room, they can leave the room through this interface.
• When to call: After creating a ZIM instance via [create], it can be called when the user is in the room.
• Caution: If the current user is not in this room, the exit fails. When everyone leaves the room, the room will be automatically destroyed.
• Related callbacks: The result of leaving the room can be obtained through the [ZIMRoomLeftCallback] callback.
• Related APIs: You can create a room through [CreateRoom] and join a room with [JoinRoom].

• Use cases: When a developer needs to obtain a list of room members for other business operations, this interface can be called to obtain a list of members.
• When to call: After creating a ZIM instance through [Create], and the user is in the room that needs to be queried, you can call this interface.
• Caution: To use this feature, please contact ZEGOCLOUD technical support. If the user is not currently in this room, the query fails. When there are more than 500 room members, the result of querying the list of room members can only contain the information of a maximum of 500 members.
• Related callbacks: Through the [ZIMRoomMemberQueriedCallback] callback, you can get the result of querying the room member list.
• Related APIs: You can check the online number of people in the room through [QueryRoomOnlineMemberCount].

• Use cases: When a developer needs to obtain the number of room members who are online, this interface can be called.

Calling time: After creating a ZIM instance through [Create], and the user is in the room that needs to be queried, this interface can be called.

• Caution: If the user is not currently in this room, the query will fail.
• Related callbacks: The result of querying the online number of room members can be obtained through the [ZIMRoomOnlineMemberCountQueriedCallback] callback.
• Related APIs: the room member can be inquired through [QueryRoomMember].

• Use cases: This interface is used when you need to set the mic bit in a chat room.
• When to call /Trigger: after login, and in the relevant room to call.
• Default value: [ZIMRoomAttributesSetConfig] the space-time of the default configuration is optional, and do not update the owner, and involves the room properties in the owner is not automatically deleted after exit.
• Privacy reminder: Try not to introduce sensitive information related to personal privacy into the property of the room, including but not limited to mobile phone number, ID number, passport number, real name, etc.

Privacy reminder: Adds or modifies room properties to an existing room.

• Related callbacks: [ZIMRoomAttributesOperatedCallback].
• Related APIs: [DeleteRoomAttributes] to delete room attributes. [QueryRoomAllAttributes], queries the room attributes.

• Required: Required by the sender, if not filled, the audio message will fail to be sent When sending local audio messages.

• Required: If a local file is sent, this parameter must be set by the sender. Otherwise, the message fails to be sent.

• Use cases: Can be used to index other messages.
• Caution: When the developer actively creates a message, there is no need to modify this parameter. This parameter only has a value during callback.

• Use cases: Used to present the sending time of a message, and can be used for message sorting.
• Caution: This is a standard UNIX timestamp, in milliseconds.

• Use cases: You can add extended fields to the message and send it to the peer
• Required: no
• Caution: the length is 1k, you can contact technical support for configuration

• Required: Internal assignment.

• Use cases: For example, it can be used in groups or rooms.
• Required: No.
• Default value: false.
• Recommended value: Set to true if you need to mention everyone.
• Caution: This value does not add the "@Everyone" to the message text. Developers need to implement it themselves

• Use cases: For example, it can be used in sending messages.
• Required: No.
• Caution: This value does not add the "@User" to the message text. Developers need to implement it themselves

• Required: Required by the sender, if not filled, the audio message will fail to be sent When sending local audio messages.

• Required: If a local file is sent, this parameter must be set by the sender. Otherwise, the message fails to be sent.

• Required: Required.

• Required: not required.
• Default value: "".

• Required: not required.

• Required: not required.

• Required: required.

• Required: not required.

• Required: not required.

Default: 90.

• Required: not required.

• Required: required. default：GENERAL

• Use cases: After the calling party sends a call invitation, if the called party does not receive the invitation within 5 seconds (3 or 4 seconds can be configured for technical support) because the user is disconnected or not online, the user status changes to notYetReceived. You can use this state flow to indicate to the user that the user may not be online. If the called party goes online before the call times out, the status changes to received received.
• Required: This is not required.
• Default value: false
• Recommended value: This property takes effect in version 2.15.0 and later, when the new version sends an invitation to a call with delivery detection turned on to the old version, which will continue to display the inviting status instead of notYetReceived.

• Required: Required.

• Required: not required.

• Use cases: When the user needs to refuse to send some custom content to the inviter.
• Required: Required.
• Default value: "".

• Required: not required.

• Use cases: Can be used to index other messages.
• Caution: When the developer actively creates a message, there is no need to modify this parameter. This parameter only has a value during callback.

• Use cases: Used to present the sending time of a message, and can be used for message sorting.
• Caution: This is a standard UNIX timestamp, in milliseconds.