Adding a new mandatory attribute to an existing class, deleting a mandatory attribute from an existing class, or adding an optional attribute to the special class Top that is not a backlink attribute (directly or through inheritance, for example, by adding or deleting an auxiliary class) is not allowed.
This is probably not the correct interpretation of this error.
The Win32 error above is more likely to indicate the actual problem.
Flags
Severity
Success
This code indicates success, rather than an error.
This may not be the correct interpretation of this code,
or possibly the program is handling errors incorrectly.
I'm trying to debug a crash but when I run symbolicatecrash against my crash log I get every method call in the stack trace except for my method calls. Here is the crash report: Incident Identifier: C3A58923-5D49-4767-A3C2-3AFFEF00DFEF CrashReporter Key: 165f7337feeb98394ab7477fc0b7280d14a16e43 Hardware Model: iPad1,1 Process: Log Jam [2862] Path: /var/mobile/Applications/625E17A7-F0FF-4109-9E62-99FE8D6C6889/Log Jam.app/Log [...] read more
Given the following symbolicated crash log, is it more likely that the crash occurred due to the ASIHTTPRequest on Thread 5 or the NSURLConnection on Thread 3? I ask because this question has similar issues: ASIHTTPRequest, EXC_BAD_ACCESS when request did finished However, they had more around their ASIHTTPREquest crash and [...] read more
I have just mutilated my rootViewController over the past day. I'm now getting this error and I have no clue where to look to fix it. Any help on how to fix, or even better, help me to decipher the error output so I can do it myself. 2011-10-24 08:56:29.746 [...] read more
My app was rejected from the app store due to a crash that produced the crash log below. What is even more strange than the crash is that the steps given to reproduce it don't happen to me or any of 10+ beta testers (on differing iOS devices). Can anyone [...] read more
I'm having an issue with an iPhone app that crashes on launch for a select few users. MOST users are just fine - the app is live on the app store, Apple didn't find any problems, I never found these problems when testing. However, they exist. So. Here is what [...] read more