Is Xcode debugging/crash report in Swift broken?
I’ve been working with Swift for over a year now and things seems to be only getting worse with each new Xcode release.
Is it only here that crashes in a app aren’t reported correctly? Most of the time it’s only
main() (yes I use a main.m in my project):
That’s not helpful. If I don’t add an ‘All Exceptions’ breakpoint, I can’t find where the crash happened. I just got used with not having any help at all from LLVM about any errors on my Swift code, and even then:
Is there something I’m missing here? I feel like back when I was programming with Objective-C things were much better.
I found this solution: https://stackoverflow.com/a/27356008/447360
Which helps sometimes:
Still looking on how to get the exception/error message to show up (again) in Xcode.
2 Solutions Collect From Internet About “Is Xcode debugging/crash report in Swift broken?”
Ok, so I finally was able to improve the debugging info for breakpoints.
Basically you should create a “All Exceptions” breakpoint like this:
This is for Xcode 7+ only.
Check if the “Debug -> Debug Workflow -> Always Show Disassembly” is turned off.
- Difference between DispatchQueue.main.async and DispatchQueue.main.sync
- PyObjc and Cocoa on Snow Leopard
- Why I did not receive any notification on my iPhone?
- Query Available iOS Disk Space with Swift
- Resize UIImage with aspect ratio?
- How do you find out what is retaining an object in Instruments?
- AFNetworking – How can I PUT and POST raw data without using a key value pair?
- POST JSON data into existing object
- How can I add JPEGs to an asset catalog in Xcode?
- IONIC/cordova, make phone call in IOS
- Combobox component for Swift (failed with DownPicker)
- Shell script for remove the unneeded architectures while archiving not working
- Run Destination Not Valid For Running Scheme Xcode
- How to cache content in UIWebView for faster loading later on?
- Xcode cannot run using the selected device