Hi I'm facing issue packaging my kmp library with ...
# compose-ios
a
Hi I'm facing issue packaging my kmp library with compose ui and resources (images/strings) using cocoapods plugin, Currently using this task to package
podPublishReleaseXCFramework
the framework is generated under
build/cocoapods/publish/release
In the podspec file it links the resources with this line
Copy code
spec.resources = ['build/compose/cocoapods/compose-resources']
I'm manually copying
build/compose/cocoapods/compose-resources
into
build/cocoapods/publish/release
While keeping the nested folders Should
podPublishReleaseXCFramework
handle that ? is there another task i should use ? Also i have to run the project once using xcode/plugin to generate the resources What's a proper way/workaround to package iOS pod with compose resources ?
k
It isn't supported yet
a
@Konstantin Tskhovrebov Thanks , should I create an issue ? So far the workaround i'm thinking of for the ci/cd • Run app once
Copy code
/Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -workspace /iosApp/iosApp.xcworkspace -scheme iosApp -configuration Debug OBJROOT=/build/ios SYMROOT=/build/ios -allowProvisioningDeviceRegistration -allowProvisioningUpdates
• Generate framework
Copy code
podPublishReleaseXCFramework
• copy build
Copy code
cp -R build/compose/cocoapods/compose-resources build/cocoapods/publish/release/build/compose/cocoapods/
k
KT-66790 Provide compose resources together with XCFramework (with SPM or Cocoapods)
🙏 1
a
@Konstantin Tskhovrebov is there a way I can contribute fixing this issue? I don’t see Resources in the list available to external contributors in the contribution guidelines. It prevents me from using Compose Resources in an XCFramework distributed via SPM and I’m sure it also impacts many others as it is a fairly common use case.