0

My concern is to improve my app by collecting crash reports via the crash report service in iOS. For internal testing I uploaded a beta version of it using Xcode, containing a built-in error throwing NSRangeException. After archiving and uploading the app to the store it was installed on an iPhone 5s running iOS 9.3.3 using TestFlight. In my opinion I followed all the steps described here, but with no success.

In the diagnostic settings of the device, automatic crash reporting is enabled and I can see various crash logs (>10) caused by my app. On the iTunes Connect website I see only three overall crashes and just one is shown in the Xcode Organizer. Even after syncing the device through iTunes nothing changed.

Contacting Apple-Support didn´t help either. because they had "very little information available".

For stability improvement I need to make the crash reports available, so I have a couple questions:

  1. Which steps are done internally by the crash reporting service and how long does it take to see some results? (As mentioned in iOS developer library documentation it can take up to three days, which are long overdue by now).

  2. Are the reports caused by the same error gathered and reported as a single entry? If not what is the procedure?

I already searched for some similar questions and came up with the following information:

I hope somebody has deeper insight or already gained more experience using Apple`s Crash Report Service and could share this information. Thanks a lot in advance.

Community
  • 1
  • 1
Dmitry
  • 372
  • 5
  • 18
  • Why don't you try Crashlytics? – Vishal Sonawane Jul 27 '16 at 12:41
  • I am aware of Crashlytics and it's advantages over the crash report service, but before embedding some 3rd party library I wanted to verify whether it is pointless to use Apple's solution. – Dmitry Jul 27 '16 at 12:54
  • I've also heard HockeyApp is pretty good. I work for Sentry as well (we also do crash reporting for iOS, as well as all the other languages). – ehfeng Jul 27 '16 at 15:21

1 Answers1

1

Fabric may be a good choice.
It can collect you crash report, and give a crash description.

zylenv
  • 942
  • 4
  • 13
  • As far as I know Crashlytics mentioned by @Vishal Sonawane is part of Fabric and seems a good choice. Nevertheless is the crash report service so bad or just unpopular by the most people? – Dmitry Jul 27 '16 at 13:00