在进行内部测试时未在crashlytics上收到崩溃 [英] Not receiving crashes on crashlytics while do internal testing

问题描述

我已经将crashlytics与pod集成在一起。我曾经用Testflight测试应用程序。我注意到在iTunes连接上几乎没有崩溃，但是没有收到来自fabric / crashlytics的电子邮件。

I have integrated crashlytics with the pod. I used to test application with Testflight. I have noticed that there were few crashed on iTunes connect but Did not received any email from fabric/crashlytics.

我像exit（1）一样手动尝试应用崩溃，并且收到了即将启动该应用程序的电子邮件。因此，假设crashlytics框架已成功集成。

I Try app crash manually like exit(1) and I received an email on very next launch of the application. So assuming that crashlytics framework integrated successfully.

您对我想去的地方有任何建议吗？

Do you have any suggestion where I suppose to look?

推荐答案

Fabric的Mike在这里。

Mike from Fabric here.

每次崩溃时，我们的电子邮件通知都不会不发送，因为对于许多开发人员来说，这是令人头疼的。将崩溃分类为多个问题，以便更轻松地跟踪应在您的应用程序中修复的问题，以及何时触发问题电子邮件。

Our email notifications will not be sent on each crash as for many developers that would be overwhelming. Crashes are grouped into issues to make it easier to track which issues should be fixed within your app and here's when the emails would be triggered for an issue.

已发送电子邮件在以下选项下，与崩溃有关（分为问题）。

An email is sent under the following options, in relation to crashes (which are grouped into issues).

• 新问题（发生全新问题时-您的应用从未发生过崩溃）


• 新非致命问题（何时发生了一个全新的已记录NSError-您的应用从未见过的NS错误）


• 已解决的问题（当在已知问题的版本之外检测到崩溃时，该问题是例如，您认为自己已经在应用程序的1.2版中解决了崩溃/问题并发布了1.3版。如果再次发生崩溃，将打开问题并触发回归电子邮件。）


• 崩溃稳定性摘要-这是一封摘要电子邮件，当检测到问题随着时间而趋向于趋势或流量特别大时发送。

• New Issue (When a brand new issue occurs - a crash that has never been seen before for your app)
• New Non Fatal Issue (When a brand new logged NSError occurs - an NS Error that has never been seen before for your app)
• Regressed Issue (When a crash is detected outside the known versions of the issue and the issue is closed. For example, you feel you've resolved the crash/issue in version 1.2 of your app and ship 1.3. If the crash re-occurs, the issue would be opened and a regression email would be triggered).
• Crash Stability Digest - This is a summary email sent when issues are detected to be trending over time or particularly high volume.

这篇关于在进行内部测试时未在crashlytics上收到崩溃的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！