Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

[bug] iOS: `useiOSBroadcastExtension: false` ignored since 2.4.0, in-app capture unreachable

未关闭
  • 哪里不对？
#1,150 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
55/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
冷清
技术栈
dart, flutter, ios
领域
mobile

调研方向

Start in lib/src/participant/local.dart and trace how the effective ScreenShareCaptureOptions are chosen before the iOS broadcast branch; then read ios/Classes/BroadcastManager.swift to understand the missing-extension guard. Done means useiOSBroadcastExtension: false reaches in-app capture, while a requested broadcast flow without an extension reports an error rather than silently returning success. Check for existing screen-share tests before adding coverage.

由索引模型根据 Issue 内容生成。

描述

Describe the bug

Since 2.4.0, setScreenShareEnabled(true) on iOS unconditionally routes into the Broadcast Upload Extension flow. ScreenShareCaptureOptions.useiOSBroadcastExtension still exists, but false (the documented in-app RPScreenRecorder mode through 2.3.6) has no effect.

lib/src/participant/local.dart (2.4.0–2.10.0 and current main):

if (lkPlatformIs(PlatformType.iOS) && !BroadcastManager().isBroadcasting) {
  // Wait until broadcasting to publish track
  await BroadcastManager().requestActivation();
  return null;
}

The branch precedes any capture options inspection; the in-app path below it is unreachable.

Worse, without an extension: requestActivation()'s native side (ios/Classes/BroadcastManager.swift) guard-returns when the RTCScreenSharingExtension Info.plist key is absent:

func requestActivation() {
    guard let bundleIdentifier = BroadcastBundleInfo.screenSharingExtension else { return }
    Task { await Self.showPicker(for: bundleIdentifier) }
}

No picker, no consent UI, no error, and no log so the call resolves null as success.

This appears to be an unintended side effect of #705 ("fix: Properly handle broadcast capture state"): the PR documents its async-return breaking change but never mentions useiOSBroadcastExtension or the in-app path. That capturer still works in flutter_webrtc, reachable via LocalVideoTrack.createScreenShareTrack() + publishVideoTrack() which is our current workaround.

Broadcast extension capture is always whole screen; in-app capture is scoped to the app's own UI. For privacy sensitive products (share this app with a support agent, never the user's other apps or notifications), app scoped capture is impossible through the public screenshare API on every released version.

To Reproduce

  1. Flutter app on a physical iPhone, livekit_client ≥ 2.4.0, no Broadcast Upload Extension target.
  2. Connect to a room, then: 
    await room.localParticipant!.setScreenShareEnabled(
  true,
  screenShareCaptureOptions:
      const ScreenShareCaptureOptions(useiOSBroadcastExtension: false),
);
  3. The call resolves (null); no consent UI, no published track, nothing logged. Remote participants receive nothing.
  4. On 2.3.6 the same code shows the ReplayKit consent alert and publishes an in-app screenshare track.

Expected behavior

  • useiOSBroadcastExtension: false (explicit or via RoomOptions.defaultScreenShareCaptureOptions) uses the in-app capturer, as through 2.3.6 . The gate should consult the effective capture options before routing to BroadcastManager.
  • Independently: when the broadcast flow is requested but RTCScreenSharingExtension is missing, fail loudly (throw or error event) instead of a silent null. Currently misconfiguration looks like success.

Platform information

  • Flutter version: 3.44.2
  • Plugin version: reproduced on 2.7.0 and 2.10.0 ; unchanged on main, 2026-08-04
  • Flutter target OS: iOS (real device, iPhone 17)
  • Flutter target OS version: iOS 26.4
  • Flutter console log: n/a, failure produces no output
主要语言
Dart
星标
421
派生
260
平均合并
2 天 17 小时
30 天内合并 PR
14

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

livekit/client-sdk-flutter 的其他 Issue

查看 livekit/client-sdk-flutter 的全部 Issue

相似的 Issue

更多 Dart Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。