blocks|key|1907397|text|Xcode调试器不允许Crashlytics处理崩溃报告。是的，即使在我第一次读到这篇文章时，这似乎也很奇怪，但这是一个事实(Source)。这就是为什么我们永远看不到崩溃报告的原因：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1907398|在模拟器中运行应用程序在iDevice上直接构建应用程序，并在打开调试器的情况下从Xcode运行。|1907399|要确保在测试期间报告崩溃(copied+from+Crashlytics+support+site)：|1907400|启动你的应用程序，并强制从web仪表板中的崩溃报告crashRelaunch+simulatorSee应用程序。|1907401|编辑：|1907402|增加了一个参考；Crashlytics还提供了一篇关于a+quick+way+to+force+a+crash的短文。|1907403|entityMap|0|LINK|mutability|MUTABLE|url|http://support.crashlytics.com/knowledgebase/articles/92523-why-can-t-i-have-xcode-connected-|1|2|http://support.crashlytics.com/knowledgebase/articles/92522-is-there-a-quick-way-to-force-a-crash^0|1R|6|0|0|0|D|10|1|0|0|0|R|S|2|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@$A|Z|B|10|1|11]]|C|$]]|$1|D|3|E|5|6|7|12|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|13|8|@]|9|@$A|14|B|15|1|16]]|C|$]]|$1|H|3|I|5|6|7|17|8|@]|9|@]|C|$]]|$1|J|3|K|5|6|7|18|8|@]|9|@]|C|$]]|$1|L|3|M|5|6|7|19|8|@]|9|@$A|1A|B|1B|1|1C]]|C|$]]|$1|N|3|-4|5|6|7|1D|8|@]|9|@]|C|$]]]|O|$P|$5|Q|R|S|C|$T|U]]|V|$5|Q|R|S|C|$T|U]]|W|$5|Q|R|S|C|$T|X]]]]

Xcode debugger does NOT allow Crashlytics to process crash reports. Yeah, that seem weird even to me when I read that first time but it is a fact (<a href="http://support.crashlytics.com/knowledgebase/articles/92523-why-can-t-i-have-xcode-connected-" rel="noreferrer">Source</a>). That's is the reason we never see crash report When: 
 - running app in Simulator 
 - running app on iDevice by directly build and run from Xcode with debugger on. 

To make sure a crash is reported during your testing (<a href="http://support.crashlytics.com/knowledgebase/articles/92523-why-can-t-i-have-xcode-connected-" rel="noreferrer">copied from Crashlytics support site</a>): 
 1. Launch simulator 
 2. Press stop 
 3. Launch your app and force a crash 
 4. Relaunch the app from simulator 
 5. See the crash report in the web dashboard.

EDIT:

Added a reference; Crashlytics also provides a short article on <a href="http://support.crashlytics.com/knowledgebase/articles/92522-is-there-a-quick-way-to-force-a-crash" rel="noreferrer">a quick way to force a crash</a>.

blocks|key|1907639|text|天啊，虽然很晚了，但还是百分之百地工作|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1907640|在项目构建设置中进行一些更改，如下图所示|1907641|​|1907642|📷|atomic|offset|length|1907643|1907644|and+follow+these+instructions.|1907645|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/ba3e6405b55c6f4aeca24b3b8d0643c6.png|imageAlt|1|LINK|MUTABLE|url|http://support.crashlytics.com/knowledgebase/articles/92523-why-can-t-i-have-xcode-connected-^0|0|0|0|0|1|0|0|0|0|U|1|0^^$0|@$1|2|3|4|5|6|7|11|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|12|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|13|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|14|8|@]|9|@$I|15|J|16|1|17]]|A|$]]|$1|K|3|E|5|6|7|18|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|19|8|@]|9|@$I|1A|J|1B|1|1C]]|A|$]]|$1|N|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U|V|-4]]|W|$5|X|R|Y|A|$Z|10]]]]

My be it's late but work 100%

Make some changes in project build settings like in below image

<a href="https://i.stack.imgur.com/D2Etp.png" rel="noreferrer"><img src="https://i.stack.imgur.com/D2Etp.png" alt="enter image description here"></a>

<a href="http://support.crashlytics.com/knowledgebase/articles/92523-why-can-t-i-have-xcode-connected-" rel="noreferrer">and follow these instructions.</a>

blocks|key|1694323|text|我使用以下步骤找到了解决方案|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1694324|+1.+Go+to+Edit+Scheme+++++2.+Run+->+Info+++++3.+Change+Build+Configuration+to+release.+++++Now+run+the+app+crash+it.+You+will+receive+mail.|code-block|syntax|javascript|1694325|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I found solution using following steps 
 1. Go to Edit Scheme
 2. Run -> Info
 3. Change Build Configuration to release.
 Now run the app crash it. You will receive mail.

blocks|key|1693863|text|到目前为止，Crashlytics对我来说是有效的。我不知道为什么，但现在它不起作用了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1693864|您应该通过以下方式打开调试模式|1693865|[Crashlytics+sharedInstance].debugMode+=+YES;|code-block|syntax|javascript|1693866|我的问题在这里Crashlytics+error+code:+202+when+Submitting+files+:(|offset|length|1693867|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/18182532/crashlytics-error-code-202-when-submitting-files^0|0|0|0|7|1D|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|W|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|X|8|@]|9|@$K|Y|L|Z|1|10]]|A|$]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]]]

Crashlytics works for me until now.
I don't know why but now it doesn't work.

You should turn debug-mode on by

<pre><code>[Crashlytics sharedInstance].debugMode = YES;
</code></pre>

My problem is here <a href="https://stackoverflow.com/questions/18182532/crashlytics-error-code-202-when-submitting-files">Crashlytics error code: 202 when Submitting files</a> :(

blocks|key|1693887|text|确保您没有过早地强制崩溃。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1693888|将[Crashlytics+sharedInstance].debugMode设置为YES；|offset|length|style|CODE|1693889|注意|1693890|Crashlytics]+Settings+loaded|code-block|syntax|javascript|1693891|在Xcode控制台日志上。|1693892|然后强制崩溃并重新启动应用程序，现在就会报告崩溃。|1693893|entityMap^0|0|1|12|16|3|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@$D|W|E|X|F|G]|$D|Y|E|Z|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|10|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|11|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|12|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|13|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|T|$]]

Make sure you are not forcing the crash too early.

Set <code>[Crashlytics sharedInstance].debugMode</code> to <code>YES</code>;

Watch for

<pre><code>Crashlytics] Settings loaded
</code></pre>

on the Xcode console logs.

Then force the crash and restart the app, and the crash will be reported now.

blocks|key|1694285|text|这是针对xcode+9的，来自crashlytics+3.4.0|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1694286|📷|atomic|offset|length|1694287|1694288|​|1694289|完成此操作后，请耐心等待几分钟。|1694290|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/6d402dd9bd20f7ee0dfa334b8fa1cc57.png|imageAlt|1|https://ask.qcloudimg.com/http-save/yehe-900000/cf9151de84fea6e7f312eb86d85421c0.png^0|0|0|1|0|0|0|1|1|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|X|8|@]|9|@$E|Y|F|Z|1|10]]|A|$]]|$1|G|3|C|5|D|7|11|8|@]|9|@$E|12|F|13|1|14]]|A|$]]|$1|H|3|I|5|6|7|15|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|16|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S|T|-4]]|U|$5|O|P|Q|A|$R|V|T|-4]]]]

This is for xcode 9, from crashlytics 3.4.0
<a href="https://i.stack.imgur.com/MwRAy.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/MwRAy.png" alt="STEP1"></a>
<a href="https://i.stack.imgur.com/R6mSO.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/R6mSO.png" alt="STEP2"></a>

After doing this, be patient and wait for a few minutes.

blocks|key|1693785|text|你有没有试过在设备上运行[[Crashlytics+sharedInstance]+crash]，看看是否会被报告？Crashlytics可能无法工作的原因有几个，包括其他崩溃记者等。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1693786|entityMap^0|C|10|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

Have you tried running <code>[[Crashlytics sharedInstance] crash]</code> on a device and seeing if that gets reported? There are a few reasons why Crashlytics might not work including other crash reporters etc.

blocks|key|1907445|text|如果您不上传dSYM文件，Crashlytics将不会显示您的崩溃，即使报告成功上传。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1907446|如果您将构建脚本设置为仅在CI服务器上运行，则可能会遇到此问题。然后，如果你已经通过xcode将你的应用程序复制到你的手机上，并且你在没有附加到调试器的情况下运行它，由于缺少dSYM文件，报告将被上传但被忽略。|1907447|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

If you don't upload the dSYM file, Crashlytics will not show your crash even though the report successfully uploaded.

You could run into this problem, if you have set up your build-script to only run on your CI server. Then if you have copied your app to your phone via xcode and you run it without being attached to the debugger, the report will be uploaded but ignored, because of the missing dSYM file.

blocks|key|1694318|text|有时，日志需要一些时间才能显示出来。我能在15-20分钟后找到它们|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1694319|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Sometimes, it takes some time for the logs to show up. I am able to find them after 15-20 mins

blocks|key|1907850|text|其中一个问题是，我觉得在运行脚本阶段，它应该是一个单独的CrashLytics运行脚本阶段。运行脚本是什么时候|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1907851|./Fabric.framework/run|code-block|syntax|javascript|1907852|使用我的其他一些脚本，一切正常，CrashLytics日志显示报告已提交，但web界面中什么都没有。|1907853|当我仅使用Fabric+run添加另一个运行脚本阶段时，它看起来像一个魔术:)|1907854|我的第一次尝试是使用cocoapods，但那不起作用。当我手动添加所有的框架和单独的运行脚本阶段的工作。|1907855|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

One of the issue I feel that in the Run Script Phase, it should be a separate Run Script Phase for CrashLytics. When had the run script 

<pre><code>./Fabric.framework/run
</code></pre>

With some of my other script, everything was ok, CrashLytics log show report submitted, but nothing was in the web interface. 

When I add another Run script phase only with Fabric run, it appears like a magic :) 

My first try was with cocoapods, but that did not work. 
When I manually add all the framework and a separate run script phase that worked.

blocks|key|1907819|text|这对我很有效，|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1907820|如果你是在iDevice上测试，只需用你的Xcode拔掉iDevice，然后运行你的应用。现在，如果崩溃，它将在仪表板上更新。|1907821|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

This worked for me,

If you're testing on iDevice, just unplug iDevice with your Xcode and run your app.
Now, If crashed it will be updated on dashboard.

blocks|key|1694074|text|我通过在Run+Script+(+Fabric(crashlytics))中取消选择"Run+script+only+when+installing“选项解决了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1694075|​|1694076|📷|atomic|offset|length|1694077|1694078|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/d21a8fba1891d1ace66ffada34e3ea94.png|imageAlt^0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@$G|V|H|W|1|X]]|A|$]]|$1|I|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q|R|-4]]]]

I solved by deselecting "Run Script only when installing" option in Run script (one for Fabric(crashlytics))

<img src="https://i.stack.imgur.com/9c2Az.png" alt="enter image description here">

I've setup the Crashlytics in my one iOS application and installed the application on a real device. My Crashlytics Dashboard is displaying that, I've successfully added the app. However, it's not sending crash report. My internet speed is not so good. But I can check my emails from this device. Can anybody guess, where is the problem?

Crashlytics is not sending Crash report from iPhone

Crashlytics

服务器

调试器

Xcode

我已经在我的one iOS应用程序中设置了Crashlytics，并在一个真实的设备上安装了该应用程序。我的Crashlytics仪表板显示了这一点，我已经成功地添加了应用程序。然而，它没有发送崩溃报告。我的网速不是很好。但我可以用这个设备查看我的电子邮件。有人能猜出问题出在哪里吗？

问Crashlytics没有从iPhone发送崩溃报告
EN

回答 12

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Crashlytics没有从iPhone发送崩溃报告EN

回答 12

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Crashlytics没有从iPhone发送崩溃报告
EN