base on LiveKit Swift Client SDK. Easily build live audio or video experiences on iOS, macOS, tvOS, and visionOS. <!--BEGIN_BANNER_IMAGE--> <picture> <source media="(prefers-color-scheme: dark)" srcset="/.github/banner_dark.png"> <source media="(prefers-color-scheme: light)" srcset="/.github/banner_light.png"> <img style="width:100%;" alt="The LiveKit icon, the name of the repository and some sample code in the background." src="https://raw.githubusercontent.com/livekit/client-sdk-swift/main/.github/banner_light.png"> </picture> <!--END_BANNER_IMAGE--> # iOS/macOS Swift SDK for LiveKit <!--BEGIN_DESCRIPTION--> Use this SDK to add realtime video, audio and data features to your Swift app. By connecting to <a href="https://livekit.io/">LiveKit</a> Cloud or a self-hosted server, you can quickly build applications such as multi-modal AI, live streaming, or video calls with just a few lines of code. <!--END_DESCRIPTION--> [](https://swiftpackageindex.com/livekit/client-sdk-swift) [](https://swiftpackageindex.com/livekit/client-sdk-swift) ## Docs & Example app > [!NOTE] > Version 2 of the Swift SDK contains breaking changes from Version 1. > Read the [migration guide](https://docs.livekit.io/guides/migrate-from-v1/) for a detailed overview of what has changed. Docs and guides are at [https://docs.livekit.io](https://docs.livekit.io). There is full source code of a [iOS/macOS Swift UI Example App](https://github.com/livekit/client-example-swift). For minimal examples view this repo 👉 [Swift SDK Examples](https://github.com/livekit/client-example-collection-swift) ## Installation LiveKit for Swift is available as a Swift Package. ### Package.swift Add the dependency and also to your target ```swift title="Package.swift" let package = Package( ... dependencies: [ .package(name: "LiveKit", url: "https://github.com/livekit/client-sdk-swift.git", .upToNextMajor("2.5.1")), ], targets: [ .target( name: "MyApp", dependencies: ["LiveKit"] ) ] } ``` ### XCode Go to Project Settings -> Swift Packages. Add a new package and enter: `https://github.com/livekit/client-sdk-swift` ### CocoaPods For installation using CocoaPods, please refer to this [guide](./Docs/cocoapods.md). ## iOS Usage LiveKit provides an UIKit based `VideoView` class that renders video tracks. Subscribed audio tracks are automatically played. ```swift import LiveKit import UIKit class RoomViewController: UIViewController { lazy var room = Room(delegate: self) lazy var remoteVideoView: VideoView = { let videoView = VideoView() view.addSubview(videoView) // Additional initialization ... return videoView }() lazy var localVideoView: VideoView = { let videoView = VideoView() view.addSubview(videoView) // Additional initialization ... return videoView }() override func viewDidLoad() { super.viewDidLoad() view.backgroundColor = .white let url = "ws://your_host" let token = "your_jwt_token" Task { do { try await room.connect(url: url, token: token) // Connection successful... // Publishing camera & mic... try await room.localParticipant.setCamera(enabled: true) try await room.localParticipant.setMicrophone(enabled: true) } catch { // Failed to connect } } } } extension RoomViewController: RoomDelegate { func room(_: Room, participant _: LocalParticipant, didPublishTrack publication: LocalTrackPublication) { guard let track = publication.track as? VideoTrack else { return } DispatchQueue.main.async { self.localVideoView.track = track } } func room(_: Room, participant _: RemoteParticipant, didSubscribeTrack publication: RemoteTrackPublication) { guard let track = publication.track as? VideoTrack else { return } DispatchQueue.main.async { self.remoteVideoView.track = track } } } ``` ### Screen Sharing See [iOS Screen Sharing instructions](Docs/ios-screen-sharing.md). ## Integration Notes ### Thread safety Since `VideoView` is a UI component, all operations (read/write properties etc) must be performed from the `main` thread. Other core classes can be accessed from any thread. Delegates will be called on the SDK's internal thread. Make sure any access to your app's UI elements are from the main thread, for example by using `@MainActor` or `DispatchQueue.main.async`. ### Swift 6 LiveKit is currently compiled using Swift 6.0 with full support for strict concurrency. Apps compiled in Swift 6 language mode will not need to use `@preconcurrency` or `@unchecked Sendable` to access LiveKit classes. ### Memory management It is recommended to use **weak var** when storing references to objects created and managed by the SDK, such as `Participant`, `TrackPublication` etc. These objects are invalid when the `Room` disconnects, and will be released by the SDK. Holding strong reference to these objects will prevent releasing `Room` and other internal objects. `VideoView.track` property does not hold strong reference, so it's not required to set it to `nil`. ### AudioSession management LiveKit will automatically manage the underlying `AVAudioSession` while connected. The session will be set to `playback` category by default. When a local stream is published, it'll be switched to `playAndRecord`. In general, it'll pick sane defaults and do the right thing. However, if you'd like to customize this behavior, you would override `AudioManager.customConfigureAudioSessionFunc` to manage the underlying session on your own. See [example here](https://github.com/livekit/client-sdk-swift/blob/1f5959f787805a4b364f228ccfb413c1c4944748/Sources/LiveKit/Track/AudioManager.swift#L153) for the default behavior. ### Integration with CallKit To integrate with CallKit for background-triggered incoming calls, LiveKit's audio session must be synchronized with CallKit's audio session: 1. Add `import LiveKitWebRTC` to your CallProvider file. 2. In your `CXProviderDelegate` implementation, add the following: ```swift func provider(_ provider: CXProvider, didActivate audioSession: AVAudioSession){ LKRTCAudioSession.sharedInstance().audioSessionDidActivate(audioSession) // ... } func provider(_ provider: CXProvider, didDeactivate audioSession: AVAudioSession) { LKRTCAudioSession.sharedInstance().audioSessionDidDeactivate(audioSession) // ... } ``` ### iOS Simulator limitations - Publishing the camera track is not supported by iOS Simulator. ### ScrollView performance It is recommended to turn off rendering of `VideoView`s that scroll off the screen and isn't visible by setting `false` to `isEnabled` property and `true` when it will re-appear to save CPU resources. `UICollectionViewDelegate`'s `willDisplay` / `didEndDisplaying` has been reported to be unreliable for this purpose. Specifically, in some iOS versions `didEndDisplaying` could get invoked even when the cell is visible. The following is an alternative method to using `willDisplay` / `didEndDisplaying` : ```swift // 1. define a weak-reference set for all cells private var allCells = NSHashTable<ParticipantCell>.weakObjects() ``` ```swift // in UICollectionViewDataSource... public func collectionView(_ collectionView: UICollectionView, cellForItemAt indexPath: IndexPath) -> UICollectionViewCell { let cell = collectionView.dequeueReusableCell(withReuseIdentifier: ParticipantCell.reuseIdentifier, for: indexPath) if let cell = cell as? ParticipantCell { // 2. keep weak reference to the cell allCells.add(cell) // configure cell etc... } return cell } ``` ```swift // 3. define a func to re-compute and update isEnabled property for cells that visibility changed func reComputeVideoViewEnabled() { let visibleCells = collectionView.visibleCells.compactMap { $0 as? ParticipantCell } let offScreenCells = allCells.allObjects.filter { !visibleCells.contains($0) } for cell in visibleCells.filter({ !$0.videoView.isEnabled }) { print("enabling cell#\(cell.hashValue)") cell.videoView.isEnabled = true } for cell in offScreenCells.filter({ $0.videoView.isEnabled }) { print("disabling cell#\(cell.hashValue)") cell.videoView.isEnabled = false } } ``` ```swift // 4. set a timer to invoke the func self.timer = Timer.scheduledTimer(withTimeInterval: 0.1, repeats: true, block: { [weak self] _ in self?.reComputeVideoViewEnabled() }) // alternatively, you can call `reComputeVideoViewEnabled` whenever cell visibility changes (such as scrollViewDidScroll(_:)), // but this will be harder to track all cases such as cell reload etc. ``` For the full example, see 👉 [UIKit Minimal Example](https://github.com/livekit/client-example-collection-swift/tree/main/uikit-minimal) # Frequently asked questions ### How to publish camera in 60 FPS ? - Create a `LocalVideoTrack` by calling `LocalVideoTrack.createCameraTrack(options: CameraCaptureOptions(fps: 60))`. - Publish with `LocalParticipant.publish(videoTrack: track, publishOptions: VideoPublishOptions(encoding: VideoEncoding(maxFps: 60)))`. # Known issues ### Avoid crashes on macOS Catalina If your app is targeting macOS Catalina, make sure to do the following to avoid crash (ReplayKit not found): 1. Explicitly add "ReplayKit.framework" to the Build Phases > Link Binary with Libraries section 2. Set it to Optional <img width="752" alt="replykit" src="https://user-images.githubusercontent.com/548776/201249295-51d9cb76-32bd-4b10-9f4c-02951d1b2edb.png"> - I am not sure why this is required for ReplayKit at the moment. - If you are targeting macOS 11.0+, this is not required. # Getting help / Contributing Please join us on [Slack](https://livekit.io/join-slack) to get help from our devs / community members. We welcome your contributions(PRs) and details can be discussed there. <!--BEGIN_REPO_NAV--> <br/><table> <thead><tr><th colspan="2">LiveKit Ecosystem</th></tr></thead> <tbody> <tr><td>LiveKit SDKs</td><td><a href="https://github.com/livekit/client-sdk-js">Browser</a> · <b>iOS/macOS/visionOS</b> · <a href="https://github.com/livekit/client-sdk-android">Android</a> · <a href="https://github.com/livekit/client-sdk-flutter">Flutter</a> · <a href="https://github.com/livekit/client-sdk-react-native">React Native</a> · <a href="https://github.com/livekit/rust-sdks">Rust</a> · <a href="https://github.com/livekit/node-sdks">Node.js</a> · <a href="https://github.com/livekit/python-sdks">Python</a> · <a href="https://github.com/livekit/client-sdk-unity">Unity</a> · <a href="https://github.com/livekit/client-sdk-unity-web">Unity (WebGL)</a></td></tr><tr></tr> <tr><td>Server APIs</td><td><a href="https://github.com/livekit/node-sdks">Node.js</a> · <a href="https://github.com/livekit/server-sdk-go">Golang</a> · <a href="https://github.com/livekit/server-sdk-ruby">Ruby</a> · <a href="https://github.com/livekit/server-sdk-kotlin">Java/Kotlin</a> · <a href="https://github.com/livekit/python-sdks">Python</a> · <a href="https://github.com/livekit/rust-sdks">Rust</a> · <a href="https://github.com/agence104/livekit-server-sdk-php">PHP (community)</a> · <a href="https://github.com/pabloFuente/livekit-server-sdk-dotnet">.NET (community)</a></td></tr><tr></tr> <tr><td>UI Components</td><td><a href="https://github.com/livekit/components-js">React</a> · <a href="https://github.com/livekit/components-android">Android Compose</a> · <a href="https://github.com/livekit/components-swift">SwiftUI</a></td></tr><tr></tr> <tr><td>Agents Frameworks</td><td><a href="https://github.com/livekit/agents">Python</a> · <a href="https://github.com/livekit/agents-js">Node.js</a> · <a href="https://github.com/livekit/agent-playground">Playground</a></td></tr><tr></tr> <tr><td>Services</td><td><a href="https://github.com/livekit/livekit">LiveKit server</a> · <a href="https://github.com/livekit/egress">Egress</a> · <a href="https://github.com/livekit/ingress">Ingress</a> · <a href="https://github.com/livekit/sip">SIP</a></td></tr><tr></tr> <tr><td>Resources</td><td><a href="https://docs.livekit.io">Docs</a> · <a href="https://github.com/livekit-examples">Example apps</a> · <a href="https://livekit.io/cloud">Cloud</a> · <a href="https://docs.livekit.io/home/self-hosting/deployment">Self-hosting</a> · <a href="https://github.com/livekit/livekit-cli">CLI</a></td></tr> </tbody> </table> <!--END_REPO_NAV--> ", Assign "at most 3 tags" to the expected json: {"id":"12644","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"