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
I am working on a podspec where I want the user of that pod to be able to optionally include some assets. The default subspec 'Core' defines a resource bundle named 'Highstreet' and adds some vital files to it. I also define an optional subspec 'Assets' that the user can include if some default assets (e.g. icons) should be included as well. Using CocoaPods version 0.29.0, the assets from the 'Assets' subspec are not included in the resulting resource .bundle.
It seems to me that CocoaPods should be able to add files to an existing bundle and that my set-up should work. Please let me know if you agree.
Observations:
The Pods project contains a generated bundle target named 'Highstreet'. In its 'copy bundle resources' build phase, I see all files from the default subspec, not the optional 'Assets' subspec.
In 'Pods-resources.sh' I see that it installs the bundle twice:
This is not a supported behavior. Can you create an another bundle for the optional assets? The intent would be more clear as changing the contents of the bundle in this way could lead to user confusion.
I am working on a podspec where I want the user of that pod to be able to optionally include some assets. The default subspec 'Core' defines a resource bundle named 'Highstreet' and adds some vital files to it. I also define an optional subspec 'Assets' that the user can include if some default assets (e.g. icons) should be included as well. Using CocoaPods version 0.29.0, the assets from the 'Assets' subspec are not included in the resulting resource .bundle.
It seems to me that CocoaPods should be able to add files to an existing bundle and that my set-up should work. Please let me know if you agree.
Observations:
I've attached several relevant pieces of information below.
Podspec (excerpts from...)
Podfile of client project:
The text was updated successfully, but these errors were encountered: