I found a way to log custom caught exceptions in the Crashlytics Android SDK, but I can't find anything like that for the iOS SDK. Is there a way to log a caught exception with Crashlytics on iOS?
See Android explanation: http://support.crashlytics.com/knowledgebase/articles/202805-logging-caught-exceptions
It is not possible to log a caught exception in iOS using Crashlytics SDK. CLS_LOG can be used to log custom messages, but these log messages will go to Crashlytics only with the next crash data. If there is no crash, these log messages will never land in the Crashlytics dashboard. I got an official confirmation from the Crashlytics support team regarding the same. Logging caught exceptions in iOS is there in their roadmap.
I have gone through different sites for this functionality to be supported for IOS alternate to Crashlytics.
I found crittercism is the best so far..@Dima I think it is the alternative to Crashlytics..try it.
Here are some links that are useful to integrate crittercism in your project...!
http://docs.crittercism.com/ios/ios.html#logging-handled-exceptions
http://www.raywenderlich.com/34050/overview-of-ios-crash-reporting-tools-part-2
Refer those links and see it is useful to you or not...!
Finally Crashlytics added the desired feature 3.5.0!!
or
Reference
https://docs.fabric.io/ios/changelog.html#january-7-2016
HISTORY
This actually doesn't work as I expected: The message is saved into Crashlytics but only after the app is restarted and it will only save the last message.
So far non of the solutions mentioned here works. There is no way to track handled exceptions in iOS using Crashlytics.
You can use this to log any exception
In Crashlytics you'll see it in the crash report but with the
NON-FATALS
type.Event if it's not it's intended usage exceptions are logged in the same way Android handled exceptions are.
This is available in version 3.0.7.
Mike from Crashlytics and Fabric here.
You can now capture logged NSErrors in your iOS, tvOS, or OS X app. You want to use:
or
This will let you capture a fair number of logged NSErrors per user session. These are only sent on app relaunch. Logged errors errors are grouped by the error domain and code. This means error issues can span many different call sites.
See Documentation
Use below lines in catch block to handle custom caught exception
as explained for iOS http://support.crashlytics.com/knowledgebase/articles/222764-can-i-use-a-custom-exception-handler