KSCrash
KSCrash copied to clipboard
Crash reason and backtrace stacks were not clear
I imported KSCrash through CocoaPods in my project and triggered an unrecognized selector error, the crash report KSCrash collected was like pic1,and then I used Bugly(another crash collect service developed by Tencent),it collected the right stack and showed the right reason(as pic2).So my question is,does the crash report KSCrash collect need to be processed again to get the true reason and stack?