I want to access the crash reports of my app inside my app and i need to send the crash reports to a server. I searched in google and I couldn't find any API that helps my purpose but I found there are open source projects like QuincyKit, plcrashreporter for getting the crash reports of the application. If I use these APIs will apple reject my app ?
Thanks in Advance
There is no API from Apple to do that. So the only chance is to use a 3rd party framework which catches the crash when it happens and provides options to further process it afterwords.
There are multiple solutions available, one is QuincyKit. The second part of the answer of Including custom data into iOS crash dumps shows all known solutions and services that you can use.
Note: I am the developer of QuincyKit and also part of the HockeyApp team.
About QuincyKit:
I've used only Flurry, which has crash collection, and there seems to be no problem in using these libraries in your project for the app store.
Related
I have a Xcode project in which the data layer is separated in a framework in order to be shared between the main iOS app and the Today extensions.
I have followed the general setup instructions here and the instruction for multiple targets here. I do get crash reports from both the app and the data framework. However, in the crash report I find only logs (CLSLog(#"Bla bla")) and keys ([CrashlyticsKit setObjectValue:#"value" forKey:#"key"]) from the main app. Logs and keys from the data framework are not recorded in the crash report even though I have verified code passes through them. As a simple example - user logs in and I set the user identifier from the data framework; then a crash happens in the app and in the crash report there is no user identifier.
I have seen this topic in which the recommendation is to not include Crashlytics in a framework that is intended to be distributed as a third party library. This is not a concern in my case and it also hints at the possibility of including Crashlytics both in the app and framework.
So my questions are:
Is it possible at all to get crash reports with logging and keys from both the main app and the framework?
If yes - what is the correct setup?
Fabric/Firebaser here -
Quoting from Mike Bonnell:
Sure, our SDK only supports being initialized once. Being initialized in a framework and application would cause a conflict. You and the app developer would have different API keys and there is no way to ask the app developer to give permission to your SDK to share stack traces from their code with your framework.
Including us in your framework will cause issues for your framework and anyone that uses it, so that's why I said don't include us! Totally understand that SDK developers would love to see this supported.
Does anyone know when GoogleAnalytics iOS SDK v3 sends the crash to their servers (when app is on AppStore)?
Does it send when the app crashes, or when the user reopens it?
The problem is that, I'm viewing a lot of crashes from a bug that I think I solved, and on HockeyApp I'm not receiving anymore of these.
Thanks
Some points:
Crash reports are usually send the next time the app starts. Trying to send them at crash time may cause big harm to an app and its data. As far as I know GoogleAnalytics only sends reports on the next startup.
Google Analytics can only catch crashes caused by exceptions! In addition, any other exception handler will NOT be able to catch the exception! This is why you only see reports in Google Analytics but not in HockeyApp. This will happen with any other 3rd party SDK too. Usually the last crash reporting SDK you setup in your app wins.
You can test this yourself by using the CrashProbe open source project and include the SDK or SDKs you want to use. And then monitor the behavior for various crash types.
From my personal experience, Google Analytics is not good in capturing crash report as I think the crash report might not be real time . Personally, I like bugsense and I am using paid version of Bugsense. Its free version is good for most apps as well. May be you can try out the free version.
If there is a crash for an application, can I capture the crash logs and send it to a server right after the crash. I guess my question really is if the app crashed can I use the network api to send some data to the server.
Lots of services out there to do this... HockeyApp & TestFlight spring to mind.
Update: HockeyApp has just released a Mac Application 'HockeyCoach' to allow you to view crash reports within a native App, with awesome functionality like viewing the source code referenced in the crash log etc...
I highly reccomend you check it out: http://hockeyapp.net/releases/hockeycoach/
Yes, there are several solutions that provide this functionality. One of them that I'm intimately familiar with (and works very well) is Apigee's Mobile Analytics (http://apigee.com/docs/enterprise/content/analyze_apps).
One of the important points for dealing with crash logs is to save a copy of your .dSYM. This is needed to symbolicate the crash log.
Try using Crashlytics. Extremely simple to incorporate into app and is completely free.
Not sure if that is possible. But what happens is, sometimes our app randomly crashes. We don't know what exactly the problem is. Is there a way for us to get the crash report off user's iphone? By code, or by another app?
Thanks.
You can inject a third party code in your app, which would basically save your crash reports and thereafter you can use them for analysis. The way we do is capture any crash logs and upload them to the app server, which uses the info to display through a user-friendly web Interface (access controlled for admin purposes).
A great open source Crash Reporter library can be found here https://github.com/kstenerud/KSCrash
It's the user who decides from Settings > General > About > Diagnostics & Usage whether to automatically send crash reports or not.
You can also use a third party component to get detailed information about crash events, for example Crittercism.
If you're interested in 3rd party services for crash reporting for iOS it's hard to go past Crashlytics. Very fast crash reporting, simple installation, great response times to queries.
I'd also mention the TestFlight SDK, which is free and easy to use, and allows you to gather crash reports easily from all your testers, and also do remote logging and other stuff. I used it on a location based app I was working on a while ago, and it was very helpful with debugging
I would like to extract crash logs of those users who are using my enterprise app. In case of the App Store apps I can get this information from iTunes connect. Since there is no intervention of App Store in case of Enterprise deployment therefore not sure how to access this information.
Is there any Objective-C API through which I can access the crash logs with the application code and upload them on my server using a web-service?
There is no Objective-C API available to access iOS generated crash reports. The only way to automatically access them, is adding a crash reporting framework to your apps that also catches the crashes and let you send them to a service or your own server.
I highly recommend not engineering your own crash reporting or exception handling mechanism, since it is way too complicated to make it right and not introduce more dangerous problems that could e.g. cause your app users to loose data.
The second part of my answer here lists a few options, contains open source projects, services with open source SDKs and closed source options: iOS crash log catch, debug info.. Catch and send via email to the Dev team
Try using Crashlytics.
Very powerfull. Very pleasant to use.
You can instruct your users to extract the logs from iTunes and send them to you. Take a look at the "Sending Crash Reports to a Developer" section of this document: http://developer.apple.com/library/ios/#documentation/Xcode/Conceptual/ios_development_workflow/35-Distributing_Applications/distributing_applications.html