|Message||The storage device has lost data or persistence.|
This appears to be a raw Win32 error. More information may be available in error 0x80070170.
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.
|Description||The default facility code.|
|Error Code||368 (0x0170)|
This crash looks like a problem with a constraints you set in your app (in a background thread ?).
In addition this looks similar (not identical) to your other reported crash: https://stackoverflow.com/questions/19114389/app-hang-and-then-crash-ios-7
So in short: your constraints setup (presumably in code) causes this problem. Most likely because your constraints reference a view that is not existing any more.
From thread 2 some code is dispatched into the main thread:
28 libdispatch.dylib 0x37cc59a4 _dispatch_main_queue_callback_4CF + 264
A transition to another View Controller via a navigation controller did finish:
21 UIKit 0x2fd81416 -[_UIViewControllerTransitionContext completeTransition:] + 70
A scrollview is being removed from its superview:
18 UIKit 0x2fd3cccc -[UIScrollView removeFromSuperview] + 60
Constraints are being evaluated:
12 Foundation 0x2de4a918 -[NSISEngine minimizeConstantInObjectiveRowWithHead:] + 180
The constraints engine wants to log some error into the console:
11 Foundation 0x2de0b78e NSLog + 22
The constraints engine tries to generate a string:
5 Foundation 0x2df73336 -[NSISObjectiveLinearExpression description] + 122
An exception occurs because it tries to add a
nil object to an
This could happen if your constraint rules (done in code) reference another view that does not exist any more. You should check your constraint rules and set breakpoints to find out which one is causing the crash.
Unfortunately this log doesn't look like it'll be too useful - it just shows the main thread handling an exception that's being re-thrown from another thread; that thread has gone off to do something else at the time of the log.
You mention your suspicion about the
RestKit loop and the possibility
NSOperation is throwing the exception. That's possible and worth putting a check in (and crossing your fingers that it doesn't break something else...), but it's probably time to beg the app review team to give you better steps to reproduce. See if you can pin down what you all are doing differently. I wish I had a better answer for you, but I think exploring all you can about what you're doing in the background while in this part of the app and trying to figure out the missing steps to reproduce is going to be your best bet. Good luck!
The crash happened in Thread 0 at the top most Snug line 4
Thread 0 name: Dispatch queue: com.apple.main-thread Thread 0: 0 libsystem_kernel.dylib 0x319e7660 __semwait_signal_nocancel + 24 1 libsystem_c.dylib 0x3410b4da nanosleep$NOCANCEL + 118 2 libsystem_c.dylib 0x340dd3a0 usleep$NOCANCEL + 44 3 libsystem_c.dylib 0x340dd2b6 abort + 118 4 Snug 0x001f8760 uncaught_exception_handler + 12 5 CoreFoundation 0x37830950 __handleUncaughtException + 68 6 libobjc.A.dylib 0x3553533e _objc_terminate + 122 7 libc++abi.dylib 0x36f683be safe_handler_caller(void (*)()) + 70 8 libc++abi.dylib 0x36f6844a std::terminate() + 14 9 libc++abi.dylib 0x36f6981e __cxa_rethrow + 82 10 libobjc.A.dylib 0x355352a2 objc_exception_rethrow + 6 11 CoreFoundation 0x37786506 CFRunLoopRunSpecific + 398 12 CoreFoundation 0x37786366 CFRunLoopRunInMode + 98 13 GraphicsServices 0x33f45432 GSEventRunModal + 130 14 UIKit 0x31532cce UIApplicationMain + 1074 15 Snug 0x000f590c main (main.m:16) 16 Snug 0x000f58c0 start + 32
There the app caused an exception which was not caught. To symbolicate the report just drag it into xCode - you need to have the dSYM file for the reviewed version. Then xCode will show you the exact line where the problem occured. To get the dSym you need to "build and archive".
Also since the crash code is
Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x00000000, 0x00000000
the reason for the crash is a memory access problem. These kind of crash reports are generated in many cases where one tries to instert a nil object into an array or dictionary. (since the crash is in the main thread and not in Thread 6 as reported)
In your case I do not see any obvious insert, however I would check the logic starting in line 16 of your main file and all the subsequent. I would assume you are accessing an object which is not existent anymore at the time of this invokation.
Is the sender application a JMS (or XMS) application or they hand crafting JMS headers? What version of XMS .NET are you using? Using RFHUtil,
I sent a message containing the JMS folder data your provided above and I see that XMS .NET V8.0 works fine. I also had to set the message type as jms_bytes. So I am wondering if the sender application is setting the message type correctly. Without the message type, application will get type casting error while receiving message.
You can analyze the crash report using the below
Steps to analyze crash report from apple:
Copy the release .app file which was pushed to the appstore, the .dSYM file that was created at the time of release and the crash report receive from APPLE into a FOLDER.
OPEN terminal application and go to the folder created above (using CD command)
atos -arch armv7 -o YOURAPP.app/YOURAPP MEMORY_LOCATION_OF_CRASH. The memory location should be the one at which the app crashed as per the report.
Ex: atos -arch armv7 -o 'app name.app'/'app name' 0x0003b508
This would show you the exact line, method name which resulted in crash.
Ex: [classname functionName:]; -510
if we use IPA for symbolicating - just rename the extention .ipa with .zip , extract it then we can get a Payload Folder which contain app. In this case we don't need .dSYM file.
Link for this Symbolicating iPhone App Crash Reports
User contributions licensed under CC BY-SA 3.0