简体繁体 English

这是iOS错误还是开发人员可以修复？

[英]Is this iOS bug or can it be fixed by developer?

原文 2012-08-27 07:30:04 3 1 iphone/ ios/ debugging/ report/ bug-tracking

I am using crash reporting tool Crashlytics for a while now and am very pleased with it. 我使用崩溃报告工具Crashlytics已有一段时间了，对此感到非常满意。 However I can not figure it out what some of the reported bugs means. 但是，我无法弄清楚所报告的某些bug的含义。

For example I get CoreFoundation error _CFAutoreleasePoolPop : 例如我得到CoreFoundation错误_CFAutoreleasePoolPop ： Crashlytics错误报告1

Or another one in UIKit -> __73-[UIPopoverController _completionBlockForDismissalWhenNotifyingDelegate:] : 或UIKit另一个-> __73-[UIPopoverController _completionBlockForDismissalWhenNotifyingDelegate:] ： Crashlytics错误报告2

Are this kind of bugs iOS bugs or bugs that my code produced? 是iOS的错误还是我的代码产生的错误？ What can I do here? 我在这里可以做什么？

1 个解决方案

UIAlertView seems to be implemented with UIPopovers and are therefore UIAlertViews which can cause this issue. UIAlertView似乎是用UIPopovers实现的，因此是UIAlertViews可能导致此问题。 I suspect that the UIPopoverController or UIAlertView delegate has been deallocated before the completion handler is called causing the crash. 我怀疑在UIPopoverController完成处理程序导致崩溃之前，已经重新分配了UIPopoverController或UIAlertView委托。

If you keep a __weak reference to the UIAlertViews and UIPopoverControllers in their delegates you can set the alert/popover's delegate property to nil in delegate's dealloc call without unnecessarily retaining popover/alert . 如果在其委托中保留对UIAlertViews和UIPopoverControllers的__weak引用，则可以在委托的dealloc调用中将alert / popover的委托属性设置为nil，而不必保留popover/alert 。