Databases
StackOverflow2013
Postsdbo
POMapping memory address of unsatisfyable NSLayoutConstraints to UI controls
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POMapping memory address of unsatisfyable NSLayoutConstraints to UI controls
    primarykey
    data
    text
    <p>I appreciate that XCode will catch the unsatifyable <code>NSLayoutConstraints</code> and gives you some information about it, however I do not know how to take the memory addresses of the controls/constraints and map that to the actual controls that have problem. </p> <p>My app is fairly large (around 20 screens), some are large UIViewControllers with several child view controller within them. Some are UITableViews with custom cells and UICollectionViews with custom cells. I'm having a hell of a time tacking down the cause of this error (which happens on landscape rotation) </p> <p>Here is the information from my console: </p> <pre><code>2013-05-02 11:18:53.225 Smile[7519:c07] Unable to simultaneously satisfy constraints. Probably at least one of the constraints in the following list is one you don't want. Try this: (1) look at each constraint and try to figure out which you don't expect; (2) find the code that added the unwanted constraint or constraints and fix it. (Note: If you're seeing NSAutoresizingMaskLayoutConstraints that you don't understand, refer to the documentation for the UIView property translatesAutoresizingMaskIntoConstraints) ( "&lt;NSAutoresizingMaskLayoutConstraint:0x16083b60 h=-&amp;- v=-&amp;- UIView:0xa5a1d00.width == UIWindow:0xa09eee0.width&gt;", "&lt;NSLayoutConstraint:0xa5a2180 V:[UIView:0xa59f160]-(954)-| (Names: '|':UIView:0xa5a1d00 )&gt;", "&lt;NSLayoutConstraint:0xa5a2140 V:|-(0)-[UIView:0xa59f160] (Names: '|':UIView:0xa5a1d00 )&gt;", "&lt;NSAutoresizingMaskLayoutConstraint:0xa593340 h=--- v=--- H:[UIWindow:0xa09eee0(768)]&gt;" ) Will attempt to recover by breaking constraint &lt;NSLayoutConstraint:0xa5a2180 V:[UIView:0xa59f160]-(954)-| (Names: '|':UIView:0xa5a1d00 )&gt; Break on objc_exception_throw to catch this in the debugger. The methods in the UIConstraintBasedLayoutDebugging category on UIView listed in &lt;UIKit/UIView.h&gt; may also be helpful. </code></pre> <p>As you can see, there are memory addresses listed. Pasting those into the watch window's search bar doesn't reveal much. Also sifting though the thread and queue call stacks, I only get disassembled code on this breakpoint (exception breakpoint). </p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USVaporwareWolf
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POMapping memory address of unsatisfyable NSLayoutConstraints to UI controls
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POMapping memory address of unsatisfyable NSLayoutConstraints to UI controls
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POMapping memory address of unsatisfyable NSLayoutConstraints to UI controls
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload