Copy only changed Resources #1886

orta opened this Issue Mar 13, 2014 · 6 comments


None yet
6 participants

orta commented Mar 13, 2014

You'll have to excuse my ignorance upfront.

So the longest part of my compile cycle is the copy Resources phase in the build cycle, in theory this only needs to be ran when the file has been updated. I realize we need to take dev pods, and people being silly into account and always check but that doesn't mean it has to take 4-5 seconds each time.

2014-03-13 14_49_00

Could it potentially check a timestamp against one already in the app binary or something?


fabiopelosin commented Mar 14, 2014

Definitely this is one of the reasons why I would like to move away from the copy resources script and add the references of the resources to the user project and let Xcode do its thing. The copy resources script has always been suboptimal and always required too much work.

This is very close in logic to the acknowledgement metadata plugin.

(if nobody is against this is one of the top priorities for me)

kylef added the Resources label Mar 14, 2014


0xced commented Mar 20, 2014

May I point out that this is exactly what I suggested in #1439? 😉

CocoaPodsBot was assigned by orta Mar 29, 2014

Issue has been confirmed by @neonichu

CocoaPodsBot was unassigned by orta Mar 29, 2014


fabiopelosin commented Mar 30, 2014

@0xced 😄


kylef commented Sep 26, 2014

Isn't this already the case? CocoaPods uses rsync to perform the copying which already does this.

From the rsync man page:

Rsync finds files that need to be transferred using a "quick check" algorithm (by default) that looks for files that have changed in size or in last-modified time. Any changes in the other preserved attributes (as requested by options) are made on the destination file directly when the quick check indicates that the file's data does not need to be updated.


neonichu commented May 2, 2016

This issue has been inactive for a long time and will be closed because we want to move forward with a clean slate after our 1.0 release. If you believe this is still relevant, please retest with the 1.0 release candidate and comment with a reproducible project in order for this to become actionable again. Thanks!

neonichu closed this May 2, 2016

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