Open Radar

 
Summary:
In a project containing a folder reference and a target that copies the folder into its product, changes to files inside the referenced folder do not cause Xcode to re-copy the folder into the product.

Steps to Reproduce:
1. Create a project from the Mac OS X application project template.
2. Create a folder within the project root.
3. Add a file to the project root.
4. Add a reference to the folder to the project.
5. Add the folder reference to the application target's Copy Bundle Resources phase.
6. Build.
7. Edit the file, making sure to save your work (if appropriate).
8. Build.

Expected Results:
Xcode re-copies the folder, or (optimally) the changed file alone.

Actual Results:
Xcode does nothing, successfully.

Regression:
No.

Workaround:
Touch the folder before building.

Notes:
One real example is Adium, in which the “folders” in question are bundles: Emoticon, status-icon, service-icon, Dock-icon, and sound packs. Changing any of the files inside the pack should cause Xcode to re-copy the pack (or the changed files) in the next build.

I was reminded of this by a Stack Overflow question (http://stackoverflow.com/questions/1438898/xcode-building-and-resources-folders). The questioner is experiencing the same problem building their iPhone app.

[Uploaded test app: http://boredzo.org/stuph/LinesOfText-r0.tbz ]