-
Notifications
You must be signed in to change notification settings - Fork 6
generateDummyFramework: resource must not be null #23
Comments
@inickt did you found the problem/solution? |
@extmkv I did not. I am currently using the default Cocoapods plugin with the following in our targets.withType<org.jetbrains.kotlin.gradle.plugin.mpp.KotlinNativeTarget> {
binaries.withType<org.jetbrains.kotlin.gradle.plugin.mpp.Framework> {
isStatic = false
export(project(":common"))
}
} This lets us have a dynamic framework and export our other project in the framework, and we are manually maintaining the podspec based of the one generated from this plugin so everything works okay in Xcode. |
Thanks for the update @inickt ! I'm using the version 0.12 of the plugin, I notice the plugin is trying to copy the resource |
@inickt Are you certain that you're actually creating a dynamic framework there? The podspec that generates when I do similar indicates static. See https://github.com/touchlab/KaMPKit/blob/rw/official-cocoapods/shared/shared.podspec#L10 I'd like to understand this better to determine whether we should continue to maintain this fork or start pointing people back toward the official plugin. |
@russhwolf From what I can tell I think its working? My main reasons for making a dynamic framework were to:
Everything seems ok right now (seeing a |
Hey all! Thanks for maintaining this plugin. I wanted to be able to export dependencies and use a dynamic framework for my project so this looks great.
I am having a problem integrating the plugin. For both my project and a clean clone of https://github.com/touchlab/KaMPKit I am unable to run the
generateDummyFramework
gradle task, which causes the podspec task to fail. I am using the Android Studio 4.2 Preview to work around some Big Sur issues. Here is a stacktrace:Not sure why the dummy task is failing, it's working okay with the upstream Cocoapods plugin. Please let me know if there is any other information you need to help with debugging. Thanks!
The text was updated successfully, but these errors were encountered: