,
14 tweets,
7 min read
Read on Twitter
1/n Summary of my talk "Debugging in Xcode" at Swift Mumbai Chapter 8 @swiftindiagroup is as follow
2/n We can spend less time debugging if we set up our workflow to avoid debugging. 
3/n Static Analyser: It analyzes possible paths in code and reports potential & impossible to replicate bugs. Identified issues are shown in build-time tab of issue navigator.
4/n Run-Time tools: They detect issues in the at the run time. To enable run time tools, open "Diagnostic" tab on Edit Scheme window. Identified issues are reported in the Runtime Tab of Issues Navigator.
5/n: Main Thread Sanitizer detects invalid usage of AppKit, UIKit, and other APIs on a background thread.
6/n: Thread Sanitizer finds threading issues such as usage of uninitialized mutex and Data Races ( Multiple threads accessing the same variable without synchronization and at least one access is a write operation. )
7/n: Address Sanitizer or ASan detect memory corruptions and other memory errors at runtime. Refer developer.apple.com/documentation/… for more details
8/n: Undefined Behaviour Sanitizer is an LLVM tool for C languages that detect undefined behaviors.
9/n Use Asserts, preconditions and fatal error as runtime checks to avoid app going in invalid state with corrosponding custom error messages. App crashing is better than having difficult to replicate logical state.
10/n: Use Enums to write robust logic. If you miss to handle any case inside switch case, compile time error will bring it to your notice.
11/n Use enum + protocol to write robust but light weight network layer.
12/n Use enums to avoid typos while string constants
@threadreaderapp UNROLL
