It has many amazing features and new things to experiment with along with new tools, but let’s focus on Swift’s background first. Swizzling With Swift (0:55)Ībout a year ago upon Swift’s release, I was excited to play with Apple’s new language. As you might have guessed, I do like changes, and I enjoy trying out new things. Five years ago, I moved to Israel from Russia, and about five months ago I moved to the States.
#Iswift stack trace how to
Hi! I’m Sash and I’d like to discuss how to deal with proprietary codebases and how to fix bugs and crashes in third-party code.Ī bit about me: for the past two years, I had very long hair until last weekend before this talk was given when I shaved my hair and face - a traumatic experience. Sash goes over how to find bugs when there’s no access to the source code, demonstrates handy tools to reverse-engineer others’ code and add our own code to it, and even explains how to patch C functions using function pointers with Swift. Since most frameworks we use are still in Objective-C, we can swizzle methods or add to their original implementation to fix issues. However, Sash Zats demonstrates in this talk how we, developers with no access to Apple’s code, can use swizzling and patching to fix bugs in those private frameworks using Swift.
No code we write is flawless, but when bugs in Apple’s code leads to our app crashing, we typically cannot do much other than file a radar.
0 kommentar(er)
