-
Notifications
You must be signed in to change notification settings - Fork 0
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
6.9.0 crashes when app is terminated by the user #8
Comments
Hi @salling, Thanks for the detailed report. We are investigating the issue. We will let you know about the process. |
It seems the problem occurs in the shutdown process. We are still investigating the issue, and it will take a little bit more time. While we try to fix it, we will keep this issue open let you know if anything happens. Luckily it doesn't affect user experience and, hopefully, we will provide an update soon. Meanwhile, if you have any other data that you share with us we appreciate it. Any other crash logs (a full log would be better), code blocks, etc. Thanks again for letting us know about the problem. |
We could not recreate the crash. Could you share your implementation code, so we can try to recreate the environment that leads to the crash? |
We are also seeing this same crash come up in tvOS a fair amount, in our New Relic crash analyses. |
Version 6.10.0 should resolve this issue. Thanks for the feedback and sorry for any inconvenience. Please feel free to reach us if you encounter any problems again. |
We found this issue in our internal testing before releasing. We have confirmed that 6.8.1 does not have this issue, and have reverted to using that version instead.
I have attached crash logs. Some symbols and threads redacted.
Please do something about the quality situation in this library. We had high hopes that 6.9.0 would fix long standing crasher issues, but it just seems to have made things worse. Here's what our current top crasher situation looks like:
As you can see, a single library (comscore) is responsible for an order of magnitude more crashers than the rest of the app. That's unacceptable, IMHO.
The text was updated successfully, but these errors were encountered: