@tencent-rtc/mcp 1.6.7 → 1.7.0

package/resource/knowledge/livekit/best-practice/common/voice-room-no-audio-troubleshoot.md

@@ -0,0 +1,100 @@
+---
+title: "Voice Room Audience Cannot Hear Anchor — Troubleshooting Guide（语聊房 / 观众听不到声音 / 没声音）"
+product: live
+frameworks: [android, ios, flutter]
+scope: platform_common
+tags: [voice room, no audio, no sound, troubleshoot, LiveSeatStore, DeviceStore, takeSeat, openLocalMicrophone, unmuteMicrophone, LoginStore, joinLive, seatList, microphoneStatus, LiveSeatState, DeviceState]
+version_range: ">=2.0.0"
+---
+
+# Voice Room Audience Cannot Hear Anchor — Troubleshooting Guide
+
+## 1. Key Takeaways
+
+- When the audience cannot hear the anchor, troubleshoot in order from anchor side to audience side: room → seat → microphone → mute → login → room entry — checking state at each layer.
+- Anchor side: confirm the anchor is seated (`seatList`), microphone is open (`DeviceStore.microphoneStatus`), and not muted (`userInfo.microphoneStatus`).
+- Audience side: confirm login status (`loginStatus == LOGIN`), room entry (`currentLive`), and device volume is normal.
+- API and state structures are consistent across all three platforms (Android/iOS/Flutter); the troubleshooting flow is universal.
+
+## 2. Field / API Reference
+
+| Field / Capability | Purpose | Notes |
+|---|---|---|
+| `LiveSeatStore` | Seat management | Provides `seatList`; check whether anchor info is present to determine if the anchor is seated |
+| `LiveSeatStore.seatList` | Seat list | Check for anchor info; the anchor item's `userInfo.microphoneStatus` indicates mute state |
+| `takeSeat` | Take a seat | Called when the anchor is not seated |
+| `DeviceStore` | Device management | Provides `DeviceState`; check `microphoneStatus` to determine if the microphone is open |
+| `DeviceState.microphoneStatus` | Microphone on/off state | Determines whether the anchor's microphone is open |
+| `openLocalMicrophone` | Open microphone | Called when the microphone is closed |
+| `unmuteMicrophone` | Resume audio publishing | Called when the anchor is muted |
+| `LoginStore` | Login management | Provides `loginState.loginStatus`; `LOGIN` means logged in |
+| `LiveListStore` | Live room management | Provides `LiveListState.currentLive`; determines if room entry succeeded |
+| `joinLive` | Enter room | Called when the audience has not entered the room |
+
+## 3. Mechanism & Sequence
+
+### Anchor-Side Troubleshooting (in order)
+
+1. Is the anchor seated? Check whether `LiveSeatStore.seatList` contains anchor info; if not, call `takeSeat`.
+2. Is the microphone open? Check `DeviceState.microphoneStatus`; if closed, call `openLocalMicrophone`.
+3. Is the anchor muted? Check the anchor item's `userInfo.microphoneStatus` in `seatList`; if muted, call `unmuteMicrophone`.
+
+### Audience-Side Troubleshooting (in order)
+
+1. Is the user logged in? Check whether `loginState.loginStatus` is `LOGIN`.
+2. Has the user entered the room? Check whether `LiveListState.currentLive` matches the current live room; if not, call `joinLive`.
+3. Is the device volume normal? Verify the system volume is audible.
+
+## 4. Standard Usage
+
+Follow this flow step by step — check the state and handle accordingly:
+
+```text
+观众听不到主播说话
+│
+├── 主播侧排查
+│   ├── 1. 是否在麦上？  → 否 → takeSeat 上麦
+│   │      查看 LiveSeatStore.seatList
+│   ├── 2. 麦克风是否打开？ → 否 → openLocalMicrophone
+│   │      查看 DeviceState.microphoneStatus
+│   └── 3. 是否静音？ → 是 → unmuteMicrophone
+│          查看 seatList 主播 userInfo.microphoneStatus
+│
+└── 观众侧排查
+    ├── 1. 是否已登录？ → 否 → 登录
+    │      查看 loginState.loginStatus == LOGIN
+    ├── 2. 是否进房？ → 否 → joinLive 进房
+    │      查看 LiveListState.currentLive
+    └── 3. 手机音量正常？ → 否 → 调整音量
+```
+
+## 5. Expected Results
+
+- Anchor's `LiveSeatStore.seatList` contains anchor info: anchor is seated and can publish audio.
+- `DeviceState.microphoneStatus` is open: microphone is capturing audio.
+- `userInfo.microphoneStatus` is open: not muted, audio is being published normally.
+- Audience `loginStatus == LOGIN`: logged in.
+- `LiveListState.currentLive` matches the current live room: room entry succeeded.
+- If all conditions above are met and the audience still cannot hear audio: check device volume or contact the development team.
+
+## 6. Common Pitfalls
+
+- Pitfall 1: Only troubleshooting the audience side while ignoring the anchor's seat/microphone/mute state.
+- Pitfall 2: Confusing `DeviceState.microphoneStatus` (device on/off) with `userInfo.microphoneStatus` (mute state) — the former is local device capture, the latter is the remote-visible state.
+- Pitfall 3: Anchor publishes audio without taking a seat (taking a seat is a prerequisite for publishing).
+- Pitfall 4: Audience has not entered the room (`currentLive` is incorrect) but assumes the anchor has no audio.
+- Pitfall 5: Skipping login status check and directly troubleshooting the audio pipeline.
+
+## 7. Problem Definition (retrieval hint)
+
+When a voice room audience member cannot hear the anchor, how to troubleshoot layer by layer on the anchor side (seat/microphone/mute) and audience side (login/room entry/volume) to locate the issue.
+
+## 8. Alternative Queries (retrieval recall)
+
+- What to do when voice room audience cannot hear the anchor?
+- How to troubleshoot no sound from the microphone in a voice room?
+- Anchor is seated but audience cannot hear audio?
+- How to check if the anchor is muted using `microphoneStatus`?
+- No sound after entering a voice room?
+- How to determine if the anchor is seated in a voice room?
+- What to check first when audience cannot hear audio?

package/resource/knowledge/livekit/best-practice/common/voice-room-seat-list-change.md

@@ -0,0 +1,65 @@
+---
+title: "Voice Room Seat Microphone Status Synchronization（语聊房 / 麦位 / 麦克风状态更新同步）"
+product: live
+frameworks: [android, ios, flutter]
+scope: platform_common
+tags: [voice room, seat, microphone status, mic on, mic off, userMicrophoneStatus, SeatListChanged, muteMicrophone, unmuteMicrophone, closeMicrophone, openMicrophone, sync]
+version_range: ">=2.0.0"
+---
+
+# Voice Room Seat Microphone Status Synchronization
+
+## 1. Key Takeaways
+
+- Both the anchor side and the audience side listen for seat microphone status (`userMicrophoneStatus`) changes via **`SeatListChanged`**.
+- `userMicrophoneStatus` values: `0` = mic on; `1` = mic off (self-muted, can be re-opened by self); `2` = mic off (muted by admin, cannot be re-opened by self).
+- `userMicrophoneStatus` can only be changed by **the anchor or a seated audience member** through `mute/unmute` or `close/open` APIs.
+- The audience side only listens for status changes and does **not need** to call `mute/unmute` or `close/open` to modify `userMicrophoneStatus`.
+
+## 2. Field / API Reference
+
+| Field / Capability | Purpose | Notes |
+|---|---|---|
+| `userMicrophoneStatus` | Seat microphone on/off state | `0` = mic on; `1` = mic off (self-muted, can reopen); `2` = mic off (admin-muted, cannot reopen) |
+| `SeatListChanged` | Seat list change event | Both anchor and audience listen to this for `userMicrophoneStatus` changes; SDK syncs automatically |
+| `muteMicrophone` / `unmuteMicrophone` | Mute / unmute | Called by anchor or seated audience; triggers `userMicrophoneStatus` change |
+| `closeMicrophone` / `openMicrophone` | Close / open microphone | Called by anchor or seated audience; triggers `userMicrophoneStatus` change |
+| Audience side | Read-only state | Only listens for status; does not call `mute/unmute` or `close/open` |
+
+## 3. Mechanism & Sequence
+
+Anchor or seated audience calls `mute/unmute` or `close/open` API -> triggers `userMicrophoneStatus` change -> SDK fires `SeatListChanged`, automatically syncing to all clients -> both anchor and audience receive the updated seat state via `SeatListChanged`.
+
+`userMicrophoneStatus` can only be changed by the anchor or a seated audience member via `mute/unmute` or `close/open` APIs; the audience side only listens for status and does not actively modify it.
+
+## 4. Standard Usage
+
+Both anchor and audience listen for `SeatListChanged` and update the UI based on `userMicrophoneStatus`.
+The anchor or a seated audience member changes the microphone state via `mute/unmute` or `close/open` APIs, and the SDK automatically syncs to all clients.
+
+## 5. Expected Results
+
+- After the anchor or seated audience calls `mute/unmute` or `close/open`, `userMicrophoneStatus` in `SeatListChanged` is updated on all clients.
+- `userMicrophoneStatus = 0`: mic is on.
+- `userMicrophoneStatus = 1`: mic is off (self-muted; can be re-opened by self).
+- `userMicrophoneStatus = 2`: mic is off (admin-muted; cannot be re-opened by self).
+- Audience side does not need to call `mute/unmute` or `close/open`; status is synced automatically by the SDK.
+
+## 6. Common Pitfalls
+
+- Pitfall 1: Audience calls `mute/unmute` or `close/open` to modify `userMicrophoneStatus` (not needed — status is auto-synced by SDK; audience side is read-only).
+- Pitfall 2: Assuming `userMicrophoneStatus = 1` and `2` mean the same thing (`1` = self-muted and can reopen; `2` = admin-muted and cannot reopen).
+- Pitfall 3: Assuming `userMicrophoneStatus` can be changed from the audience side (it can only be triggered by the anchor or a seated audience member via `mute/unmute` or `close/open`).
+
+## 7. Problem Definition (retrieval hint)
+
+The meaning of each `userMicrophoneStatus` value in a voice room seat, how it syncs to both anchor and audience via `SeatListChanged`, and which roles can change it through which APIs.
+
+## 8. Alternative Queries (retrieval recall)
+
+- Audience cannot see anchor's mic-on status in a voice room — what to do?
+- What do `userMicrophoneStatus` values 0/1/2 mean?
+- How does `SeatListChanged` sync seat microphone status?
+- Who can change `userMicrophoneStatus`?
+- Does the audience need to call `muteMicrophone` to update mic status?
+- After admin mutes a user, can the user reopen their mic?

