if ([myArray objectForKey:@"identifier"] isEqualToString:@"myID"]) {
    DebugBreak(); // Step through the code from here
}

The macro below will allow you to write code like the example above. It will work on both real iOS hardware and in the iOS simulator:

#if TARGET_CPU_ARM
    #define DebugBreak() __asm__ __volatile__ ("mov r0, %0\nmov r1, %1\nmov r12, #37\nswi 128\n" \
                                            : : "r" (getpid ()), "r" (signal) : "r12", "r0", "r1", "cc")
#elif TARGET_CPU_X86
    #define DebugBreak() __asm__("int $3\n" : : )
#endif

Anything that makes debugging easier and more efficient is a good thing in my book.

If you’re one of the people and you’ve tried the various fixes that can be found, but you’ll still having issues, then this is what worked for me:

1. Download ProKit 5.1 from Apple.
2. Double-click ProKitUpdate5.1.dmg and you’ll see ProKitUpdate5.1.mpkg.
3. Right-click (or Ctrl-click) ProKitUpdate5.1.mpkg and click Show Package Contents.
4. Expand Contents and Packages revealing ProAppRuntime.pkg and ProRuntime.pkg.
5. Right-click (or Ctrl-click) ProAppRuntime.pkg and click Show Package Contents.
6. Expand Contents and copy Archive.pax.gz to your Desktop.
7. Double-click Archive.pax.gz and the Archive Utility will extract the contents to a folder called Archive.
8. Within the Archive folder, navigate to System/Library/PrivateFrameworks and copy the ProKit.framework folder to your Desktop.
<br/>You now have version 5.1 of the ProKit.framework ready to replace the 6.0.1 version.
9. Open up Terminal (which can be found in /Applications/Utilities) and enter the following command:

sudo pkgutil --forget com.apple.pkg.ProAppRuntime

Since you’re running the command through the Super User account, you’ll be prompted for your Administrator password. Type in your password and click OK.
10. In Finder, navigate to /System/Library/PrivateFrameworks and copy the ProKit.framework folder to your Documents folder.
11. Delete the ProKit.framework folder from /System/Library/PrivateFrameworks. You’ll be prompted for your Administrator password.
12. This is important. I’ve seen users inadvertently copy ProKit.framework 5.1 into the existing ProKit.framework folder. Deleting the existing ProKit.framework folder will ensue this does not happen.
13. Copy the ProKit.framework folder from your Desktop to /System/Library/PrivateFrameworks. You’ll be prompted for your Administrator password again.
14. Launch Final Cut Studio and you should be good to go.