-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple Class Implementations Warnings and Crash on iOS 17 When Starting Stream with LiveKit v1.1.2 #257
Comments
I am not able to reproduce this one.
Is there something unique with your setup ? |
Hello @hiroshihorie , Thank you for your prompt response. I would like to provide some additional details regarding the environment and setup in which these issues are occurring: Development Environment:
Configuration:
Implementation Details:I am currently utilizing own camera for broadcaster purposes only, with the following configuration: let cameraCaptureOptions = CameraCaptureOptions(position: .front, preferredFormat: nil, dimensions: .h360_169, fps: 20)
let options = RoomOptions(defaultCameraCaptureOptions: cameraCaptureOptions, adaptiveStream: false, dynacast: false)
self.roomOptions = options
self.room = Room(delegate: self, roomOptions: roomOptions) Streamer/broadcaster settings self.localVideoTrack = LocalVideoTrack.createBufferTrack(name: Track.cameraName, source: .camera, options: BufferCaptureOptions(dimensions: .h720_169, fps: 30))
self.localAudioTrack = LocalAudioTrack.createTrack(options: roomOptions.defaultAudioCaptureOptions) Co-streamer settings self.localVideoTrack = LocalVideoTrack.createCameraTrack(options: roomOptions.defaultCameraCaptureOptions)
self.localAudioTrack = LocalAudioTrack.createTrack(options: roomOptions.defaultAudioCaptureOptions) Observed Behavior:Upon running the application with the above setup, I encounter the following runtime warnings:
I am wondering if there might be something unique about my setup that could be leading to these issues, and I would appreciate any insights or recommendations you might have to resolve this problem. Thank you in advance for your assistance. Best, |
@isandeepj could you create a minimal project that is able to reproduce these warnings? From the warnings it looks like your app is linking against two copies of LiveKit SDK. Though I could be wrong and something else is going on. |
I am experiencing a challenging issue with the LiveKit SDK integration into my iOS project on Xcode 15. I have tried installing the SDK using both Swift Package Manager and CocoaPods, each in separate instances and on a completely fresh project. However, the outcome has been the same, with persistent errors during runtime. The specific warnings I am receiving are as follows:
These warnings seem to indicate that there are multiple implementations of the LiveKit SDK classes in my project’s runtime, which is causing ambiguity about which implementation should be used. I have made sure to clean the build folder, remove all derived data, and even delete and re-install all the dependencies. Despite these efforts, the warnings persist. Can you please guide me on how to resolve these issues? Any help or insights would be greatly appreciated. Thank you |
What's your Xcode version ? and can you try with Zombie Objects off ? |
Xcode 15.0.1 version is used, and if we turn off Zombie Objects then not showing the above error. @hiroshihorie any thoughts on below crash logs?
|
My guess is that it's related to Do you read the |
I've released v1.1.5, can you try it out ? |
WebRTC symbols in v2 are prefixed with "LK" I don't think you will get any "Multiple class implementations exist" error. |
Describe the bug
When starting a stream using LiveKit on iOS 17, I encounter warnings indicating that multiple class implementations exist in the runtime for several _NSZombie_LiveKitClient classes. This could potentially lead to unpredictable behavior.
SDK Version
LiveKit Client SDK for Swift v1.1.2
iOS Version
iOS 17
Steps to Reproduce
Expected behavior
The application should stream without warnings or crashes.
Screenshots
N/A
Logs
** Crash Stack Trace**
The text was updated successfully, but these errors were encountered: