问题描述
我最近在更新到Crashlytics 3.0后收到了这个应用程序
不确定它是否来自我的代码或其他内容。崩溃报告无法追踪
I recently received this app after updating to Crashlytics 3.0Not sure if it comes from my code or something else. The crash report is untraceable
Here is the crash report
Crashed: com.apple.main-thread EXC_BAD_ACCESS KERN_INVALID_ADDRESS at 0x000000009a0dbeb8
0 libobjc.A.dylib objc_msgSend + 16 release
1 CoreFoundation CFRelease + 524
2 CoreFoundation -[__NSArrayM dealloc] + 152
3 libobjc.A.dylib (anonymous namespace)::AutoreleasePoolPage::pop(void*) + 564
4 CoreFoundation _CFAutoreleasePoolPop + 28
5 Foundation -[NSAutoreleasePool release] + 148
6 UIKit -[UIApplication _run] + 588
7 UIKit UIApplicationMain + 1488
8 MyAppName main.m line 32main
9 libdyld.dylib start + 4
推荐答案
事实证明这是框架工作的错误
It turns out to be bug of the frame work
以下是我从Crashlytics的支持中得到的结果
Here is what I got from the support of Crashlytics
如果您更新到Crashlytics SDK的3.0.10，那么应该全部设置 - 有一个罕见的竞争条件3.0.9我们修补了最新版本。打开Fabric.app，更新框架，你会很高兴:)
This should be all set if you update to 3.0.10 of the Crashlytics SDK - there was a rare race condition in 3.0.9 that we patched up with the latest version. Open up Fabric.app, update the framework and you'll be good to go :)
Crashlytics的支持团队非常棒！
The support team of Crashlytics are awesome!
这篇关于有时来自Crashlytics的objc_msgSend [__NSArrayM dealloc]崩溃报告的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！