Xcode 3.x to 4.0 transition tips

To change your build configuration, choose Product/Edit scheme. You can select different build configurations for run/test/profile/analyze/archive.

Which profile to use is determined in different build configurations. To view/edit a build configuration, in the left panel select the project navigator and click the top most entry (project). The settings of build configuration will show up in the right panel.

Building and submitting app to app store is done through archive, therefore the build configuration used by archive should choose distribution profile in code signing identity. However this makes the app cannot be run with Xcode. To run it you need to use developer profile as code signing identity.

Use Subversion with Xcode

## create svn repo
svnadmin create /path/to/your/repo

## create directory in svn repo
svn mkdir -m "blah" file:///path/to/your/repo/trunk

## import project to svn repo
svn import ./YourProjectName -m "comments" file:///path/to/your/repo/trunk/YourProjectName

## checkout project
svn checkout file:///path/to/your/repo/trunk/YourProjectName /path/to/local/dir

## delete directory from repo
svn rm -m "blah" file:///path/to/your/repo/trunk/YourProjectName/dir
svn update

## add a file
svn add -m "blah" file

## delete a file
svn rm -m "blah" file

## commit change
svn commit -m "blah"

## make file executable in repo
svn propset svn:executable on file

It is suggested to remove build directory before importing Xcode project to svn. Build directory contains some binary files which are easily causing problem with svn.

Another common issue is library files are not imported into svn by the Xcode built-in SCM. When you checkout the project to a new location and try to build it, the build fails due to missing libraries. You need to add the libraries to svn by command line.

Xcode error: No launchable executable present at path

If this error shows up after the name of the executable changes in Xcode, restarting Xcode could solve this problem.