crash-reports

iPhone app “has active assertions beyond permitted time”

混江龙づ霸主 提交于 2019-11-28 23:02:23
问题 I'm trying to make sense of some crash logs I received for my iPhone app. The main thing that I can see that's useful is: Application Specific Information: MyMoodTrack[144] has active assertions beyond permitted time: {( <SBProcessAssertion: 0x73c6480> identifier: Suspending process: MyMoodTrack[144] permittedBackgroundDuration: 10.000000 reason: suspend owner pid:26 preventSuspend preventThrottleDownCPU preventThrottleDownUI )} This reads to me as if the process has been killed because it

App crashes in Release build but not in debug

做~自己de王妃 提交于 2019-11-28 22:42:35
As I said in the title, I am writing an app for iPhone which runs perfectly in debug mode but when I build it as release and install it via TestFlight, it crashes. Due to the crash log it might have to do something with this lines: let path = NSBundle.mainBundle().pathForResource("PrinterList", ofType: "plist") if path != nil { let printerDic = NSDictionary(contentsOfFile: path!) let printerList = NSArray(array: printerDic.allKeys) printerNames = printerList as [String] } I am using an framework from Brother to print without AirPrint, but I think thats not the problem because the app crashes

How to symbolicate crash report from Apple received in .txt format not .crash format

房东的猫 提交于 2019-11-28 18:28:08
My app got rejected from Apple and I have got crash reports in .txt format instead of .crash format. How can I symbolicate or read the crash report ? Shakti When you get your crash report as a .txt file just follow these steps : Change the file extension .txt to .crash (eg mycrash.txt to mycrash.crash ). Create a new folder in desktop and copy the mycrash.crash file to the newly created folder. Copy the .dSYM file: update: download all DSYMs from appstoreconnect activity- they are properly named with their UUIDs Unzip DSYMs, then copy the App and Sybolicate script as defined below: https:/

Crash logs generated by iPhone Simulator?

怎甘沉沦 提交于 2019-11-28 15:13:41
问题 Are there any crash logs generated by iPhone Simulator? the Simulator crashes a lot but not leaving any traces in Console... the crash log will be useful. 回答1: The console will show the NSLog() output from an app running in the simulator. The crash logs are saved to file. I have found some in my home directory under ~/Library/Logs/DiagnosticReports/ They have a file extension of .crash Something I haven't yet figured out is how to get them to generate even if the debugger grabs the EXC_BAD

How to integrate Crashlytics into an iOS framework target?

删除回忆录丶 提交于 2019-11-28 12:20:51
I have an iOS framework target, and I need integrate Crash reporting system for it. So Crashlytics looks good, but This Xcode project does not have any Mac or iOS targets So, is there any way to integrate Crashlytics directly into iOS framework? Garnett Thanks Mike Bonnell for your comment here , which says: 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

Android saving logs on every run for crash report

这一生的挚爱 提交于 2019-11-28 11:18:57
I'm currently developing an android app. I noticed a very rare error which leeds to a crash of my app. Unfortunately, I had my smartphone never connected to my pc when it occured. So, is there a way to automatically save all logs (and especially the thrown runtimeexceptions) to a file when my app starts, so that I can copy this file to my pc and analyse the error? The file should be overwritten on every start of my app, so that it contains only the logs of the last run... How can I achieve that? regards You can find help by following this link Writing crash reports into device sd card You don

iOS 8 NSInternalInconsistencyException

喜你入骨 提交于 2019-11-28 08:12:28
I get the following crash reports. They only occur on devices with iOS 8. Notice the message: Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'this request has been neutered - you can't call -sendResponse: twice nor after encoding it' Crash report: Date/Time: 2014-08-31T01:39:15Z OS Version: iPhone OS 8.0 (12A4345d) Report Version: 104 Exception Type: SIGABRT Exception Codes: #0 at 0x1964cb270 Crashed Thread: 0 Application Specific Information: *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'this request has been

Xcode Crash Organizer does Not Symbolicate .xccrashpoint Files

a 夏天 提交于 2019-11-28 06:20:29
The new Xcode 7 "Crashes" tab in the organizer shows a handful of crashes from the AppStore for my app. According to the documentation , there should be a stack trace. However, none of the 6 crashes have symbolicated stack traces: I've tried clicking "Open in Project" but it's just as useless: Of course, I included the dsym and debug info when I submitted to the store. I still have the submission build in my organizer, so the dsyms are still present on my machine. How can I get a proper stack trace on this? esilver Not ideal, but if you right-click an .xccrashpoint file, select "Show Package

Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 32140

孤街浪徒 提交于 2019-11-28 04:43:37
50% of the time when running my app I'm getting this error 06-20 12:56:51.183: A/libc(32140): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 32140 (example.www) I just have to reopen the app and then it works. But I don't know why I'm getting this error and the app crashes. I'm working with big images with dimensions, almost 1200x1200px and setting that as a background. I also use that image as a bitmap for some other activities as background. Also doing some calls to a server and getting JSON data back. Hope I gave enough information, because I don't know what to look for... I'm

Strange iPhone crash log

╄→гoц情女王★ 提交于 2019-11-28 03:27:35
问题 Can anybody tell me the reason for this crash. Specially I am concerned about this - **Application Specific Information: iMixtapes[1185] has active assertions beyond permitted time: {( <SBProcessAssertion: 0x66bc490> identifier: UIKitBackgroundCompletionTask process: iMixtapes[1185] permittedBackgroundDuration: 600.000000 reason: finishTask owner pid:1185 preventSuspend preventIdleSleep , <SBProcessAssertion: 0x66ade50> identifier: UIKitBackgroundCompletionTask process: iMixtapes[1185]