Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash reason and backtrace stacks were not clear #425

Open
qtechdrew opened this issue Mar 3, 2022 · 0 comments
Open

Crash reason and backtrace stacks were not clear #425

qtechdrew opened this issue Mar 3, 2022 · 0 comments

Comments

@qtechdrew
Copy link

qtechdrew commented Mar 3, 2022

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?
截屏2022-03-03 下午5 44 57
截屏2022-03-03 下午5 45 51

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant