Unable to simultaneously satisfy constraints will attempt to recover by breaking constraint

Question

Below is the error message I receive in the debug area  It runs fine and nothing is wrong except that I receive this error  Would this prevent apple accepting the app  How do I fix it   2012-07-26 01 58 18 621 Rolo 33597 11303  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 0x887d630 h -- amp  v -- amp  V  UIButtonLabel 0x886ed80 19   gt          lt NSAutoresizingMaskLayoutConstraint 0x887d5f0 h -- amp  v -- amp  UIButtonLabel 0x886ed80 midY      37 5 gt          lt NSAutoresizingMaskLayoutConstraint 0x887b4b0 h -- amp  v -- amp  V  UIButtonLabel 0x72bb9b0 19   gt          lt NSAutoresizingMaskLayoutConstraint 0x887b470 h -- amp  v -- amp  UIButtonLabel 0x72bb9b0 midY    - 0 5 gt          lt NSLayoutConstraint 0x72bf860 V  UILabel 0x72bf7c0 17   gt          lt NSLayoutConstraint 0x72c2430 UILabel 0x72bfad0 top    UILabel 0x72bf7c0 top gt          lt NSLayoutConstraint 0x72c2370 UILabel 0x72c0270 top    UILabel 0x72bfad0 top gt          lt NSLayoutConstraint 0x72c22b0 V  UILabel 0x72bf7c0 - NSSpace 8  - UIButton 0x886efe0  gt          lt NSLayoutConstraint 0x72c15b0 V  UILabel 0x72c0270 - NSSpace 8  - UIRoundedRectButton 0x72bbc10  gt          lt NSLayoutConstraint 0x72c1570 UIRoundedRectButton 0x72bbc10 baseline    UIRoundedRectButton 0x7571170 baseline gt          lt NSLayoutConstraint 0x72c21f0 UIRoundedRectButton 0x7571170 top    UIButton 0x886efe0 top gt      Will attempt to recover by breaking constraint   lt NSLayoutConstraint 0x72bf860 V  UILabel 0x72bf7c0 17   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

User · Answer

For me the main reason of this problem was that I forgot to uncheck AutoLayout in the Xib editor  In fact  I did a lot of adjustments of the XIB in code

User · Answer

I am getting this same error  but only on a specific view  when I touch the first textfield  and then the next textfield down    I am writing in SwiftUI for iOS 13 4    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                   lt NSLayoutConstraint 0x2809b6760  assistantHeight  TUISystemInputAssistantView 0x105710da0 height    44    active  gt              lt NSLayoutConstraint 0x2809ccff0  assistantView bottom  TUISystemInputAssistantView 0x105710da0 bottom     UIKBCompatInputView 0x10525ae10 top    active  gt              lt NSLayoutConstraint 0x2809cccd0  assistantView top  V  - 0 - TUISystemInputAssistantView 0x105710da0     active  names      UIInputSetHostView 0x105215010   gt              lt NSLayoutConstraint 0x2809ca300  inputView top  V  - 0 -  UIKBCompatInputView 0x10525ae10     active  names      UIInputSetHostView 0x105215010   gt              Will attempt to recover by breaking constraint       lt NSLayoutConstraint 0x2809ccff0  assistantView bottom  TUISystemInputAssistantView 0x105710da0 bottom     UIKBCompatInputView 0x10525ae10 top    active  gt       Make a symbolic breakpoint at UIViewAlertForUnsatisfiableConstraints to catch this in the debugger      The methods in the UIConstraintBasedLayoutDebugging category on UIView listed in  lt UIKitCore UIView h gt  may also be helpful

User · Answer

The problem you re having is the NSAutoresizingMaskLayoutConstraints should not be in there  This is the old system of springs and struts  To get rid of it  run this method on each view that you re wanting to constrain    view setTranslatesAutoresizingMaskIntoConstraints NO

User · Answer

None of the foregoing answers is helpful in my situation   I am running XCode 10 1 and testing my app on the simulator for an  iPad  5th generation     The simulator is running iOS 12 1   I ve got a simple root view in my storyboard  with two UITextField subviews   There are no constraints being used in the storyboard at all   And I have no UIButtonBarView objects in the app or the storyboard   No messages get printed when the app launches and lays the root view out   None when the simulated device is rotated   But in the simulator  the moment I click on one of the text fields  the keyboard extension arises from the bottom of the screen  although not the full keyboard  which never seems to show up in the simulator   But the following is printed out on the terminal   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 0x6000034e7700 h -- amp  v -- amp  UIKeyboardAssistantBar 0x7f9c7d714af0 height    0    active  gt      lt NSLayoutConstraint 0x6000034aba20 V  - 0 -  UIUCBKBSelectionBackground 0x7f9c7d51ec70     active  names       UIButtonBarButton 0x7f9c7d51de40   gt      lt NSLayoutConstraint 0x6000034aba70  UIUCBKBSelectionBackground 0x7f9c7d51ec70 bottom     UIButtonBarButton 0x7f9c7d51de40 bottom    active  gt      lt NSLayoutConstraint 0x6000034fb3e0 V  - 0 -  UIButtonBarStackView 0x7f9c7d715880     active  names      UIKeyboardAssistantBar 0x7f9c7d714af0   gt      lt NSLayoutConstraint 0x6000034fb750 V   UIButtonBarStackView 0x7f9c7d715880 - 0 -     active  names      UIKeyboardAssistantBar 0x7f9c7d714af0   gt      lt NSLayoutConstraint 0x6000034abc00  UIButtonBar maximumAlignmentSize   UIButtonBarButton 0x7f9c7d51de40 height    UILayoutGuide 0x600002ef4e00 UIViewLayoutMarginsGuide  height    active  gt      lt NSLayoutConstraint 0x6000034d7cf0  UIView-bottomMargin-guide-constraint  V  UILayoutGuide 0x600002ef4e00 UIViewLayoutMarginsGuide  - 9 -     active  names       UIButtonBarStackView 0x7f9c7d715880   gt      lt NSLayoutConstraint 0x6000034d7c50  UIView-topMargin-guide-constraint  V  - 10 - UILayoutGuide 0x600002ef4e00 UIViewLayoutMarginsGuide      active  names       UIButtonBarStackView 0x7f9c7d715880   gt      Will attempt to recover by breaking constraint   lt NSLayoutConstraint 0x6000034aba70  UIUCBKBSelectionBackground 0x7f9c7d51ec70 bottom     UIButtonBarButton 0x7f9c7d51de40 bottom    active  gt   Make a symbolic breakpoint at UIViewAlertForUnsatisfiableConstraints to catch this in the debugger  The methods in the UIConstraintBasedLayoutDebugging category on UIView listed in  lt UIKitCore UIView h gt  may also be helpful    It certainly appears to me that all this has to do with nothing in my app  and everything to do with how Apple is creating its own keyboard view  even with my small extension declared to be combined with it   So the question remains  is there something I as an app developer am responsible for doing  on the presumption this is a bunch of stuff worth attending to  or is it just Apple s own problem bug   FWIW  this constraint problem message doesn t occur when simulating a newer iPad model  such as the iPad Pro 12 9-inch  3rd generation     But the message does show up when simulating an iPad Pro 9 7-inch    All claiming they re running iOS 12 1

User · Answer

I have followed SO questions and answers from each search query  But they all are related with specific one   At the basic  I mean before you are going to write down a format  may be a simple one  it will gives you a warnings   From iOS 8 0 by default views are size classes  Even if you disable size classes it will still contains some auto layout constraints   So if you are planning to set constrains via code using VFL  Then you must take care of one below line      Remove constraints if any   self view removeConstraints self view constraints     I had search a lot in SO  but the solution was lies in Apple Sample Code    So you must have to remove default constraints before planning to add new one

User · Answer

One thing to watch out for  at least this tripped me up  was that I was removing the constraint from the wrong view  The constraint I was trying to remove was not a child constraint of my view so when I did  myView removeConstraint theConstraint    it wasn t actually removing anything because I needed to call  myView superView removeConstraint theConstraint    since the constraint was technically sibling constraint of my view

User · Answer

Here is my experience and Solution  I didn t touched code   Select view  UILabel  UIImage etc  Editor   Pin    Select     to Superview Editor   Resolve Auto Layout Issues   Add Missing Constraints

User · Answer

I had quite a number of these exceptions thrown  the fastest and easiest way I found to solve them was to find unique values in the exceptions which I then searched for in the storyboard source code  This helped me to find the actual view s  and constraint s  causing the problem  I use meaningful userLabels on all of the views  which makes it a lot easier to track the constraints and views      So  using the above exceptions I would open the storyboard as  source code  in xcode  or another editor  and look for something I can find      lt NSLayoutConstraint 0x72bf860 V  UILabel 0x72bf7c0 17   gt        this looks like a vertical  V  constraint on a UILabel with a value of  17    Looking through the exceptions I also find    lt NSLayoutConstraint 0x72c22b0 V  UILabel 0x72bf7c0 - NSSpace 8  - UIButton 0x886efe0  gt    Which looks like the UILabel 0x72bf7c0  is close to a UIButton 0x886efe0  with some vertical spacing  8     That will hopefully be enough for me to find the specific views in the storyboard source code  probably by searching the text for  17  initially   or at least a few likely candidates  From there I should be able to actually figure out which views these are in the storyboard which will make it a lot easier to identify the problem  look for  duplicated  pinning or pinning that conflicts with size constraints

User · Answer

I was also getting the same issue of breaking constraints in the log  for a viewCircle in the xib  I almost tried everything listed above and nothing was working for me   Then I tried to change the priority of the Height constraint which was breaking in the log confirmed by adding an identifiers for the constraints on the xib enter image description here

User · Answer

swift 4  I just add this line in viewDidLoad and work fine with me   view removeConstraints view constraints

User · Answer

for UIView  view in  self view subviews          view setTranslatesAutoresizingMaskIntoConstraints NO       This helped me catch the view causing the problem

User · Answer

I had a hard time figuring out what constraints were causing this error  Here is a simpler way to do it    I m using Xcode 6 1 1    Command   A  to select all the UILabels  UIImages etc   Click Editor -  Pin    Select     to Superview again click Editor -  Resolve Auto Layout Issues -  Add Missing Constraints or Reset to Suggested Constraints  It depends on your case

User · Answer

Be careful  that you do not use more than one constraint in the same direction and type   For example  Vertical constraint for trailing   15 and another one is    10   Sometimes  Xcode creates some constraints you don t notice  You have to get rid of redundant constraints and the log warning will surely disappear     Additionaly  you can read and detect some certain reasons  directly from the log      NSLayoutConstraint 0xa338390 V  - 15 - UILabel 0xa331260     Names        UILabel 0xa330270      This we can read as problem in UILabel constraint  it is leading vertical constraint being 15pt long      NSLayoutConstraint 0x859ab20 H - 13 -  UIView 0x85a8fb0       This would be trailing horizontal constraint etc

User · Answer

I would recommend to debug and find which constraint is  the one you don t want   Suppose you have following issue     Always the problem is how to find following Constraints and Views   There are two solutions how to do this    DEBUG VIEW HIERARCHY  Do not recommend this way    Since you know where to find unexpected constraints  PBOUserWorkDayHeaderView  there is a way to do this fairly well  Lets find UIView and NSLayoutConstraint in red rectangles  Since we know their id in memory it is quite easy    Stop app using Debug View Hierarchy       Find the proper UIView       The next is to find NSLayoutConstraint we care about      As you can see  the memory pointers are the same  So we know what is going on now  Additionally you can find NSLayoutConstraint in view hierarchy  Since it is selected in View  it selected in Navigator also     If you need you may also print it on console using address pointer    lldb  po 0x17dce920  lt UIView  0x17dce920  frame    10 30  300 24 5   autoresize   RM BM  layer    lt CALayer  0x17dce9b0 gt  gt    You can do the same for every constraint the debugger will point to you -  Now you decide what to do with this     PRINT IT BETTER  I really recommend this way  this is of Xcode 7    set unique identifier for every constraint in your view        create simple extension for NSLayoutConstraint    SWIFT     extension NSLayoutConstraint        override public var description  String           let id   identifier               return  id    id   constant    constant     you may print whatever you want here           OBJECTIVE-C   interface NSLayoutConstraint  Description    end   implementation NSLayoutConstraint  Description   - NSString   description       return  NSString stringWithFormat   id      constant   f   self identifier  self constant       end    build it once again  and now you have more readable output for you       once you got your id you can simple tap it in your Find Navigator       and quickly find it      HOW TO SIMPLE FIX THAT CASE    try to change priority to 999 for broken constraint

User · Answer

Basically  you just have to remove that constraint from the associated view  For instance  if is the height constraint giving warning  just remove it from your view  it will not affect the view

User · Answer

use swift this code  view translatesAutoresizingMaskIntoConstraints   false

User · Answer

I had this issue because my  xib files were using autolayout   In the file inspector  first tab  Unticking  Use Autolayout  solved the problem

[ios] Unable to simultaneously satisfy constraints, will attempt to recover by breaking constraint

Examples related to ios

Examples related to objective-c

Examples related to debugging

Examples related to nslayoutconstraint