Has anyone managed to get flurry to correctly do crash reporting?
I have the following init
[lua]
flurry.init(flurryListener, {
apiKey = apiKey,
crashReportingEnabled = true,
logLevel = “all”
})
[/lua]
Using this just by itself does increase the issue count in flurry if I cause an error, but there are no details (stack or message).
If I add an “unhandledError” event listener I can send the handled error through to flurry and this will show up as a logged event, but it does not tie in with the crash analytics. And since it is now handled the issue could does not increase.
Basically, I can get the information into flurry but I can’t take advantage of the full range of crash analytics.
I have done some research and can see that the crash logs should show 3 different types of issues “Crashes, Caught Exceptions and Logged Errors”. Not uncaught. In other languages there is a method “logError” that you can use in the unHandledError function.
I was hoping that I could use the logEvent method in the same way, but have had no luck. Any help would be appreciated.
Below is some of my attempts.
[lua]
local function myUnhandledErrorListener( event )
table.print_r(event)
local iHandledTheError = true
if iHandledTheError then
print( “Handling the unhandled error”, event.errorMessage )
flurryListener(event)
flurry.logEvent( “logError”,
{
message=event.errorMessage,
exception=event.stackTrace
})
flurry.logEvent( “Application_UnhandledException”,
{
name=“uncaught”,
reason=event.stackTrace
})
flurry.logEvent( “debug”,
{
name=“uncaught”,
reason=event.stackTrace
})
flurry.logEvent( “Uncaught”,
{
name=“uncaught”,
reason=event.stackTrace
})
flurry.logEvent( “Application_UnhandledException”, event)
flurry.logEvent( “debug”, event)
flurry.logEvent( “uncaught”, event)
else
print( “Not handling the unhandled error”, event.errorMessage )
end
return iHandledTheError
end
Runtime:addEventListener(“unhandledError”, myUnhandledErrorListener)
[/lua]