package/resource/knowledge/livekit/best-practice/flutter/voice-room-anchor-start.md

@@ -0,0 +1,122 @@
+---
+title: "Voice Room Anchor Creates Room and Starts Streaming (Flutter)（语聊房 / 房主 / 开播 / createLive）"
+product: live
+frameworks: [flutter]
+scope: platform_specific
+tags: [voice room, anchor, start streaming, publish audio, createLive, openLocalMicrophone, muteMicrophone, unmuteMicrophone, LiveListStore, AudioSalon, keepOwnerOnSeat, seatMode, TakeSeatMode, Flutter, AtomicXCore]
+version_range: ">=2.0.0"
+---
+
+# Voice Room Anchor Creates Room and Starts Streaming (Flutter)
+
+## 1. Key Takeaways
+
+- Voice room streaming flow: construct `LiveInfo` (with `liveID`, `seatTemplate`, `seatMode`, `keepOwnerOnSeat`), call `createLive` to create the room; on success, call `openLocalMicrophone` to capture and publish audio so other users in the room can hear the anchor.
+- `liveID` is required; setting `keepOwnerOnSeat` to `true` makes the anchor automatically take a seat upon entering (taking a seat is a prerequisite for publishing audio — only seated users can publish audio streams in the room).
+- `seatTemplate` should be set to the voice room template `AudioSalon(n)`, where n is the maximum seat count supported by the plan or a value less than it.
+- `seatMode` sets the seat-taking mode (e.g., `TakeSeatMode.apply` for apply-to-take-seat).
+- `muteMicrophone` pauses publishing local audio; `unmuteMicrophone` resumes publishing local audio.
+
+## 2. Field / API Reference
+
+| Field / Capability | Purpose | Notes |
+|---|---|---|
+| `LiveInfo` | Room information | Dart constructor `LiveInfo({liveID, liveName, seatTemplate, seatMode, keepOwnerOnSeat})` |
+| `liveID` | Room ID | Required parameter for `createLive` |
+| `liveName` | Room name | Display name of the room |
+| `seatTemplate` | Seat layout template | Use `AudioSalon(n)` for voice rooms, where n ≤ max seats in plan |
+| `seatMode` | Seat-taking mode | e.g., `TakeSeatMode.apply` for apply-to-take-seat |
+| `keepOwnerOnSeat` | Auto-seat the owner | Set to `true` so the anchor automatically takes a seat upon entering |
+| `createLive(liveInfo)` | Create room (start streaming) | Pass `LiveInfo`, returns `Future<result>` for async handling |
+| `result.isSuccess` | Success flag | `true` means creation succeeded |
+| `result.message` | Error message | Returns error description on failure |
+| `openLocalMicrophone` | Capture and publish audio | Opens local microphone and publishes audio stream to the room |
+| `muteMicrophone` | Pause audio publishing | Pauses local audio stream while microphone remains open |
+| `unmuteMicrophone` | Resume audio publishing | Resumes local audio stream while microphone remains open |
+
+## 3. Mechanism & Sequence
+
+Construct `LiveInfo` (`liveID` required, `seatTemplate=AudioSalon(n)`, `seatMode` as needed, `keepOwnerOnSeat=true`) -> `await createLive(liveInfo)` -> `result.isSuccess` is `true`, anchor is auto-seated -> call `openLocalMicrophone` to capture and publish audio -> other users in the room hear the anchor.
+
+Taking a seat is a prerequisite for streaming: `keepOwnerOnSeat=true` ensures the anchor takes a seat before publishing audio. `muteMicrophone` / `unmuteMicrophone` are used to pause/resume during streaming.
+
+## 4. Standard Usage
+
+1. Construct `LiveInfo`: set `liveID`, `seatTemplate`, `seatMode`, `keepOwnerOnSeat`.
+2. Call `await _liveListStore.createLive(liveInfo)` to start streaming.
+3. Check `result.isSuccess`; on success, call `openLocalMicrophone` to capture and publish audio.
+4. Call `muteMicrophone` / `unmuteMicrophone` to pause/resume streaming as needed.
+
+```dart
+class _YourAnchorPageState extends State<YourAnchorPage> {
+  // ... 其他代码 ...
+  final String _liveID = "test_voice_room_001";
+
+  @override
+  void initState() {
+    super.initState();
+    // ... 其他代码 ...
+
+    // 开始语聊
+    _startLive();
+  }
+
+  Future<void> _startLive() async {
+    // 1. 准备 LiveInfo 对象
+    final liveInfo = LiveInfo(
+      // 2. 设置房间 id
+      liveID: _liveID,
+      // 3. 设置房间名称
+      liveName: "test 语聊房",
+      // 4. 设置语聊房布局模板（传入 9 即代表有 9 个麦位）
+      seatTemplate: AudioSalon(9),
+      // 5. 设置上麦模式，例如申请上麦
+      seatMode: TakeSeatMode.apply,
+      // 6. 设置主播开播后自动上麦
+      keepOwnerOnSeat: true,
+    );
+
+    // 7. 调用 createLive 开始直播
+    final result = await _liveListStore.createLive(liveInfo);
+
+    if (result.isSuccess) {
+      debugPrint("Response startLive onSuccess");
+      // 8. 房主创建成功后默认自动上麦，此时调用 openLocalMicrophone 采集并发布音频
+      _liveSeatStore.openLocalMicrophone();
+    } else {
+      debugPrint("Response startLive onError: ${result.message}");
+    }
+  }
+}
+```
+
+## 5. Expected Results
+
+- `result.isSuccess == true`: room created successfully, anchor is auto-seated.
+- After `openLocalMicrophone`: other users in the room can hear the anchor.
+- After `muteMicrophone`: local audio publishing is paused; after `unmuteMicrophone`: publishing resumes.
+- If `keepOwnerOnSeat` is not set to `true`: the anchor is not auto-seated and cannot publish audio.
+- `result.isSuccess == false`: streaming failed, `result.message` contains the error description.
+
+## 6. Common Pitfalls
+
+- Pitfall 1: Calling `openLocalMicrophone` without calling `createLive` first (cannot publish audio without creating a room).
+- Pitfall 2: Not setting `keepOwnerOnSeat` to `true`, so the anchor is not seated and audio publishing does not work.
+- Pitfall 3: Not setting `seatTemplate` or setting n beyond the plan's maximum seat count.
+- Pitfall 4: Confusing `muteMicrophone` (pauses audio stream publishing) with closing the microphone (stops audio capture).
+- Pitfall 5: Reusing `liveID` (it must be globally unique; otherwise creation fails).
+- Pitfall 6: `AudioSalon(9)` is a constructor form (not an enum); `seatMode` uses `TakeSeatMode.apply` (Dart enum lowercase).
+
+## 7. Problem Definition (retrieval hint)
+
+A Flutter voice room anchor needs to create a room and start audio streaming in the correct order, understanding the call timing and parameter meanings of `createLive`, `openLocalMicrophone`, `muteMicrophone`, and `unmuteMicrophone`.
+
+## 8. Alternative Queries (retrieval recall)
+
+- How does a Flutter voice room anchor start streaming?
+- What is the call order of `createLive` and `openLocalMicrophone` in Flutter?
+- How does a Flutter anchor take a seat and publish audio?
+- What does the `keepOwnerOnSeat` parameter do?
+- How to set the `AudioSalon` template for `seatTemplate`?
+- What is the difference between `muteMicrophone` and `unmuteMicrophone` in Flutter?
+- How to publish audio after creating a voice room?

package/resource/knowledge/livekit/best-practice/ios/voice-room-anchor-start.md

@@ -0,0 +1,126 @@
+---
+title: "Voice Room Anchor Creates Room and Starts Streaming (iOS)（语聊房 / 房主 / 开播 / createLive）"
+product: live
+frameworks: [ios]
+scope: platform_specific
+tags: [voice room, anchor, start streaming, publish audio, createLive, openLocalMicrophone, muteMicrophone, unmuteMicrophone, LiveListStore, AudioSalon, keepOwnerOnSeat, seatMode, iOS, Swift, AtomicXCore]
+version_range: ">=2.0.0"
+---
+
+# Voice Room Anchor Creates Room and Starts Streaming (iOS)
+
+## 1. Key Takeaways
+
+- Voice room streaming flow: construct `LiveInfo` (with `liveID`, `seatTemplate`, `keepOwnerOnSeat`, `seatMode`), call `createLive` to create the room; on success, call `openLocalMicrophone` to capture and publish audio so other users in the room can hear the anchor.
+- `liveID` is required; setting `keepOwnerOnSeat` to `true` makes the anchor automatically take a seat upon entering (taking a seat is a prerequisite for publishing audio — only seated users can publish audio streams in the room).
+- `seatTemplate` should be set to `SeatLayoutTemplate.AudioSalon(seatCount: n)`, where n is the maximum seat count supported by the plan or a value less than it.
+- `seatMode` sets the seat-taking mode (e.g., `.apply` for apply-to-take-seat).
+- `muteMicrophone` pauses publishing local audio; `unmuteMicrophone` resumes publishing local audio.
+
+## 2. Field / API Reference
+
+| Field / Capability | Purpose | Notes |
+|---|---|---|
+| `LiveInfo` | Room information | Contains `liveID`, `liveName`, `seatTemplate`, `keepOwnerOnSeat`, `seatMode`, etc. |
+| `liveID` | Room ID | Required parameter for `createLive` |
+| `liveName` | Room name | Display name of the room |
+| `seatTemplate` | Seat layout template | Use `SeatLayoutTemplate.AudioSalon(seatCount: n)` for voice rooms, where n ≤ max seats in plan |
+| `keepOwnerOnSeat` | Auto-seat the owner | Set to `true` so the anchor automatically takes a seat upon entering |
+| `seatMode` | Seat-taking mode | e.g., `.apply` for apply-to-take-seat |
+| `createLive(liveInfo)` | Create room (start streaming) | Pass `LiveInfo`, returns `Result` for async handling |
+| `openLocalMicrophone` | Capture and publish audio | Opens local microphone and publishes audio stream to the room |
+| `muteMicrophone` | Pause audio publishing | Pauses local audio stream while microphone remains open |
+| `unmuteMicrophone` | Resume audio publishing | Resumes local audio stream while microphone remains open |
+
+## 3. Mechanism & Sequence
+
+Construct `LiveInfo` (`liveID` required, `seatTemplate=AudioSalon(n)`, `keepOwnerOnSeat=true`, `seatMode` as needed) -> call `createLive` to create the room -> `case .success` callback fires, anchor is auto-seated -> call `openLocalMicrophone` to capture and publish audio -> other users in the room hear the anchor.
+
+Taking a seat is a prerequisite for streaming: `keepOwnerOnSeat=true` ensures the anchor takes a seat before publishing audio. `muteMicrophone` / `unmuteMicrophone` are used to pause/resume during streaming.
+
+## 4. Standard Usage
+
+1. Construct `LiveInfo`: set `liveID`, `seatTemplate`, `keepOwnerOnSeat`, `seatMode`.
+2. Call `createLive(liveInfo)` and handle success/failure in `switch result`.
+3. In `case .success`, call `openLocalMicrophone` to capture and publish audio.
+4. Call `muteMicrophone` / `unmuteMicrophone` to pause/resume streaming as needed.
+
+```swift
+import UIKit
+import AtomicXCore
+
+class YourAnchorViewController: UIViewController {
+    // ... 其他代码 ...
+    private let liveID = "test_voice_room_001"
+
+    override func viewDidLoad() {
+        super.viewDidLoad()
+        // ... 其他代码 ...
+
+        // 开始语聊
+        startLive()
+    }
+
+    private func startLive() {
+        // 1. 准备 LiveInfo 对象
+        var liveInfo = LiveInfo()
+
+        // 2. 设置房间 id
+        liveInfo.liveID = liveID
+        // 3. 设置房间名称
+        liveInfo.liveName = "test 语聊房"
+        // 4. 设置语聊房布局模板（传入 9 即代表有 9 个麦位）
+        liveInfo.seatTemplate = SeatLayoutTemplate.AudioSalon(seatCount: 9)
+
+        // 5. 设置主播开播后自动上麦
+        liveInfo.keepOwnerOnSeat = true
+
+        // 6. 设置上麦模式，例如申请上麦
+        liveInfo.seatMode = .apply
+
+        // 7. 调用 createLive 开始直播
+        liveListStore.createLive(liveInfo) { [weak self] result in
+            guard let self = self else { return }
+            switch result {
+            case .success(let liveInfo):
+                print("Response startLive onSuccess")
+                // 8. 房主创建成功后默认自动上麦，此时调用 openLocalMicrophone 采集并发布音频
+                liveSeatStore.openLocalMicrophone(completion: nil)
+            case .failure(let errorInfo):
+                print("Response startLive onError: \(errorInfo.message)")
+            }
+        }
+    }
+}
+```
+
+## 5. Expected Results
+
+- `case .success` callback fires: room created successfully, anchor is auto-seated.
+- After `openLocalMicrophone`: other users in the room can hear the anchor.
+- After `muteMicrophone`: local audio publishing is paused; after `unmuteMicrophone`: publishing resumes.
+- If `keepOwnerOnSeat` is not set to `true`: the anchor is not auto-seated and cannot publish audio.
+- `case .failure(let errorInfo)` callback fires: streaming failed, `errorInfo.message` contains the error description.
+
+## 6. Common Pitfalls
+
+- Pitfall 1: Calling `openLocalMicrophone` without calling `createLive` first (cannot publish audio without creating a room).
+- Pitfall 2: Not setting `keepOwnerOnSeat` to `true`, so the anchor is not seated and audio publishing does not work.
+- Pitfall 3: Not setting `seatTemplate` or setting `seatCount` beyond the plan's maximum seat count.
+- Pitfall 4: Confusing `muteMicrophone` (pauses audio stream publishing) with closing the microphone (stops audio capture).
+- Pitfall 5: Reusing `liveID` (it must be globally unique; otherwise creation fails).
+- Pitfall 6: Forgetting `[weak self]` (to avoid retain cycles causing memory leaks); both `success` and `failure` branches of `switch result` must be handled.
+
+## 7. Problem Definition (retrieval hint)
+
+An iOS voice room anchor needs to create a room and start audio streaming in the correct order, understanding the call timing and parameter meanings of `createLive`, `openLocalMicrophone`, `muteMicrophone`, and `unmuteMicrophone`.
+
+## 8. Alternative Queries (retrieval recall)
+
+- How does an iOS voice room anchor start streaming?
+- What is the call order of `createLive` and `openLocalMicrophone` on iOS?
+- How does an iOS anchor take a seat and publish audio?
+- What does the `keepOwnerOnSeat` parameter do?
+- How to set the `AudioSalon` template for `seatTemplate`?
+- What is the difference between `muteMicrophone` and `unmuteMicrophone` on iOS?
+- How to publish audio after creating a voice room?

