livekit / client-sdk-swift

LiveKit Swift Client SDK. Easily build live audio or video experiences on iOS, macOS, tvOS, and visionOS.
https://livekit.io
Apache License 2.0
187 stars 93 forks source link

Build error - #428

Open robert-sparhawk-simplisafe opened 1 month ago

robert-sparhawk-simplisafe commented 1 month ago

Describe the bug I see the following when I try to build my project when LiveKit 2.0.11 or 2.0.12 is specified in SPM:

Screenshot 2024-07-11 at 5 52 32 PM

Could not find or use auto-linked framework 'AudioUnit': framework 'AudioUnit' not found Could not find or use auto-linked framework 'CoreAudioTypes': framework 'CoreAudioTypes' not found Undefined symbol: _OBJC_CLASS_$_LKRTCEAGLVideoView

I have tried linking the two frameworks in my project file and confirmed that they exist inside my Xcode app package in my filesystem but one or the other is always unable to be found at build time.

SDK Version 2.0.11, 2.0.12

iOS/macOS Version Testing on iOS 17.0.1, targeting iOS 15

Xcode Version Xcode 15.4 Swift 5

Steps to Reproduce

  1. Update SPM to LiveKit 2.0.11 or 2.0.12
  2. File -> Packages -> Reset package caches
  3. Build

Expected behavior The project successfully builds

Screenshots Here are my log errors:

Screenshot 2024-07-11 at 5 52 32 PM

Logs Currently unsure if I can post logs.

hiroshihorie commented 1 month ago

Hmm, this is odd. Can you "Reset Package Caches" ?

robert-sparhawk-simplisafe commented 1 month ago

Thank you for your response! Neither Clean Build Folder, Reset Package Caches, or deleting Derived Data have any effect on the issue.

davidzhao commented 1 month ago

@robert-sparhawk-simplisafe we are unable to reproduce this. If you are able to modify the example project so that it could reproduce the error, that'll help us to see what the error path is.

robert-sparhawk-simplisafe commented 1 month ago

I was unable to solve this but the build error goes away if I use LKRTCMTLVideoView instead of LKRTCEAGLVideoView.

hiroshihorie commented 1 month ago

Oh ok I think you shouldn't use LKRTCEAGLVideoView I think we removed it but looks like headers were still being exposed.