crash-reports

How to capture iOS crashes in MonoTouch application

由 偶尔善良 提交于 2019-12-05 00:55:22
问题 We have logging in place for any .Net Framework exceptions that occur in our iPad MonoTouch application and can get these back to our support department to help analyze and resolve issues. However, if the application crashes due to an iOS error (i.e. sigsev), we are unsure how to capture that information or tell our very unsophisticated users how to obtain and provide it to us. Can anyone offer any guidance on this? 回答1: Crashes will often (but not always, e.g. out-of-memory) create crash

Android App Crashes on HTC and Sony Ericsson Phone

由 核能气质少年 提交于 2019-12-05 00:03:02
问题 We launched the app on the Market today - Nomad. I am getting reports that the app crashes on HTC and Sony Ericsson Phones. I got the following Log report from one of the USER. java.lang.RuntimeException: Unable to start activity ComponentInfo{com.m7.nomad/com.m7.nomad.SplashActivity}: java.lang.UnsupportedOperationException: Can't convert to dimension: type=0x3 at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1956) at android.app.ActivityThread.handleLaunchActivity

Where can I view the Google Analytics iOS crash logs?

由 人盡茶涼 提交于 2019-12-04 23:30:32
问题 In Google Analytics native SDK for iOS (v2 Beta) I found the following line in there documentation: // Optional: automatically track uncaught exceptions with Google Analytics. [GAI sharedInstance].trackUncaughtExceptions = YES; Does this mean, that Google Analytics now also supports crash logs tracking (like BugSense or Crittercism)? But where do I find them in the online interface of Google Analytics? 回答1: On the left panel, expand the Engagement menu and then click on Crash and Exceptions

Crash reporting in Python

由 帅比萌擦擦* 提交于 2019-12-04 22:57:18
问题 Is there a crash reporting framework that can be used for pure Python Tkinter applications? Ideally, it should work cross-platform. Practically speaking, this is more of 'exception reporting' since the Python interpreter itself hardly crashes. Here's a sample crash reporter: 回答1: Rather than polluting your code with try..except everywhere, you should just implement your own except hook by setting sys.excepthook . Here is an example: import sys import traceback def install_excepthook(): def my

Crash log without crash?

由 ♀尐吖头ヾ 提交于 2019-12-04 18:23:49
Hey this may be a stupid question but I couldn't find the answer anywhere, apologies if the answer is easily found and if my research skills are pants. anyway is it possible to generate a crash report when an app doesn't crash? so say if a user encounters a bug could there be an option to allow them to generate a crash report which can then be sent to me? also how would I go about doing this? Thanks for any help :) I have used it couple of times when I had to print stack trace: + (NSArray *)backtrace { void* callstack[128]; int frames = backtrace(callstack, 128); char **strs = backtrace

EXC_BREAKPOINT (SIGTRAP) for App Review Team. Not Reproducible

由 亡梦爱人 提交于 2019-12-04 15:53:46
问题 So, my App (iOS, Swift 2.2, Xcode 7.3) got rejected by Beta App Review team because it crahsed on launch. UPDATE Got an answer from the App Review Team...it's only crashing on iPad, not on iPhone. The thing is that I can't reproduce this crash. Not even when testing on my 3 physical devices (iPhone 4S, iPhone6 and iPad Air) with a clean install nor update through TestFlight Internal Testing (so exactly the same build & archive as App Review Team is reviewing) Extract of crash log (received

iPhone sdk read crash files programmatically?

由 那年仲夏 提交于 2019-12-04 12:19:00
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. 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 register exception and signal handlers using: NSSetUncaughtExceptionHandler(&HandleException); signal(SIGABRT,

Debugging .xccrashpoint

由 早过忘川 提交于 2019-12-04 11:02:51
问题 I've got some logs on Xcode's Organizer but I don't know how to properly debug them. I've read Apple Documentation at Apple Documentation by it doesn't tells me where the error/crash message is. It's hard to debug if you don't know what has caused it. When I try to open each log in Finder, it opens a .xccrashpoint file, not a standard crash log. Is there anyway to know the error message (as we received on previous crash reports)? 回答1: I have stumbled on this recently too. What helped me was:

Does atos not supports armv7s?

由 故事扮演 提交于 2019-12-04 10:38:25
问题 I tried to symbolicate an iOS crash report sent from Apple. atos -arch armv7s -o APP_BINARY_PATH 0x0006a23c 0x35000 + 217660 And I got below error. > atos: Unknown architecture: armv7s I make sure that binary includes armv7s build by using otool. Does atos not supports armv7s? When I changed -arch argument to armv7, it works fine. My Xcode version is 4.5.2. 回答1: You need to use the atos version that is part of Xcode. You can find it here: /Applications/Xcode.app/Contents/Developer/usr/bin

iPhone application crash on launch

由 南笙酒味 提交于 2019-12-04 08:36:44
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 inside of that controller to a separate thread. However, we are still seeing crash logs that say our
订阅 crash-reports