Submitting app today and I have a question about the Xcode Project Name

jlerma1 · 09-13-2011, 11:35 AM

Hello,

I plan on submitting my app later on today and I was wondering about the following thing:

when I created this Xcode Project, I gave it a generic name calling it "Primary". Everything in that Xcode project references that name.

I have the real app name populated in the plist summary, Called "Holidays 4 Kidz" as an example.

That is the name that shows up below the icon in the simulator when i test it and thats the name I will give it in itunes connect.

Here is the question. Do I need to rename the project "Holidays 4 Kidz" or can i submit the Xcode project named Primary as long as the App name in itunes connect references the "Holidays for Kidz"? Does this make a difference?

Let me know if I am overreacting. This is my first app and it is time sensitive (because of the Holidays) and I want to make sure I do everything right.

Thanks,

J

nobre84 · 09-13-2011, 11:37 AM

There is no problem. The project name will often influence the executable name, but that name is not visible for the users and Apple does not care what you name it. You can still change that one if you wish, but its not required.

jlerma1 · 09-13-2011, 11:53 AM

Quote:

Originally Posted by nobre84

There is no problem. The project name will often influence the executable name, but that name is not visible for the users and Apple does not care what you name it. You can still change that one if you wish, but its not required.

Thanks for the response. how do I change the entire project name, while maintaining the snapshot backups and making sure that all of the items named Primary throughout the project get changed?

Or is the last part of my question too much?

Thanks,

J

**dljeffery** · 09-13-2011, 09:57 PM

Quote:

Originally Posted by jlerma1

Thanks for the response. how do I change the entire project name, while maintaining the snapshot backups and making sure that all of the items named Primary throughout the project get changed?

Or is the last part of my question too much?

Thanks,

J

It sounds like maybe you are relying on Xcode snapshots as a form of version control. If so, don't do that. Set up real version control (Subversion or Git). Do it before you attempt something like refactoring your project name (and related class names, etc.) across your entire codebase. And from then on, use Subversion/Git for version control, not Xcode snapshots.

jlerma1 · 09-13-2011, 10:03 PM

Quote:

Originally Posted by dljeffery

It sounds like maybe you are relying on Xcode snapshots as a form of version control. If so, don't do that. Set up real version control (Subversion or Git). Do it before you attempt something like refactoring your project name (and related class names, etc.) across your entire codebase. And from then on, use Subversion/Git for version control, not Xcode snapshots.

Hi DJeffrey,

you are correct, because I am a new developer with minimum knowledge I am using snapshots as version control. I need to learn about what you said to do but for now, I can upload my "primary" xcode" project and worry about the subversion/GIT another time.

Thanks,

J

**dljeffery** · 09-13-2011, 10:15 PM

Now is always better than later when it comes to version control.

Creating a Subversion repository and adding your current sources to it should take you at most an hour to figure out. I'd encourage you to do that before submitting your app, so that you will always be able to refer to the exact code you shipped for your first version, should the need arise.