You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My understanding is that the inability to include multiple KMP xcframeworks had been resolved, as mentioned in KT-42254:
Kotlin/Native compiler can produce Swift/Obj-C frameworks from Kotlin code. Multiple frameworks can be used in the single application, they are usually properly isolated from each other.
I did a quick experiment, and I am able to build an iOS app with multiple KMP xcframeworks. There are warts with the process (e.g., all the frameworks will have their own KotlinBase, KotlinNumber, KotlinMutableSet, etc., which makes it impossible to cast base types between one framework and the other), but it does seem to be possible.
Our use case is that we (the Skip project) would like to have a bluetooth framework that can be included independently from the iOS and Kotlin sides of the app without needing to make the user manually build and include the framework. For the time being, we will follow your advice and make our own cover library and publish the xcframework as a GitHub release, but it may be something you want to consider adding in the future for your own users.
A more general benefit is that iOS users who don't use KMP at all would still be able to use the framework by adding it as a SwiftPM binary dependency.
Originally posted by @marcprux in #703 (comment)
The text was updated successfully, but these errors were encountered: