We are using Crashlytics in our app as the crash reporting tool. For Android native crashes, it\'s working fine and grouping the crashes correctly. Our app also has few comp
I resolved this by setting a custom stack trace to the exception. A new Exception(exceptionMessage)
will create the exception there itself, what we did was to throw an exception which in catch called my counterpart of handleException()
with the actual stack trace furnished in the exceptionMessage. Some parsing and the exceptionMessage can be used to set the stack trace on the newly created exception using exception.setStackTrace()
. Actually, this was required in my project only because it is cross-language, for regular projects, simply passing the exception thrown and caught at the place of interest should work.