Cocoapods: pod install does not pull down latest commit from master

[rex-remind101]

I'm pointed at master for a repo's podspec :branch => 'master', this repo is used by a project of mine. I made some changes to master and pushed them upstream, but when I did a pod install the changes were not reflected in the project that's using the repo. I had to manually delete the cocoapods cache and then pod install for the changes to show.

[kylef]

pod install will not update your dependencies, you would need to use pod update to update them.

[hemangshah]

@kylef, Why don't I have the latest code which is in my release?
Github: https://github.com/hemangshah/printer
CocoaPods: https://cocoapods.org/pods/printer-logger

Thanks!

[reitzig]

@kylef pod update won't pull the new commit either.

[albertbori]

You can force it to update by changing the target :commit: value in your Podfile.lock:

[reitzig]

@albertbori Sure, but that's missing the point. I don't expect to do something manually if you point to a branch. I expect the dependency to be at the same state as the sources I get when cloning the repo, checking out that branch, and building.

In terms of use cases, developing a module and one of its dependencies at the same time is a huge annoyance: full pod cache clean; rm -rf Podfile.lock Pods; pod install and rebuild takes a _lot_ more time than a plain pod install that just pulls the latest revision of a single dependency.

[KimiChiu]

Here's how I did:

1. remove pod 'library' from Podfile
2. run pod install
3. add pod 'library' back
4. run pod install again