When you get the dreadful “will attempt to recover by breaking constraint” warning in Xcode, just know you can use the constraint address to filter the view hierarchy in “View Debugging/Capture View Hierarchy” and identify the broken constraint.
1. Visit the report generator
2. Fill the data (specify N/A when not sure because it likely does no apply)
3. Choose 5D992 for Export Control Classification Number
4. Select MMKT for Authorization Type
I was bitten by the infamous
BUG! exception in phase 'semantic analysis' in source unit '_BuildScript_' Unsupported class file major version 60
error while building a React Native app I developed for my employer:
Xcode supports the possibility of setting symbolic breakpoints to inspect the status of your app when some odd condition occurs.
Great post on StackOverflow about detecting when an app is killed, due to an exception, a signal, etc.