CocoaPods/CocoaPods — Issue #139: Checking for outdated/missing pods
Author: lukeredpath
Created: 2012-02-24 23:30:48+00:00
State: open

Currently, when you change your Podfile (update, add or remove a dependency), there's no way of communicating that change with the rest of your team, unless they scan the diffs each time they pull.

This can leave them with build problems if your app code now depends on a new or changed Pod.

It seems to me that we should be able to detect this somehow. On the assumption that the Pods directory is left out of version control, we could store a manifest of some kind in there - if this doesn't match up with the current Podfile, is there a way we can alert the user?

I'm thinking ideally, it would be something that would fail the build; a run script phase perhaps?