using a cocoapod that is in a library that is in an app?

RE: using a cocoapod that is in a library that is in an app?

Mostafa Berg — Mon, 08 May 2017 07:10:37 GMT

@robmonti, it's a much better route for you that's true, you need to decouple your code and it'll be easier to use it with other libraries as well, also remember that you can have private cocoapods that are not published to the cocoapods trunk if you are not planning to release this to the public

Please remember to the mark the question as answered to make the solution visible to future search visitors :)

RE: using a cocoapod that is in a library that is in an app?

robmonti — Fri, 05 May 2017 15:15:24 GMT

Thanks for the reply. While I was not originally using our library as a cocoapod (we were adding the library directly into our app), it looks like this may be the route I have to take.

RE: using a cocoapod that is in a library that is in an app?

Mostafa Berg — Tue, 02 May 2017 09:40:37 GMT

Hi robmonti!

This is a good question, to use the library as a dependency you simply need to add it as a dependency to your own cocoapod's podspec file, to do that, simply remove all the references to iOSDFULibrary from your podfile, then open up your myLibrary.podspec file and add a dependency field, it should look like the way we added zip as a denpendency to our podspec, you may see that here for reference.

Simply, replace

s.dependency 'Zip', '~> 0.7'

to be

s.dependency 'iOSDFULibrary', '~> 3.0'

Note: You do not need to add Zip as a dependency, since our library already has that built in.

after doing that you should go to your app and run

pod install

and you should be set to go, next time you run

pod trunk push

to release your cocoapod, your dependencies should be ready out of the box.

hope this helps, if you encounter issues just let us know.