Geek Answers Handbook

What is the most hated mistake you come across when developing for the iPhone?

Each language has its own famous and painful mistakes. I will be interested to know what errors have earned this reputation when developing for the iPhone.

List your data!

I agree with GenericTypeTea If you can list the error code / message and the reason for making a more useful entry.

+7
objective-c iphone
source share
9 answers

I especially hate this mistake.

Thanks for submitting [app name here] to the App Store. We reviewed the application and, in accordance with the criteria in our approval process, we did not choose to publish this application. As you know, Apple reserves the right, in its sole discretion, to decline for any reason.

+9
source share

Any error related to code signatures.

+8
source share

I hate all device sync errors like

"iTunes could not connect to the iPhone because an unknown error occurred (0xE8000025)"

Oh humanity.

+6
source share

I hate this EXC_BAD_ACCESS (sometimes called EXEC_BAD_ACCESS)

+5
source share

I would say that the most unpleasant mistake is actually a mistake that never happens . For example. when you have an IBOutlet that has not been properly "connected", instead of getting a NullPointerException or some such, the code just silently does nothing. Why sending a message to a null object does not raise an exception? Grr ....

+3
source share

By sending autorelease to an object that you do not have, the application crashes with EXC_BAD_ACCESS, and you do not know when the object was released.

+2
source share

My most hated mistake is when you download the sample code to check something, run it and make sure it is configured to run on the device when you have not changed the package ID and the code is not signed.

+1
source share

I despise the error about "gcc issued with status code 1" and no other information.

0
source share

I like and hate it that you can send messages to Nile objects. I like it because you don’t need to look anywhere anywhere. I hate this because sometimes you look for this error for hours, when everything you do sends a message to the nil object. In this case, the error would be pleasant

0
source share

More articles:


All Articles