Ever language has their famous and painfull errors. I will be fun to learn which errors earn this reputation when developing for the iPhone.
曾经的语言有着名和痛苦的错误。在开发iPhone时,我会很有趣地了解哪些错误可以获得这种声誉。
Please list yours!
请列出你的!
I agree with GenericTypeTea If you can please list the error code/message and the cause to make for a more useful post.
我同意GenericTypeTea如果您可以请列出错误代码/消息以及原因,以便获得更有用的帖子。
9 个解决方案
#1
9
I particularly hate this error.
我特别讨厌这个错误。
Thank you for submitting [application name here] to the App Store. We've reviewed the application and, consistent with the criteria in our approval process, we have chosen not to publish this application. As you know Apple reserves the right, in its sole discretion, to reject an application for any reason.
感谢您将[此处的应用程序名称]提交到App Store。我们已审核了该申请,并且根据审批流程中的标准,我们选择不发布此申请。如您所知,Apple保留自行决定以任何理由拒绝申请的权利。
#2
8
Any error that has to do with code signing.
与代码签名有关的任何错误。
#3
6
I hate all the device sync errors like
我讨厌所有的设备同步错误
"iTunes could not connect to iPhone because an unknown error occurred (0xE8000025)"
“iTunes无法连接到iPhone,因为发生了未知错误(0xE8000025)”
Oh the humanity.
噢,人性。
#4
5
I hate this one EXC_BAD_ACCESS (sometimes called EXEC_BAD_ACCESS)
我讨厌这个EXC_BAD_ACCESS(有时称为EXEC_BAD_ACCESS)
#5
3
I would say that the most frustrating error is actually the error that never happens. E.g. when you have an IBOutlet that has not been properly "plugged in", rather then getting a NullPointerException or some such, the code just silently does nothing. Why does sending a message to a "null" object not throw an exception? Grr....
我会说最令人沮丧的错误实际上是从未发生过的错误。例如。当你有一个没有正确“插入”的IBOutlet,而不是获得NullPointerException或其他一些时,代码只是默默地做什么。为什么向“null”对象发送消息不会抛出异常?格儿....
#6
2
Sending autorelease to an object you do not own, the app crashes with a EXC_BAD_ACCESS and you have no clue when did the object get released.
将自动释放发送到您不拥有的对象,应用程序崩溃了EXC_BAD_ACCESS,您不知道该对象何时被释放。
#7
1
My most-hated error is when you download sample code to check something out, go to run it, and realize it's set to run on the device when you haven't changed the bundle identifier and the code isn't signed.
我最讨厌的错误是当您下载示例代码以检查某些内容时,去运行它,并意识到当您未更改捆绑包标识符并且代码未签名时,它将设置为在设备上运行。
#8
0
I despise the error about "gcc exited with status code 1" and no other information.
我鄙视“gcc退出状态代码1”的错误,没有其他信息。
#9
0
I love it and hate it that you can send messages to nil objects. I love it because you don't have to check for nil everywhere. I hate it because sometimes you're looking for that error for hours when all you do is send a message to a nil object. In that case an error would have been nice
我喜欢它,并且讨厌你可以向零个对象发送消息。我喜欢它因为你无需到处检查零。我讨厌它,因为有时候当你所做的就是向nil对象发送消息时,你会在几个小时内找到那个错误。在那种情况下,错误会很好
#1
9
I particularly hate this error.
我特别讨厌这个错误。
Thank you for submitting [application name here] to the App Store. We've reviewed the application and, consistent with the criteria in our approval process, we have chosen not to publish this application. As you know Apple reserves the right, in its sole discretion, to reject an application for any reason.
感谢您将[此处的应用程序名称]提交到App Store。我们已审核了该申请,并且根据审批流程中的标准,我们选择不发布此申请。如您所知,Apple保留自行决定以任何理由拒绝申请的权利。
#2
8
Any error that has to do with code signing.
与代码签名有关的任何错误。
#3
6
I hate all the device sync errors like
我讨厌所有的设备同步错误
"iTunes could not connect to iPhone because an unknown error occurred (0xE8000025)"
“iTunes无法连接到iPhone,因为发生了未知错误(0xE8000025)”
Oh the humanity.
噢,人性。
#4
5
I hate this one EXC_BAD_ACCESS (sometimes called EXEC_BAD_ACCESS)
我讨厌这个EXC_BAD_ACCESS(有时称为EXEC_BAD_ACCESS)
#5
3
I would say that the most frustrating error is actually the error that never happens. E.g. when you have an IBOutlet that has not been properly "plugged in", rather then getting a NullPointerException or some such, the code just silently does nothing. Why does sending a message to a "null" object not throw an exception? Grr....
我会说最令人沮丧的错误实际上是从未发生过的错误。例如。当你有一个没有正确“插入”的IBOutlet,而不是获得NullPointerException或其他一些时,代码只是默默地做什么。为什么向“null”对象发送消息不会抛出异常?格儿....
#6
2
Sending autorelease to an object you do not own, the app crashes with a EXC_BAD_ACCESS and you have no clue when did the object get released.
将自动释放发送到您不拥有的对象,应用程序崩溃了EXC_BAD_ACCESS,您不知道该对象何时被释放。
#7
1
My most-hated error is when you download sample code to check something out, go to run it, and realize it's set to run on the device when you haven't changed the bundle identifier and the code isn't signed.
我最讨厌的错误是当您下载示例代码以检查某些内容时,去运行它,并意识到当您未更改捆绑包标识符并且代码未签名时,它将设置为在设备上运行。
#8
0
I despise the error about "gcc exited with status code 1" and no other information.
我鄙视“gcc退出状态代码1”的错误,没有其他信息。
#9
0
I love it and hate it that you can send messages to nil objects. I love it because you don't have to check for nil everywhere. I hate it because sometimes you're looking for that error for hours when all you do is send a message to a nil object. In that case an error would have been nice
我喜欢它,并且讨厌你可以向零个对象发送消息。我喜欢它因为你无需到处检查零。我讨厌它,因为有时候当你所做的就是向nil对象发送消息时,你会在几个小时内找到那个错误。在那种情况下,错误会很好