Debugging tips and tricks on Apple Platforms.
_eventFirstResponderChainDescriptionAppKit includes a private category on
NSApplicationthat adds_eventFirstResponderChainDescription— a string describing the current responder chain. This can be a really useful debugging tool!You can also set the
_NS_4445425547user default to see a Cocoa debug menu.Today’s Darwin crazy hidden debugging tool of the day: iOS has a built in HUD for showing performance statistics like FPS, frame duration etc. […] This HUD can be activated by calling the private
CARenderServerSetDebugOptionfunction
Lately I’ve seen a lot of people asking “How are you getting that pseudo-code,” in regards to @steipete’s radar he filed and I thought this would be a great first blog post of mine as I’ve been wanting to for awhile. I spend a lot of my time in a tool called Hopper (it’s a must have in my toolbox) and while it’s an amazing tool, it can seem overwhelming at first. The goal of this post is to bridge the gap for those that have shied away or aren’t familiar with reverse engineering.
In this Xcode tutorial, you’ll learn how to use Instruments to profile and debug performance, memory and reference issues in your iOS apps.
Xcode comes with a bunch of tools you need to build, debug and release your apps. One of these tools is the Instruments app. The Instruments app is a great tool for profiling your iOS apps. It provides many profiling templates for debugging Core Data, catching memory leaks, disk read/writes, and much more. This week we will learn how to profile SwiftUI apps using the SwiftUI template.