Crashlytics is not sending Crash report from iPhone

Question

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?

I'm having the same issue with the Crashlytics service. Crash reports from the device are never sent (in my experience) - only from the simulator. I ended up using Crittercism crash reporting and error handling. — Sam Spencer, Jul 23 '13 at 18:58
Same happening to me. Try your application with another device than actual development device, this way you can get crash reports. — Samet DEDE, Jul 23 '13 at 19:32
Yes, I'm using my development device. Is it making the problem? — farhad rubel, Jul 24 '13 at 05:54
Without a complete setup description or test project this is impossible to answer. You should contact crashlytics support. Wild guessing doesn't help. — Kerni, Jul 24 '13 at 14:39
I'm so astonished that someone from Crashlytics saw my this post on StackOverflow and he contacted me by email; He's helping me to solve this issue. Let's see what happens. — farhad rubel, Jul 24 '13 at 21:11
My client has checked the app on his iPad. The application crashes... but the crash report never comes to my Crashlytics dashboard. — farhad rubel, Jul 31 '13 at 15:49
I have installed Crashlytics in our project too and distributed to about 15 people. There have been crashes, but no reports have been going through to Crashlytics. — jowie, May 01 '14 at 13:53
Hi @farhadrubel, wondering if this has been resolved for you? or if you have got any help from the Crashlytics team? — Johngorithm, Oct 13 '20 at 12:30

score 107 · Answer 1 · edited Jun 06 '20 at 00:16

107

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 (Source). 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 (copied from Crashlytics support site):
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 quick way to force a crash.

edited Jun 06 '20 at 00:16

SwiftiSwift

7,528
9
56
96

answered Nov 29 '13 at 12:59

Saurabh Hooda

2,536
2
20
30

9

This helped me. I've also discovered that in some cases. Crashlytics will not send the crash report unless the application is opened up again. To reiterate: User experiences a crash. User reopens application. Crashlytics sends previous crash report. – Tamby Kojak Apr 19 '14 at 21:42
1

@tambykojak this is likely due to the fact that iOS Crashes are quite volatile in most cases and the safer route is to send a crash report on the next app load versus sending it right away. Many Crash Reporting tools use this paradigm on iOS and other non-VM crash handlers. – pixelknitter May 06 '14 at 19:34
2

Thank you. This should be marked as correct answer :) – iMemon Dec 15 '15 at 10:52
Do i need to upload any dsyms in this case ? If so where can i find them ? – SoliQuiD Dec 17 '17 at 22:43
1

links are dead. – luky Jun 03 '20 at 15:40
This is still a valid answer, thx and +1 upvote or it. – Alex Terente May 04 '21 at 10:28
+1 as this solved my issue. I didn't run my app on the Simulator though, I ran it on my physical device in profile mode (Run > Profile in Android Studio), stopped the app, unplugged the device, restarted the app, triggered the crash via a button and then restarted the app. Note that profile mode is necessary as it allows you to restart the app many times on your device (something you can't do in the standard debug mode). – Wes1324 May 19 '21 at 15:54

Anand Suthar · Answer 2 · 2017-08-08T09:11:05.800

72

My be it's late but work 100%

Make some changes in project build settings like in below image

and follow these instructions.

edited Aug 08 '17 at 09:11

answered Oct 15 '15 at 12:21

Anand Suthar

3,678
2
30
52

Even after disabling Bitcode, I was still having missing dSYMS errors every now and then, and 100% of the time when debugging with the simulator. This fixed it. Thank you. – user3344977 Apr 13 '16 at 04:14
By changing this setting I was able to see crashes in firebase platform – Kwnstantinos Nikoloutsos May 27 '20 at 10:38
Thank you! That did it! – btraas Apr 09 '21 at 22:49

score 23 · Answer 3 · edited Apr 30 '16 at 11:38

The primary reason any crash reporter won't work on iOS is due to interference from different crash reporters. However, with Crashlytics specifically there could be something specific to them causing the crash report not getting reported.

Xcode debugger does NOT allow Any Crash Reporter to process crash reports. This is because XCode overrides any hooks into the crash handling call backs. This only happens when:

running app in Simulator (with debugger on)
running app on iDevice by directly build and run from Xcode with debugger on.

To make sure a crash is reported during your testing (http://support.crashlytics.com/knowledgebase/articles/92523-why-can-t-i-have-xcode-connected-):

Launch simulator
Press stop
Launch your app and force a crash
Relaunch the app from simulator
See the crash report in the web dashboard.

While a super old video it's still relevant, here's a video of the steps above (example from Crittercism): https://www.youtube.com/watch?v=sU6Su3PBFH4

Crashlytics disables itself when it detects a debugger attached. Not because it will not work, but because it will stop the *debugger* from working correctly. Crashlytics uses the same mechanisms the debugger itself uses, and it would be really frustrating for the SDK to mess up the normal debugging flow. For reference, I wrote most of the Crashlytics SDK. — Mattie, Jul 08 '18 at 14:21

score 11 · Answer 4 · answered Sep 09 '16 at 09:32

11

For me, the problem was that the device was connected to my Mac :) From this source:

Also, if you have your device connected to your Mac, XCode's debugger will step in as well. So just disconnect the device before testing :)

answered Sep 09 '16 at 09:32

Fengson

4,751
8
37
62

1

thank you for this!!! – Marcela Ceneviva Auslenter Dec 09 '21 at 15:44

score 8 · Answer 5 · answered Jul 20 '17 at 16:24

8

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.

answered Jul 20 '17 at 16:24

Gurjinder Singh

9,221
1
66
58

score 6 · Answer 6 · edited May 23 '17 at 11:47

6

We recently ran into this issue and I found that somewhere along the way the build script was removed. Adding it back in with the following fixed the issue for us:
./Crashlytics.framework/run <your_api_key> <build_secret>

Note : When using Cocoapods you will want to us the following instead of the above (source): ./Pods/CrashlyticsFramework/Crashlytics.framework/run

Adding a build script:

To add a Run Script Build Phase in Xcode 6, select your application target in your project, then select "Build Phases".

Click the small "plus" icon and select "New Run Script Build Phase".

You should now see a Run Script section in the middle of your Build Phase options, as shown above.

Inside the body of the Run Script Build Phase, paste in the script.`

The above quote comes from Crashlytics's visual tutorial, referenced in this post.

Note: I originally posted this answer verbatim for Crashlytics error code: 202 when Submitting files.

edited May 23 '17 at 11:47

Community

1
1

answered Dec 29 '14 at 20:26

James Nelson

1,793
1
20
25

This seems to have helped me. – Chris Prince Mar 19 '15 at 18:30
1

i used fabric previously for twitter integration now i want crashlytics also i added framework and i followed all instructions but i didn't get any crash reports to my dash board please help me – RameshIos May 13 '15 at 11:03
@iOS_Ramesh I would love to try to help you, but without knowing more it will be hard. To do this you should open a a new question outlining where you are at (the step you followed to integrate, any appropriate code snippets, and any feedback you are getting from Crashlytics or the console). – James Nelson May 13 '15 at 15:50
I Already post a new question ... http://stackoverflow.com/questions/30215049/crashlytics-not-sending-crash-reports-to-my-fabric-dash-board – RameshIos May 14 '15 at 05:54
1

Thanks for the hint. We had [ "Release" = "${CONFIGURATION}" ] check in our Run Script and we have renamed our Release configuration. – Marián Černý Jul 30 '15 at 06:06

score 4 · Answer 7 · answered Sep 08 '15 at 09:11

From the RayWenderlich site:

You won’t get any crash reports if Xcode intercepts the crash event! To make all the examples below work, you have to build and run the application, then click the stop button on Xcode. This way you will have the latest version installed on the the device. Once that is done, you can launch the app on the device itself, and then crash it all you want! All the crashes on your iOS device will be caught and sent to the server component of the service that you have integrated into the app. Crash reports are usually sent to the server the next time you start the app, so the steps to follow to generate a crash report on the server are as follows: Build and run on Xcode. Press the stop button. Run the app on your iOS device. Make the app crash. Run the app again.

score 3 · Answer 8 · edited May 23 '17 at 11:54

3

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

You should turn debug-mode on by

[Crashlytics sharedInstance].debugMode = YES;

My problem is here Crashlytics error code: 202 when Submitting files :(

edited May 23 '17 at 11:54

Community

1
1

answered Aug 12 '13 at 09:14

Tony

4,311
26
49

score 3 · Answer 9 · answered Oct 15 '13 at 18:01

3

Make sure you are not forcing the crash too early.

Set [Crashlytics sharedInstance].debugMode to YES;

Watch for

Crashlytics] Settings loaded

on the Xcode console logs.

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

answered Oct 15 '13 at 18:01

erkanyildiz

13,044
6
50
73

score 3 · Answer 10 · answered Jul 26 '16 at 16:33

I ran into a similar problem when trying the test crash code.

Crashlytics.sharedInstance().crash()

I was running my app from a device, without Xcode, and the crash wouldn't show up on Crashlytics Dashboard. What worked for me was the following tip from Crashlytics website:

Make sure to launch the app after crashing it, so that the crash can be uploaded

I commented out the above crash() call, and re-ran the app. Then the crash showed up in the Dashboard.

score 2 · Answer 11 · answered Nov 10 '15 at 12:32

2

This is for xcode 9, from crashlytics 3.4.0

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

answered Nov 10 '15 at 12:32

Ted

22,696
11
95
109

score 1 · Answer 12 · edited Jul 23 '13 at 19:28

1

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

edited Jul 23 '13 at 19:28

jszumski

7,430
11
40
53

answered Jul 23 '13 at 19:27

Patrick Tescher

3,387
1
18
31

No, I'm using int *x = NULL; *x = 42; code to see crash report. Moreover, my app is also crashing for different core data model. – farhad rubel Jul 24 '13 at 06:00

score 1 · Answer 13 · edited Dec 05 '14 at 17:40

1

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.

edited Dec 05 '14 at 17:40

James Nelson

1,793
1
20
25

answered Apr 28 '14 at 10:28

thetrutz

1,395
13
12

1

As reference: http://support.crashlytics.com/knowledgebase/articles/121064-why-don-t-i-see-data-from-my-first-crash-in-the-da – thetrutz Jun 24 '14 at 09:15

score 1 · Answer 14 · answered Mar 22 '17 at 23:48

1

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

answered Mar 22 '17 at 23:48

Lax

55
11

score 0 · Answer 15 · answered Sep 29 '17 at 08:10

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

./Fabric.framework/run

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.

score -1 · Answer 16 · answered Dec 04 '15 at 07:21

-1

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.

answered Dec 04 '15 at 07:21

Mohammad Zaid Pathan

16,304
7
99
130

score -3 · Answer 17 · answered Jun 21 '15 at 09:19

-3

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

enter image description here

answered Jun 21 '15 at 09:19

Shaz

958
7
9

That's just the script that uploads the symbols to Crashlytics; how that solve the issue of crash reports not being sent? What steps to do you take to avoid using Crashlytics when the symbols haven't been uploaded? This answer is misleading and just plain wrong. – Droppy Jun 21 '15 at 09:33

Crashlytics is not sending Crash report from iPhone

17 Answers17

Linked