Replies: 2 comments 1 reply
-
Can you elaborate what Libra are you publishing via SPM? And where exactly MVIKotlin classes are not available? MVIKotlin is published to maven central. It should be added to your shared module a usual via dependencies, and then you assemble your framework. |
Beta Was this translation helpful? Give feedback.
-
Thanks for the clarification. I have no idea how to integrate a shared Gradle module into an iOS app via SPM. I think MVIKotlin is no different from any other KMP library here. You may need to build and publish MVIKotlin from sources manually, but that's just my guess. In samples, the shared module is integrated directly as one self-contained framework via embedAndSignAppleFrameworkForXcode. Another option is to use Cocoapods. These two options are officially supported by KMP and documented. |
Beta Was this translation helpful? Give feedback.
-
After publishing library via SPM for iOS , my KMM module classes I am able to access and use correctly while its transitive dependancy i.e mvikotlin classes are not available.
To confirm in .framework file header file I didn't find MviKotlin classes names . While in your sample proj I can see the class names present in its framework header .
Is there anything I am missing to mention in gradle file so mvikotlin is not being added in my frameworks header file .
Beta Was this translation helpful? Give feedback.
All reactions