This message was deleted.

cc @better-house-11852, in case he knows some trickery

We only have Swift package at the moment. I'm not familiar with .NET MAUI but is your "iOS Wrapper" written in ObjC ? Does simply adding a package dependency to your "iOS Wrapper" cause compile issues ? If so, can I see more details ?

I found this, it might help https://learn.microsoft.com/en-us/xamarin/ios/platform/binding-swift/

Hi all, Thanks for the replies. So we have already gone down both those roads. Long story short, we already have a solution set up using the Microsoft link from @freezing-lifeguard-43174. @better-house-11852 the iOS library that we created (that relied on the Twilio XCFramework) is written in Swift, but is using the -Objc compiler flag. The issue that we are having with it is when we try to ultimately build it using the Swift package, the resulting .h file errors about not being able to find the LiveKit import, even though it's clearly added and the code itself shows no errors. (Screenshot attached) We have also tried that exact link regarding creating our own version of the XCFramework from the LiveKit package. However we run into an error regarding “Logging unable to be found” when we try to follow it. (Using the command

xcodebuild -scheme LiveKit -sdk iphoneos -configuration Release ARCHS="arm64" BUILD_DIR="./Build" -destination "platform=iOS,arch=arm64"

Aside from that though, we don’t want to have to rely on modifying a 3rd party package just in order to get this MAUI application working. We’ve been having some other issues getting the Android side of MAUI working (we’ve not had the greatest integration experiences in general with MAUI), so unless there’s a semi-simple way around this, or unless an XCFramework solution will be supplied by yourselves, we will be abandoning the MAUI path and going down the native road instead for iOS/Android.