This is kind of a note to my future self, which I figured I'd post here (my future self will probably be Googling this anyway)
1) Break on UIViewAlertForUnsatisfiableConstraints
2) If "Will try to break constraint" does not appear in the debug area, hit "Continue"
3) Take note of the constraint's printed memory address
4) If you have constraints in code, use the stack trace to go back as far as necessary to the point in the code where the constraint is created.
Edit: A good practice for constraints in code is to set identifiers that will allow you to identify the problem constraint during debug time.
If anyone has any better ideas (such as using an NSLayoutConstraint property) please let me know.
1) Break on UIViewAlertForUnsatisfiableConstraints
2) If "Will try to break constraint" does not appear in the debug area, hit "Continue"
3) Take note of the constraint's printed memory address
4) If you have constraints in code, use the stack trace to go back as far as necessary to the point in the code where the constraint is created.
Edit: A good practice for constraints in code is to set identifiers that will allow you to identify the problem constraint during debug time.
If anyone has any better ideas (such as using an NSLayoutConstraint property) please let me know.
Last edited: