Stack trace not showing application frames. about airbrake-ios HOT 6 CLOSED

+1 this is making airbrake for iOS pretty much useless

from airbrake-ios.

On further investigation this is a bug in airbrake-ios. (new information indicates this is server bug ... see comments below)

An exception handler in CFRunloop catches and rethrows a new exception.(https://stackoverflow.com/questions/13777446/ios-how-to-get-stack-trace-of-an-unhandled-stdexception)

Airbrake is logging the new Exception instead of the real underlying one, which means that almost every issue doesn't get a correct stack as it crashes in the context of a runloop.

PLCrashReporter already has the ability to get the stack of the original underlying exception. Airbrake-ios should get it from PLCrashReportExceptionInfo *_exceptionInfo;

from airbrake-ios.

Thx for the finding, will take a look at this issue.

from airbrake-ios.

Jocelyn,
Some further information. This may actually be a bug on the airbrake server api.
POST https://airbrake.io/api/v3/projects/PROJECT_ID/ios-reports?key=PROJECT_KEY

body json:
{
report: '...',
context : '...'
}

The report string json sent by airbrake-ios contains the correct backtrace from PLCrashReportExceptionInfo*, this is in a part of the report text starting with
"Last Exception Backtrace:"

However the airbrake web console does not display this. It only displays the stack of crashed thread, which is useless for crashes in a RunLoop.

I did not find a way to get the full report from web console or locate url returned by the above web API. (https://airbrake.io/locate/xxxxxxxxxxxxxxxx)

Also the full report string contains stacks for all threads, useful to debug multithreading issues, which also is not available from airbrake web dashboard.

from airbrake-ios.

samplereport.txt

Here's a report that was sent to airbrake server. The stack trace of interest starts with:
Last Exception Backtrace:

The airbrake dashboard / website only shows the stack trace starting with:
Thread 0 Crashed:

There seems to be no way of getting the Last Exception Backtrace.

from airbrake-ios.

Have forked the code, and developed a workaround.
https://github.com/SimpleBillsDev/airbrake-ios
The last exception backtrace is converted to a pseudo crashed thread, and a second crash report is sent to airbrake server.
The Podfile can be changed to use the fork rather than the default.
pod 'Airbrake-iOS', :git => 'https://github.com/SimpleBillsDev/airbrake-ios.git'

from airbrake-ios.