package/resource/knowledge/livekit/core-sdk/api-reference/android/AudioEffectStore.md

@@ -3,17 +3,14 @@
 `AudioEffectStore` provides a complete set of audio effect management APIs, including voice changer effects, reverb effects, and ear monitor functionality. Through this class, anchors can adjust their voice effects in real-time during live streaming to enhance the experience.
 
 > **Important:**
->
 > Use the **AudioEffectStore.shared** singleton to get the `AudioEffectStore` instance. The set effects will automatically become invalid after leaving the room, and need to be set again for the next room entry.
 >
 
 > **Note:**
->
 > Audio effect state updates are delivered through the **audioEffectState** publisher. Subscribe to it to receive real-time updates about voice changer, reverb, and ear monitor states.
 >
 
 > **Warning:**
->
 > Due to the very high hardware latency of Bluetooth earphones, the ear monitor feature cannot be enabled when the anchor is wearing Bluetooth earphones. Please prompt the anchor to wear wired earphones in the user interface.
 >
 
@@ -78,7 +75,6 @@ Call after entering the room and when voice changer effect is needed.
 **Notes**
 
 > **Note:**
->
 > The set effect will automatically become invalid after leaving the room. If you need the corresponding effect for the next room entry, you need to call this interface again to set it.
 >
 
