LiveKit integrates with ReplayKit to support screen sharing on iOS. There are two capture modes available depending on the requirements of your app:
- In-app Capture (default): Share screen content within your app.
- Broadcast Capture: Share screen content even when users switch to other apps.
By default, LiveKit uses the In-app Capture mode, which requires no additional configuration. In this mode, when screen sharing is enabled, the system prompts the user with a screen recording permission dialog. Once granted, a screen share track is published. The user only needs to grant permission once per app execution. Application audio is not supported with the In-App Capture mode.
Permission DialogIn this mode, when screen sharing is enabled, the system will present the user with a "Screen Broadcast" dialog. To start broadcasting, the user must tap "Start Broadcast." If the user taps outside the dialog, the operation is canceled. This dialog will be presented each time screen sharing is requested.
Screen Broadcast DialogIn order to capture system-wide screen content, ReplayKit requires a Broadcast Upload Extension—a separate process responsible for delivering samples to your app. This architecture is conceptually illustrated below:
flowchart LR
subgraph ide1[Common App Group]
a1[Your Application]
a2[Broadcast Upload Extension]
a1--->a2
a2--Samples from screen-->a1
end
To use the Broadcast Capture mode, follow these steps to add a Broadcast Upload Extension target and associated configuration to your project. You can also refer to the example app, which demonstrates this configuration.
- In Xcode, Choose "File" > "New > "Target"
- From the template chooser, select "Broadcast Upload Extension"
- Name the extension (e.g. "BroadcastExtension").
- Press "Finish"
- From the "Signing & Capabilities" tab of the new target, change the bundle identifier to be the same as your main app with
.broadcast
added to the end. To use a custom identifier, see Custom Identifiers below. - Replace the default content of
SampleHandler.swift
in the new target with the following:
import LiveKit
#if os(iOS)
@available(macCatalyst 13.1, *)
class SampleHandler: LKSampleHandler {
override var enableLogging: Bool { true }
}
#endif
Note: Overriding the enableLogging
property to return true
will bootstrap the logging system in the extension's process, making log messages available through the macOS Console app for troubleshooting.
In order for the broadcast extension to communicate with your app, they must be members of the same app group. To enable this, perform the following steps for both your primary app target and broadcast extension target:
- In the Project Editor, select the target.
- Select the "Signing & Capabilities" tab and press the "+ Capability" button.
- Add the "App Groups" capability.
- Press "+" to add a new app group.
- Add the target to the group
group.<main-app-bundle-id>
. To use a custom identifier, see Custom Identifiers below.
With setup of the broadcast extension complete, broadcast capture will be used by default when enabling screen share:
try await room.localParticipant.setScreenShare(enabled: true)
Note: When using broadcast capture, custom capture options must be set as room defaults rather than passed when enabling screen share with set(source:enabled:captureOptions:publishOptions:)
.
When using Broadcast Capture, you can capture app audio even when the user navigates away from your app. When enabled, the captured app audio is mixed with the local participant's microphone track. To enable this feature, set the default screen share capture options when connecting to the room:
let roomOptions = RoomOptions(
defaultScreenShareCaptureOptions: ScreenShareCaptureOptions(
appAudio: true // enables capture of app audio
)
)
// Option 1: Using SwiftUI RoomScope component
RoomScope(url: wsURL, token: token, enableMicrophone: true, roomOptions: roomOptions) {
// your components here
}
// Option 2: Using Room object directly
try await room.connect(
url: wsURL,
token: token,
roomOptions: roomOptions
)
try await room.localParticipant.setMicrophone(enabled: true)
While running your app in a debug session in Xcode, check the debug console for errors and use the Console app to inspect logs from the broadcast extension:
- Launch the Console app.
- Select your iOS device from the left sidebar and press "Start Streaming."
- In the search bar, add a filter for messages with a category of "LKSampleHandler."
- Initiate a screen share in your app and inspect Console for errors.
When using broadcast capture, a broadcast can be initiated externally (for example, via control center). By default, when a broadcast begins, the local participant automatically publishes a screen share track. In some cases, however, you may want to handle track publication manually. You can achieve this by using BroadcastManager
:
First, disable automatic track publication:
BroadcastManager.shared.shouldPublishTrack = false
Then, use one of the two methods for detecting changes in the broadcast state:
let subscription = BroadcastManager.shared
.isBroadcastingPublisher
.sink { isBroadcasting in
// Manually handle track publication
}
class MyDelegate: BroadcastManagerDelegate {
func broadcastManager(didChangeState isBroadcasting: Bool) {
// Manually handle track publication
}
}
BroadcastManager.shared.delegate = MyDelegate()
By default, the app group identifier is expected to be group.<main-app-bundle-id>
, and the broadcast extension's bundle identifier is expected to be <main-app-bundle-id>.broadcast
.
To override these values, set RTCAppGroupIdentifier
in Info.plist for both targets (both broadcast extension and main app), and set RTCScreenSharingExtension
in Info.plist for your main app.