Sorry Apple, but your color themes are just awful. There’s no way to candy coat this. They suck.

So, readers, I have converted several easy-on-the-eyes TextMate and Vim themes for xcode and provided them for You! Go get them from Github and save yourself some eyestrain.

Download

Contains themes:

• 2morrow Night
• 2morrow Night (Eighties)
• Coal Graal
• Glitterbomb
• Kellys
• Monokai
• Night
• Resesif
• Sidewalk Chalk

Installation

Place the

~/Library/Developer/Xcode/UserData/FontAndColorThemes

folder of your home directory.

The original iPhone, iPhone 3G, and first two generations of iPod touch used processors supporting the armv6 instruction set. However, with the iPhone 3GS, Apple moved to the more modern, but backwards compatible, armv7 instruction set, and the iPhone 5 includes armv7s. To support older devices while taking advantage of the capabilities of the newer processors, iOS supports fat binaries, which are multiple executables, each for a separate instruction set, combined into one.

(more...)

Finally, Apple introduced native Git support in Xcode 4. Git is now the standard version control system you can use within Xcode. The Apple engineers did a great job in integrating Git into Xcode 4 … but there is room for improvements  Tools like gitx still are essential for me to keep track of all the branches in the Git-repository.

# Exclude the build directory
build/*

# Exclude temp nibs and swap files
*~.nib
*.swp

# Exclude OS X folder attributes
.DS_Store

# Exclude user-specific XCode 3 and 4 files
*.mode1
*.mode1v3
*.mode2v3
*.perspective
*.perspectivev3
*.pbxuser
*.xcworkspace
*.xcuserstate
xcuserdata

one can also specify a global gitignore file in ~/.gitconfig:

[core]
excludesfile = /Users/username/.gitignore

Xcode 4 on Mac OS X Lion reopens all the projects from the last session. This is pretty frustrating to me most of the time as I switch from working on a client app or two plus a couple of my own. I’d rather be able to quit and reopen a fresh session to work on what I want at that moment, not have to sift through four or five spaces with different Xcode projects to find the one I want… every time I switch to and from another app.

There used to be a way of preventing this in Xcode’s preference plist, but this no longer works. Instead, a solution is to set the following folder as locked, so Xcode can’t write to it to save the state.

~/Library/Saved\ Application\ State/com.apple.dt.Xcode.savedState

You’ll want to delete the contents of this, then get info and click the locked checkbox. Et voila, no more projects reopening themselves.

It is obvious that Xcode knows exactly what caused the crash, but its always saying that the main file caused the exception...???

You should also ensure that you have breakpoints set for all exceptions. This will cause Xcode to stop at the line where the exception is occurring. Do the following [in Xcode 4]:

1. In the Project Navigator on the left side of Xcode, click on the breakpoint navigator (almost all the way to the right hand side of the top button bar. The icon looks like a fat right arrow).
2. At the bottom of the navigator, click the "+" button.
3. Click "Add Exception Breakpoint".
4. A new breakpoint will be created. It should be configured as needed but you can tweak its behavior.
5. Run your project and reproduce the exception.

Also you mentioned that you linked to some 3rd party libraries/frameworks. If the exception is occurring within those frameworks then you are going to have a hard time since the code is compiled and Xcode can't actually show you the line that caused the exception. If this is the case and you are certain you are using the libraries correctly, then you should file a bug report to the maintainers of those libraries.