@@ -112,7 +108,6 @@ Call after entering the room and when reverb effect is needed.
 **Notes**
 
 > **Note:**
->
 > The set effect will automatically become invalid after leaving the room. If you need the corresponding effect for the next room entry, you need to call this interface again to set it.
 >
 
@@ -148,7 +143,6 @@ Call after entering the room and when the anchor is wearing wired earphones.
 **Notes**
 
 > **Warning:**
->
 > Due to the very high hardware latency of Bluetooth earphones, this effect cannot be enabled when the anchor is wearing Bluetooth earphones. Please try to prompt the anchor to wear wired earphones in the user interface.
 >
 
@@ -178,7 +172,6 @@ Call after enabling the ear monitor feature.
 **Notes**
 
 > **Note:**
->
 > If the volume is still too low after setting it to 100, you can set the volume to a maximum of 150, but a volume exceeding 100 may cause distortion, please operate with caution.
 >
 

package/resource/knowledge/livekit/core-sdk/api-reference/android/BarrageStore.md

@@ -3,12 +3,10 @@
 `BarrageStore` provides a complete set of barrage management APIs, including sending text barrages, sending custom barrages, and adding local tip messages. Through this class, you can implement barrage interaction functionality in live rooms.
 
 > **Important:**
->
 > Use the **BarrageStore.create** factory method to create a `BarrageStore` instance, which requires a valid live room ID.
 >
 
 > **Note:**
->
 > Barrage state updates are delivered through the **barrageState** publisher. Subscribe to it to receive real-time updates of barrage data in the room.
 >
 
@@ -117,7 +115,6 @@ Supported since version 3.5.
 **Notes**
 
 > **Note:**
->
 > This message is only displayed locally and will not be sent to other users through the network.
 >
 

package/resource/knowledge/livekit/core-sdk/api-reference/android/BattleStore.md

@@ -3,17 +3,14 @@
 PK feature enables real-time interactive battles between hosts. `BattleStore` provides a comprehensive set of APIs to manage the entire PK lifecycle.
 
 > **Important:**
->
 > Always use the factory method **BattleStore.create** with a valid live room ID to create a `BattleStore` instance. Do not attempt to initialize directly.
 >
 
 > **Note:**
->
 > PK state updates are delivered through the **battleState** publisher. Subscribe to it to receive real-time updates about PK information, participating users, and scores.
 >
 
 > **Warning:**
->
 > If a PK request does not receive a response within the specified timeout, a timeout event will be triggered. Always handle timeout scenarios in the UI.
 >
 

package/resource/knowledge/livekit/core-sdk/api-reference/android/CameraView.md

@@ -3,7 +3,6 @@
 `CameraView` is a view component specifically designed to display camera preview. When starting camera test, the camera rendering view will be displayed on this view.
 
 > **Note:**
->
 > This class is only available on Android platform.
 >
 

package/resource/knowledge/livekit/core-sdk/api-reference/android/CoGuestStore.md

@@ -3,17 +3,14 @@
 Co-guest feature enables real-time interaction between hosts and audience members through a seat-based system. `CoGuestStore` provides a comprehensive set of APIs to manage the entire co-guest lifecycle.
 
 > **Important:**
->
 > Always use the factory method **CoGuestStore.create** with a valid live room ID to create a `CoGuestStore` instance. Do not attempt to initialize directly.
 >
 
 > **Note:**
->
 > Co-guest state updates are delivered through the **coGuestState** publisher. Subscribe to it to receive real-time updates about connected users, invitations and applications.
 >
 
 > **Warning:**
->
 > If a co-guest request does not receive a response within the specified timeout, an event with `NoResponseReason.timeout` will be triggered. Always handle timeout scenarios in your UI.
 >
 
@@ -169,7 +166,6 @@ Supported since version 3.5.
 **Notes**
 
 > **Note:**
->
 > If no host responds within the timeout, {ref2} event with **NoResponseReason.TIMEOUT** will be triggered.
 >
 
