Open Radar

 
Like many (most) programmers, my intention with my Xcode project is to make all paths within it relative, either directly or indirectly, or relative to the project, workspace, symbolic roots or build directory. Something not tying it directly to my system.

Occasionally, Xcode will — without warning me — make some new file I drop into the project or workspace ABSOLUTE_PATH.

I have no good steps to reproduce this happening by accident. I can tell you that even as I was typing this up, I found that my workspace was using an absolute path to reference one of the projects contained within.

Steps to Reproduce:
This is an entirely synthetic way to create this problem. Xcode will occasionally do it on its own, but I have no reproduction steps for that.

1. Create a new iOS project using Single View application template.
2. ViewController.h and adjust it to "Absolute To Path."
3. Build.
4. Copy the entire project (including all files) to another machine, with a different user name. Build again.

Expected Results:
At step 3, there should be a warning that the project includes absolute paths.

Actual Results:
You have no indication anything is wrong until step 5. At this point, you have to make guesses about the computer the project was created on, even though you may not have access to it.

Version:
6.0.1 (6A317)

Notes:
That entries in an Xcode workspace or project can be added as absolute paths is a long-standing defect. However, even if this was corrected first, existing workspaces and projects could still have unexpected absolute paths. I think the consequence is more important to address here.

There really is no good reason to have an absolute path now that Xcode has "Source Trees."

Configuration:


Attachments: