I tried to solve this with lldb and I found a solution:
- Create a symbolic breakpoint for the UIViewAlertForUnsatisfiableConstraints symbol in the UIKit module.
- Add a return flow debugger command as a breakpoint action
- Add a second debugger command: "c"
- Disable "Continue automatically after evaluating actions"
If your application encounters a layout problem, execution is paused. With the "return stream" instruction, the UIViewAlertForUnsatisfiableConstraints function, which displays this error, is forced to return before a warning message is printed to the console.
With the c command, your application continues to run (Note: "Automatically continue after evaluating actions" somehow does not work in this case)
However, with these automatic actions, the breakpoint is likely to behave strangely if it hits twice in a row, which will cause your application to crash. To solve this problem, you can remove the breakpoint actions and enter the commands manually when the debugger pauses the program.
Palle Sep 08 '15 at 4:12 2015-09-08 04:12
source share