从Crashlytics 3.0.0开始，实现用户提示是应用程序的责任 [英] As of Crashlytics 3.0.0, implementing a user prompt is the application's responsibility

问题描述

我收到以下警告：

[Crashlytics：Crash]警告：已启用用户提示功能。从
Crashlytics 3.0.0开始，实施用户提示是应用程序的
责任。请参阅Crashlytics.h的有关
的注释-crashlyticsDidDetectReportForLastExecution：completionHandler：

[Crashlytics:Crash] WARNING: the user prompt feature is enabled. As of Crashlytics 3.0.0, implementing a user prompt is the application's responsibility. See Crashlytics.h's notes about -crashlyticsDidDetectReportForLastExecution:completionHandler:

当我使用Xcode运行它时，它会出现在我的应用程序日志中。看来我正在使用的Crashlytics版本是3.0.8（来自Crashlytics.framework中的info.plist文件）。

appearing in my app's log when I run it with Xcode. It looks like the version of Crashlytics I'm using is 3.0.8 (from the info.plist file in the Crashlytics.framework).

以下是相关的文档Crashlytics.h文件：

Here's the relevant doc from the Crashlytics.h file:

/**
 *
 * Called when a Crashlytics instance has determined that the last execution of the
 * application ended in a crash.  This is called synchronously on Crashlytics
 * initialization. Your delegate must invoke the completionHandler, but does not need to do so 
 * synchronously, or even on the main thread. Invoking completionHandler with NO will cause the
 * detected report to be deleted and not submitted to Crashlytics. This is useful for
 * implementing permission prompts, or other more-complex forms of logic around submitting crashes.
 *
 * Failure to invoke the completionHandler will prevent submissions from being reported. Watch out.
 * 
 * Just implementing this delegate method will disable all forms of synchronous report submission. This can
 * impact the reliability of reporting crashes very early in application launch.
 *
 **/

- (void)crashlyticsDidDetectReportForLastExecution:(CLSReport *)report completionHandler:(void (^)(BOOL submit))completionHandler;

从警告中看来，我不会收到通常的发送崩溃报告？在我的应用程序中提示。但是，崩溃后我确实得到了。也就是说，我似乎不需要实现此UI。那么，有什么用呢？这个警告是否真的是个错误的警告，表示将来我们必须为此发送崩溃报告提示创建自己的UI？

From the warning, it would seem that I wouldn't get the usual "Send Crash Report?" prompt in my app. HOWEVER, I do get this after a crash. That is, it does not seem necessary for me to implement this UI. So, what gives? Is this warning really a mis-said warning that we'll have to do our own UI for this Send Crash Report prompt in the future?

我还查看了docs https://dev.twitter.com/crashlytics/ios
和 http://support.crashlytics.com/knowledgebase/topics/14721-crashlytics -sdk-for-ios
，但自3.0.0起找不到任何有关更改的内容。

I've also looked at docs https://dev.twitter.com/crashlytics/ios and http://support.crashlytics.com/knowledgebase/topics/14721-crashlytics-sdk-for-ios but can't find anything talking about a change since 3.0.0.

想法？

推荐答案

Fabric的Mike在这里。

Mike from Fabric here.

使用SDK 3.0，我们为如何处理崩溃报告添加了更细粒度的控制，以便您和其他开发人员可以显示警报或不显示警报。至。如果要实现自己的对话框，请在结构面板中关闭隐私对话框，然后使用提供的调用来执行此操作。

With SDK 3.0, we added more fine-grained control over how to handle crash report submission so that you, and other developers, can display the alert or not however you want to. If you want to implement your own dialog, turn off the privacy dialog in the Fabric dashboard and you use the call provided to do that.

如果要继续使用可以使用Fabric提供的隐私对话框，但是我建议您创建一个新对话框，因为它更加灵活并且可以根据应用程序的UI进行自定义。

If you want to continue to use the privacy dialog Fabric provides, you can, but I'd encourage you to create a new one as it's more flexible and can be customized to the UI of your application.

这篇关于从Crashlytics 3.0.0开始，实现用户提示是应用程序的责任的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！