Can't call app.pods multiple times #38

clayallsopp opened this Issue Nov 4, 2012 · 2 comments


None yet

3 participants


app.pods might be called multiple times when AFMotion ( I.e. you require AFMotion and also use your own pods in the project.

But calling it multiple times produces different Podfiles, and some pods don't get built. This can be repro'd with just one Rakefile with no extra gems.


One app.pods:
Two app.pods:

Both logging statements in the second example ran, so the block was executed. I tried to look at the source, but it dives into full Cocoapods territory at that point =\

cc @alloy

+1 - Just ran into this by distributing a pod in my gem by following the documentation on the RM website, but can't have pods inside my project rakefile or the project won't build.

It would be great if someone familiar with motion-cocoapods could look into this. It makes writing wrappers for CocoaPods a little more difficult.

@clayallsopp clayallsopp added a commit to clayallsopp/motion-cocoapods that referenced this issue Sep 29, 2013
@clayallsopp clayallsopp Defer installing Cocoapods until right before the app is built. Fixes #… 9e82593
@Watson1978 Watson1978 closed this in #71 Sep 30, 2013
@macfanatic macfanatic referenced this issue in ryanlntn/indoctrinator Mar 23, 2014

Automatically add the cocoapod #3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment