Cocoapods: Pod cache contents interferes with 'pod spec lint' operations
- [🌈] I've read and understood the *CONTRIBUTING guidelines and have done my best effort to follow.
Report
What did you do?
While working with a private CocoaPod, we had a Swift file that we removed from the project, and removed from the GitHub repository. When trying to perform a 'pod spec lint --verbose' on a new version, the compilation kept complaining that the file that we removed was causing a compilation error.
Performing a 'pod cache clean' fixed the problem, suggesting that the "ghost" file still remained in the cache.
What did you expected to happen?
Performing a 'pod spec lint' operation should use the code that is in the current repository.
What happened instead?
The 'pod spec lint' failed because a removed file from my repository was not removed from my pod cache.
Curtis-Halbrook
All 3 comments
Did you change what the git tag pointed to, perchance?
segiddins
on 21 Apr 2016
I did indeed.
On Apr 21, 2016, at 4:32 PM, Samuel Giddins [email protected] wrote:
Did you change what the git tag pointed to, perchance?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub https://github.com/CocoaPods/CocoaPods/issues/5186#issuecomment-213102516
Curtis-Halbrook
on 22 Apr 2016
That's purposefully unsupported -- if you change what a git tag points to, you'll have to clean the cache by running pod cache clean POD
segiddins
on 22 Apr 2016
Related issues
evermeer
·
3Comments
soleares
·
3Comments
pallaviMN
·
3Comments
tlandsmancars
·
3Comments
pronebird
·
3Comments
Most helpful comment
That's purposefully unsupported -- if you change what a git tag points to, you'll have to clean the cache by running
pod cache clean POD