Operation failed with underlying error 4294956467

Thanx Xcode, that was very informative. I'll fix it right away! Oh wait, what was that...

Failed to launch simulator: Operation failed with underlying error 4294956467.

How to Control Which iPhone Simulator Starts

Been debugging application, verified several fixes were ok in simulator. Installed application on real device, just to find out bugs were still there!

What's going on?

Comparing iPhone and iPad Simulator Fonts

After I checked new Fonts in iPhone 4.2.1 it was just a question of time until I would start wondering iPhone vs iPad fonts.

Here's a quick and small chart about iPhone & iPad fonts in simulator. Would do comparison between real devices, but don't have enough of those. Does anyone ever :)

GDB: Program received signal: "EXC_BAD_ACCESS"

When your program crashes (not if, but when) with an error message...

GDB: Program received signal: "EXC_BAD_ACCESS"

...you know that there is most likely a memory leak somewhere. Your code just tried to access something, which was supposed to be there, which used to be there, which is going to be there, which should have been there - but right now is missing.

Apple AppStore status: Rejected

Some application submission status change emails go to "support" address only, not to iTunes Connect account holder.

There's excuse for everything, I can think of a dozen right away. Still find it rather strange that some emails go to account holder (review started) while other not (rejected). Makes one wonder many a things. Processes and people, for example. Theory and reality vs. achieved results. Investing time in right places.

Reason of Rejection: does not work with soon-to-be-released OS update.

Guess it's time to download beta SDK. Makes one wonder a few other things, too, like importance of backwards compatibility and legacy support. Seen different solutions for it, but kind of like Apple approach. Good for business, too.

Btw the content of "reject" email was just excellent. There was everything I could ask for and then some. Definitely time invested in right place!

How to Make Instruments Show Your Own Code

Debugging memory leaks with Instruments. Great tool, but would be more useful, if I could see there references to my code.

Turned out it's a known iPhone OS 3.0 defect, almost two years old! No idea why it hasn't been fixed by Apple. Maybe old SDKs are not supported on purpose, which does make some business sense.

How to fix: Go to your Xcode project, select project info, go to Build tab and search Base SDK. Change your project Base SDK to 3.1. I had there 3.0, which seems to be a known defect.

• Build - Clean All Targets - select all - Clean
• Build - Build and Analyze
• Run - Run with Performance Tool - Leaks
• Stop
• Open popup item with application name - Launch Executable - Choose Executable
• Browse to your Build directory and select your application
• Record (the red Dot button)

It's not enough to start your application from Instruments, but you also have to choose the file. Stop and Record is not enough.

Graphics ok in Simulator, not found in Real Device

This is one of the ways that simulator and real device differ: check the names of your graphics files.

Filenames are case-sensitive in real device, not in emulator.