Best practice for pod in multiple targets

[damienpontifex]

I require a pod to be built and be available in multiple targets. The targets are:

• An iOS app
• Cocoa Touch Framework (gets linked via Embedded Binaries in Xcode)

I see a couple of ways of doing it

1. In my Podfile, define the pod against both targets and install as such
2. Define the pod only against my Framework target and expose the pod framework publicly inside that to use in my iOS app somehow

I am enquiring if anyone has any guidelines/experience for the best way to achieve this. I have been running into issues with option 2 above resulting in an error of 'No such module' in my iOS app. I was able to resolve this by adding to the Framework Search Paths of my iOS app $(BUILD_DIR)/$(CONFIGURATION)$(EFFECTIVE_PLATFORM_NAME)/Pods- which then resolved the built module.

If I do option 1, then on archive I get errors for the specific pod target frameworks of 'invalid or unsupported format for signature'

I would have thought it could be contained within the Cocoa Touch Framework target and when linked with my app, be also available if it was made public somehow.

[orta]

Best practice questions should be taken to Stack Overflow, where you will get more eyes on it, with an incentive for readers to post opinions. We keep github issues reserved for feature requests and bug reports. Sorry.