crash-reports

问题 I have an app being tested via TestFlight on iTunes connect. One of the test devices keeps crashing and I'm pretty sure that there should be crash logs on itunes connect but I can't find any on my testflight builds. Does anyone know where they can be found? 回答1: It is simply not possible for Betas, check here for more information, this is the important part: Hope that helps :) 来源： https://stackoverflow.com/questions/29368392/itunes-connect-where-can-i-see-the-crash-reports-for-testflight

问题 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

问题 Since the latest builds I'm always getting the following error message when trying to upload the build to Crashlytics. Archive Distribution Error: -3 Could not upload the distribution. The operation couldn't be completed. (HTTP error 422.) I've tried the following: restart Xcode and Fabric plugin rm -rf ~/Library/Caches/com.crashlytics.mac different internet connections (WiFi, mobile) 回答1: Mike from Fabric here. We had a temporary issue where distributions could not be uploaded. That issue

问题 I'm trying to setup Parse crash reporting on iOS, using this guide, but unfortunatly, even after several crashes, there is nothing on my dashboard. Here is my code (i'm using sdk 1.6.3) : - (void)crash { [NSException raise:NSGenericException format:@"Everything is ok. This is just a test crash."]; } ... [ParseCrashReporting enable]; [Parse setApplicationId:@"********" clientKey:@"********"]; [self performSelector:@selector(crash) withObject:nil afterDelay:10.0]; I followed the troubleshooting

问题 I have already tried crashlytics but it is not supported. this is the reply i got from their team Thanks for reaching out on this and Crashlytics, or any part of Fabric, cannot be included in any SDK that is distributed to external apps. As you mentioned, this will cause conflicts for both the SDK and app. With that said, we do hope to support this in the future and if you'd like, I can keep you updated on that. I have tried to set my own UncaughtExceptionHandler for this but the problem with

问题 I have an iOS app, written in Swift in Xcode 6.2, using the Parse SDK 1.7.0. I've gone through the Parse Quick Start instructions for setting up crash reporting (including ParseCrashReporting.enable() in the AppDelegate), but it seems that my run script is having an issue. The error is: App "/Users/ben/Library/Developer/Xcode/DerivedData/MyApp-ahydphsjgdgefbhcdodokcmofehe/Build/Products/Debug-iphonesimulator/MyApp.app.dSYM" wasn't found. Command /bin/sh failed with exit code 1 . According to

问题 It seems that as of Android 2.2, there is a new feature for sending crash reports, as mentioned in the links: http://www.androidcentral.com/new-android-app-crash-report-tool-already-and-running http://android-developers.blogspot.com/2010/05/google-feedback-for-android.html http://developer.android.com/sdk/android-2.2-highlights.html http://www.youtube.com/watch?v=o8unC9bA4O8 How do I use this feature? Is it automatic for each application downloaded from the market (aka Google Play Store)?

问题 I'm coding in C++/MFC using WinAPIs. My software consists of a local service and a user-mode app that provides user interface for a logged in Windows user. I'm looking for a way to collect .dmp and .hdmp files in case of crash in either of those modules. I know that WER supposedly collects them and submits them to Microsoft. Is there a way to collect those files and keep them somewhere on the hard drive? PS. I need this to work under Windows XP SP3, Vista, 7, 8. 回答1: Windows 2000 and XP

问题 I've tried searching for this, but no luck, so hoping there are some guru's who may know the answer. I'm seeing loads of reports in iTunes Connect of my app crashing with a particular stack trace, but the stack trace reveals nothing useful. #0. Crashed: main 0 UIKit 0x1871100c0 __56-[UIPresentationController runTransitionForCurrentState]_block_invoke + 324 1 UIKit 0x1871100bc __56-[UIPresentationController runTransitionForCurrentState]_block_invoke + 320 2 UIKit 0x1870630c8

问题 I there any way to register a global error handler that will prevent application from crashing? Crashing reporting is described here: How do I obtain crash-data from my Android application?. One thought I had was to extend these solutions to take in the application context so a redirect to a particular reporting activity could be made? But not sure if the application context is valid at this point once there is a crash to report? But how can you redirect user to a global error message