app.pods might be called multiple times when AFMotion (https://github.com/clayallsopp/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: https://gist.github.com/4009695
Two app.pods: https://gist.github.com/4009693
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 =\
+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.
Defer installing Cocoapods until right before the app is built. Fixes #…
Automatically add the cocoa pod now that the issue has been resolved