Crashlytics不会显示崩溃 [英] Crashlytics does not show crashes

问题描述

我刚刚使用

AppDelegate：

  Fabric.sharedSDK（）。debug = true 
 Fabric.with（[Crashlytics.self]）
  

为了模拟崩溃，我使用

  Crashlytics.sharedInstance 
  

和

  var ggg：Int！ 
 print（ggg）
  

Crashlitics收集一些关于会话的信息。例如，它更新软件包版本信息：

所以连接Crashlitics工程。但崩溃信息为空：

如果是，请执行以下步骤

1. 右键点击您的归档 - >在Finder中显示 - >右键单击文件，然后点击显示软件包内容


2. 右键单击dSYM文件 - 显示包内容 - >内容 - >资源 - > DWARF（在终端中打开）


3. 运行命令dwarfdump --uuiddwarf $ b

这将显示所有关联的UUID ，并且如果任何列出的UUID与缺少dSYM id中提及的UUID匹配，则仅压缩dSYM文件夹并将其上传到crashlytics上。缺少dSYM段。

此步骤是重要的原因有时我们从组织者提取的dSYM文件不包含正确的UUID。在上传错误的文件之后，我们等待它的更新。

除了上述内容，Bitcode属性和构建设置中的调试信息格式也会影响崩溃报告。 / p>

I have just installed Crashlitycs using this official instruction.

I have set Debug Information Format is "DWARF with dSYM File" for both Debug and Release and disabled Bitcode (some people wrote that it could help):

AppDelegate:

Fabric.sharedSDK().debug = true
Fabric.with([Crashlytics.self])

To simulate a crash I use

Crashlytics.sharedInstance().crash()

and

var ggg: Int!
print(ggg)

Crashlitics collects some information about sessions. For example it updates bundle versions info:

So connection with Crashlitics works. However crash information is empty:

I am using XCode 8 and iOS 9/10. What I am doing wrong?

EDIT:

I have tested it on simulator and device without XCode debugger connection (i.e. launching from sumulator/device screen)

Finally I have received some Crashlytics reports after 7-8 hours after crashes. I expected them earlier because according to documentation:

Within a few minutes, you should see the crash appear on your Fabric Dashboard.

However I did not receive all crashes I was waiting for. During my experiments I have tried different ways to initialise Crashlytics:

Fabric.with([Crashlytics.self])
and
Fabric.with([Crashlytics.self()])

Could it be the reason? I have also found the similar unanswered question.

解决方案

Checked the following terms,

1. Make sure Crashlytics SDK line is after all other 3rd-party SDK lines. (it needs to be last one called in your appDidFinishLaunching method.)

2. Force a crash and then relaunch the app. Xcode must be disconnected to stop it from intercepting the crash report. To disconnect Xcode, follow the instructions here.

3. If you're using [Crashlytics sharedInstance] crash]; to test crashing, make sure it's not in the appDidFinishLaunching method.

These are already mentioned in support section, Here is additional ones -

1. Check in organization -> Your App -> Missing dSYM, Is it showing any missing dSYM file

if yes, Then do the following step

1. Right Click on your archive -> Show in Finder -> Right click on file and click on Show package contents
2. Right click on dSYM file - > Show package contents -> Contents -> Resources -> DWARF (Open in terminal)
3. Run command dwarfdump --uuid "file name you saw there in dwarf folder"

This will show all the associated UUID, And if any listed UUID matched with the one mentioned in missing dSYM id then just compress the dSYM folder and upload it on crashlytics Missing dSYM segment.

This step is important cause sometimes the dSYM file we extract from organizer doesn't contain correct UUID. And after uploading the wrong one we wait for its updations. So it's better to make sure you are uploading the right dSYM file.

Other than aforementioned things, Bitcode property and Debug Information Format in Build Settings also affect the crash reporting.

这篇关于Crashlytics不会显示崩溃的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！