crash-reports

Programmatically getting Crash Reports inside an iOS app

微笑、不失礼 提交于 2019-12-06 11:51:18
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 Kerni 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,

iOS 7 App Crash EXC_CRASH (SIGABRT) objc_exception_throw Works fine on iOS 6

拟墨画扇 提交于 2019-12-06 11:11:20
Our app is crashing in iOS 7, its working fine in iOS 6. We are not sure what is causing the issue. We can see that there is some exception thrown but we are not sure where in code is causing that. Here is the crash report: Incident Identifier: 1F589930-15BD-49F7-80E6-831A95092FDF CrashReporter Key: aaa79870161ff1e371394b881a26e97f0066f464 Hardware Model: iPhone5,2 Process: myapp [1492] Path: /var/mobile/Applications/A121DF2F-A7B9-4DD9-9FBC-BB06CD7C5EF5/myapp.app/myapp Identifier: co.uk.myapp Version: 1.0 (0.9) Code Type: ARM (Native) Parent Process: launchd [1] Date/Time: 2013-10-01 14:59:17

iOS app cannot be opened after update

风流意气都作罢 提交于 2019-12-06 10:35:58
We have an app live in the app store for almost an year, and we've been receiving several bad reviews from customer which cannot open the app after updating it. Users have reported they are unable to launch the application following deleting and subsequently reinstalling the application. One user did indicate they could launch the application only following a factory reset of their iPhone. We believed the issue was related to the Keychain, since this seems to be persistent in the system. For this reason we updated the third party library we are using to access the keychain to https://github

How to force an application crash when AccessViolationException is detected

旧时模样 提交于 2019-12-06 07:31:48
We use an automated crash reporting tool (namely http://crashrpt.sourceforge.net ) for generating crash reports. So if a piece of unmanaged code fails by accessing a NULL pointer for example, the application crashes, the crash reporting tool activates and we get usable stack trace for diagnosing and grouping issues. The problem is that .NET seems to interfere with crash handling in some cases. One sample is the following: this.Dispatcher.BeginInvoke((ThreadStart)delegate { // Send message to unmanaged control for performing a specific task. User32.SendMessage(...); }, DispatcherPriority.Input)

How does OS X generate a crash report?

爱⌒轻易说出口 提交于 2019-12-06 05:54:44
问题 The material available from web, mail-list, books like Mac OS X Internals , and even source code is quite limited. Now I know that xnu kernel raise an EXC_CRASH, which notify launched to start "Problem Reporter.app" (prior is Crash Reporter.app). Is this app using some debugging interface to generate the crash report, or is it kernel already generating the report and just notify the app to open the already-generated report? 回答1: Every Mach thread and/or task (the underlying kernel object on

iPhone sdk read crash files programmatically?

青春壹個敷衍的年華 提交于 2019-12-06 05:31:41
问题 I want to read crash files programmatically. How can I do this? I am allowed to do this? Will my application be rejected if I do this? Any advice, link, tutorial is well come. 回答1: I am not sure if its possible. You can’t access the logs themselves, but you can catch uncaught exceptions and generate your own crash logs for which I think you can make use of the following example: http://cocoawithlove.com/2010/05/handling-unhandled-exceptions-and.html it's very simple and easy to use, just

iPhone application crash on launch

荒凉一梦 提交于 2019-12-06 03:34:16
问题 We are receiving a crash log from iTunes connect that is a little strange. We were preivously having problems with our app taking to long to return from ApplicationDidFinishLaunching. This was caused by doing a too much work inside of applicationDidFinishLaunching and we exceeded the 20 second time out on slower devices. To fix this we moved all of our setup code out of ApplicationDidFinishLaunching and moved it into a special secondaryLoadingController. On top of that we moved the setup code

Reporting Crashes in Android Library via Crashlytics

吃可爱长大的小学妹 提交于 2019-12-05 20:10:14
I am building an android library that I plan to integrate into many 3rd party apps(which do not belong to me). So, I am trying to figure out a way to find out if any of those 3rd party apps crashes due to the code in my library. Is there any way to find that out? I was looking at Crashlytics to achieve the same. But, as I understand, Crashlytics will be able to give the Crash analytics to only the app owner, right? Is there any way to collect the crash info without the intervention of the 3rd party app? Thanks. EDIT: This isn't a duplicate of Integrating Crashlytics to library project because

Crash reporting watchdog for when my application locks up on a customer's machine

拈花ヽ惹草 提交于 2019-12-05 19:45:25
I'm working with a somewhat unreliable (Qt/windows) application partly written for us by a third party (just trying to shift the blame there). Their latest version is more stable. Sort of. We're getting fewer reports of crashes, but we're getting lots of reports of it just hanging and never coming back. The circumstances are varied, and with the little information we can gather, we haven't been able to reproduce the problems. So ideally, I'd like to create some sort of watchdog which notices that the application has locked up, and offers to send a crash report back to us. Nice idea, but there

xCode device logs not populating after application crash

白昼怎懂夜的黑 提交于 2019-12-05 19:02:28
I'm getting a crash on my iPad 2 when building my Corona SDK app with a distribution profile, and putting it on my device via a USB cable. I'm testing a bug that happens when the internet is not connected (not sure if relevant). When the app crashes, the devices window's output stream states that it's storing a crash report ( http://pastebin.com/Qa3BeaJ2 ), but then the crash never shows up when I push the "view device logs" button. When I push that button, I get an error message. Is resolving this the secret to getting my crashes to show up in the device logs? Jul 28 13:41:17 JackSpicer crash