Crashes report in iOS life cycle metrics

Avatar

Avatar

JillsMatthew

Avatar

JillsMatthew

JillsMatthew

15-10-2015

Hi,

I have a question regarding Crashes report in iOS life cycle metrics. 
Can someone please explain how 'Crashes' report is tracked in SiteCatalyst?

"Triggered when the application does not exit gracefully. Event is sent on application start after crash (the application is considered to crash if quit is not called)."

We found the above in documentation, but we need more details. 

What is a quit and when is it called/triggers usually?

The reason why I'm asking is because we are seeing a massive increase in our crashes report since we launched our latest app version. But the new version traffic seems to be doing better than our previous versions.
The numbers we are seeing from SiteCatalyst aren’t the same we are seeing from Crittercism (10k vs 150k daily) – we’d like to understand what triggers the instance.
We don't have any idea why SiteCatalyst suddenly reports such an increase in Crashes report. 

Thanks

View Entire Topic

Avatar

Avatar

steve_benedick

Employee

Avatar

steve_benedick

Employee

steve_benedick
Employee

15-10-2015

Hey Mike,

 

Sending hits when the app enters the background (or while the app is in the background) can cause issues in your lifecycle data.  If you are sending hits via the SDK from the background, make sure you're using the trackActionFromBackground:data: message.  Using this will suppress new lifecycle sessions from being created by your app's activity while it's in the background.

If this doesn't help, I recommend contacting Client Care so we can get a ticket open for you.  

 

steve benedick
mobile software engineer
Adobe Marketing Cloud