@@ -200,7 +196,6 @@ Supported since version 3.5.
 **Notes**
 
 > **Note:**
->
 > If the application has already been processed by a host, the cancellation may have no effect.
 >
 

package/resource/knowledge/livekit/core-sdk/api-reference/android/CoHostStore.md

@@ -3,17 +3,14 @@
 Cross-room connection feature allows hosts from different live rooms to interact in real-time. `CoHostStore` provides a comprehensive set of APIs to manage the entire cross-room connection lifecycle.
 
 > **Important:**
->
 > Always use the factory method **CoHostStore.create** with a valid live room ID to create a `CoHostStore` instance. Do not attempt to initialize directly.
 >
 
 > **Note:**
->
 > Connection state updates are delivered through the **coHostState** publisher. Subscribe to it to receive real-time updates about connection status, connected hosts, invitations and applications.
 >
 
 > **Warning:**
->
 > If a connection request does not receive a response within the specified timeout, the timeout event will be triggered. Always handle timeout scenarios in your UI.
 >
 

package/resource/knowledge/livekit/core-sdk/api-reference/android/DeviceStore.md

@@ -3,12 +3,10 @@
 `DeviceStore` provides a comprehensive set of APIs to manage audio and video devices, including microphone, camera and screen sharing features.
 
 > **Important:**
->
 > Use **DeviceStore.shared** singleton to get the `DeviceStore` instance. Do not attempt to initialize directly.
 >
 
 > **Note:**
->
 > Device state updates are delivered through the **deviceState** publisher. Subscribe to it to receive real-time updates about microphone, camera, network and other states.
 >
 

package/resource/knowledge/livekit/core-sdk/api-reference/android/GiftStore.md

@@ -3,12 +3,10 @@
 `GiftStore` provides a complete set of gift management APIs, including sending gifts, refreshing gift lists, setting language, and listening to gift events. Through this class, gift interaction features can be implemented in live rooms.
 
 > **Important:**
->
 > Use the **GiftStore.create** factory method to create a `GiftStore` instance, passing a valid live room ID.
 >
 
 > **Note:**
->
 > Gift state updates are delivered through the **giftState** publisher. Subscribe to it to receive real-time updates of gift data in the room.
 >
 

package/resource/knowledge/livekit/core-sdk/api-reference/android/LikeStore.md

@@ -3,12 +3,10 @@
 `LikeStore` provides a complete set of like management APIs, including sending likes, listening to like events, and getting like states. Through this class, you can implement like interaction features in live rooms.
 
 > **Important:**
->
 > Use the **LikeStore.create** factory method to create a `LikeStore` instance, which requires a valid live room ID.
 >
 
 > **Note:**
->
 > Like state updates are delivered through the **likeState** publisher. Subscribe to it to receive real-time updates of like data in the room.
 >
 

package/resource/knowledge/livekit/core-sdk/api-reference/android/LiveAudienceStore.md

@@ -3,12 +3,10 @@
 `LiveAudienceStore` provides a complete set of audience management APIs, including fetching audience list, setting administrators, kicking users, muting, etc. Through this class, you can implement audience management functions in live rooms.
 
 > **Important:**
->
 > Use the **LiveAudienceStore.create** factory method to create a `LiveAudienceStore` instance, which requires a valid live room ID.
 >
 
 > **Note:**
->
 > Audience state updates are delivered through the **liveAudienceState** publisher. Subscribe to it to receive real-time updates of audience data in the room.
 >
 

package/resource/knowledge/livekit/core-sdk/api-reference/android/LiveCoreView.md

@@ -3,7 +3,6 @@
 `LiveCoreView` provides view container for live streaming push and playback, supporting multi-person co-guest, PK and other features. Through this component, video rendering and interaction in live rooms can be implemented.
 
 > **Important:**
->
 > Before using, you need to call **setLiveID** to set the live room ID first.
 >
 

package/resource/knowledge/livekit/core-sdk/api-reference/android/LiveSeatStore.md

@@ -3,12 +3,10 @@
 `LiveSeatStore` provides a complete set of seat management APIs, including taking seat, leaving seat, locking seat, unlocking seat, kicking user off seat, remote device control, etc. Through this class, seat management functionality can be implemented in the live room.
 
 > **Important:**
->
 > Use the **LiveSeatStore.create** factory method to create a `LiveSeatStore` instance, passing a valid live room ID.
 >
 
 > **Note:**
->
 > Seat state updates are delivered through the **liveSeatState** publisher. Subscribe to it to receive real-time updates of seat data in the room.
 >