On May 18, 2017, at 15:23 , Bryce Glover <email@hidden> wrote:
So perhaps you’d have to change all of the in-bundle identifiers along with the bundle name to get everything to propagate correctly.
There are multiple things to keep in mind.
— Remember that when you create a project from a template, there are several identifiers that are derived (at creation time) from the single Project Name field. The in-Xcode project rename dialog is a convenience that “knows” where it originally used the project name, and so knows which places need to be changed.
— The problem with renaming the project externally may have been a bug that’s fixed. Nasty-detail bugs are fixed in Xcode all the time, and it’s easy to condemn the current Xcode for bugs in the previous versions. (OTOH there are plenty of bugs that don’t get fixed over a long span of versions, so there’s that too.)
— Xcode is much better about tracking file change activity and knowing what effect is has on the repository. This is definitely one area that used to suck, and is currently much improved. I was kind of shocked yesterday to see a build warning telling me that a file from the repository was missing. That was new.
— Historically, Xcode has had difficulty tracking changes to directory names in the paths to files tracking in a git repository. When you rename the project in the Finder, you’re actually renaming a directory that’s a couple of levels above the actual project file. Doing this outside Xcode may well mess up the repository. The project is inside the repository, not the other way around.
|