I have an app which is written in swift and uses AFNetwork and some other helpers written in Obj c. On my clients device (iPhone 6+) he is getting an SIGTRAP error, I have tried to recreate the issue on the testing devices that we have and on all the simulators but could not recreate it.
Below is the stack trace, it crashed twice: http://paste.ubuntu.com/12077304/ When I symbolicate the crash report it is pointing to:
-[Instagram getOwnBaseUrl] (in DiaryApp) (Instagram.m:118)
And on the second instance it point to:
[UIAlertView(AFNetworking) showAlertViewForTaskWithErrorOnCompletion:delegate:cancelButtonTitle:otherButtonTitles:]_block_invoke (in DiaryApp) (UIAlertView+AFNetworking.m:72)
Crash Log : http://paste.ubuntu.com/12077328/
I am not able to pin point the exact cause for the crash. Any help in this regard will be highly appreciated.
Thanks.
EXC_BREAKPOINT (SIGTRAP) and EXC_BAD_INSTRUCTION (SIGILL)A trace trap gives an attached debugger the chance to interrupt the process at a specific point in its execution. On ARM processors, this appears as EXC_BREAKPOINT (SIGTRAP).
EXC_BREAKPOINT (SIGTRAP) is a trace trap interrupted the process. It gives an attached debugger, if any, a chance to interrupt the process at a specific point in its execution.
You can also see the crash log on an iPhone/iPad by going to Settings -> Privacy -> Analytics -> Analytics Data. You can also see the crash log on a simulator if the app crashes during building through a simulator.
SIGTRAP is not the error it is the exception. It doesn't show the origin of the crash. This exceptions throw into Main thread on Main/Next Runloop, so the stacktrace of the main thread does not show the origin of it.
It happen like NSArray indexOutOfBounds
or library or anything else
reference link
signal Types
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With