While working on my iPhone app Quickie, I encountered one of many examples why you must always check your code on the actual device.
Quickie uses Core Data for storage and in one particular place I was comparing the NSString variable to a NSString–typed property of my CoreData class, QuickieList. Like this:
listName is defined as NSString and theListName is obviously that as well. In this particular instance, both of those had the value of “test”.
In the iPhone Simulator (running on 10.6.2) this comparison returned false, but on the iPhone running 3.1.2 it returned true. When changed into:
result was the same.
Never – I repeat — never assume that simulator testing will be fine, even for seemingly small things. It can bite you when you least expect it.
Thanks for the tips so far.
I’m in the starting stages of my app company. I have more of a design/photography background and am working with a programmer.
The first thing I did was link my phone and run tests. The first thing I noticed was a crash when scrolling through a thumbnail list. I tested on the simulator and there were no hiccups.
Once linked, testing on the phone is just as quick as loading it onto the simulator, so there’s no excuse not to.
Steve White
dadico apps