Open Radar

 
Summary:
Copied from existing bug report found online:
https://openradar.appspot.com/24764160

When a Universal app is launched in Split View mode on iPad Mini 4, an Auto Layout Constraint violation is logged to the console.

Steps to Reproduce:
1- On an iPad Mini 4, open two apps in Split View mode (IMPORTANT: Make sure they're in Split View mode, NOT Slide Over mode).
2- Using XCode on OS X, create a new Universal Single View Application (or use the attached project).
3- Run the app on the iPad Mini 4.
4- Open the Console window in XCode, you'll see this:

2016-02-22 08:51:12.250 demo3[387:28313] 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. 
(
    "<NSLayoutConstraint:0x12d52d760 V:|-(20)-[UIInputSetContainerView:0x12d5283c0]   (Names: '|':UITextEffectsWindow:0x12d526930 )>",
    "<NSLayoutConstraint:0x12d621320 'UIInputWindowController-top' V:|-(0)-[UIInputSetContainerView:0x12d5283c0]   (Names: '|':UITextEffectsWindow:0x12d526930 )>"
)

Will attempt to recover by breaking constraint 
<NSLayoutConstraint:0x12d52d760 V:|-(20)-[UIInputSetContainerView:0x12d5283c0]   (Names: '|':UITextEffectsWindow:0x12d526930 )>

Make a symbolic breakpoint at UIViewAlertForUnsatisfiableConstraints to catch this in the debugger.
The methods in the UIConstraintBasedLayoutDebugging category on UIView listed in <UIKit/UIView.h> may also be helpful.


Expected Results:
No error should be displayed in the Console.


Actual Results:
The following is displayed in the Console:

2016-02-22 08:51:12.250 demo3[387:28313] 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. 
(
    "<NSLayoutConstraint:0x12d52d760 V:|-(20)-[UIInputSetContainerView:0x12d5283c0]   (Names: '|':UITextEffectsWindow:0x12d526930 )>",
    "<NSLayoutConstraint:0x12d621320 'UIInputWindowController-top' V:|-(0)-[UIInputSetContainerView:0x12d5283c0]   (Names: '|':UITextEffectsWindow:0x12d526930 )>"
)

Will attempt to recover by breaking constraint 
<NSLayoutConstraint:0x12d52d760 V:|-(20)-[UIInputSetContainerView:0x12d5283c0]   (Names: '|':UITextEffectsWindow:0x12d526930 )>

Make a symbolic breakpoint at UIViewAlertForUnsatisfiableConstraints to catch this in the debugger.
The methods in the UIConstraintBasedLayoutDebugging category on UIView listed in <UIKit/UIView.h> may also be helpful.




Version:
Version: iOS 9.2.1 (13D15), OS X 10.11.3, XCode 7.2.1 (7C1002)  Also present in beta: Version 7.3 beta (7D152p) and iOS 9.3 beta (13E5214d)

Notes:
 

Configuration:
Simulator

Attachments:
'test5.zip' was successfully uploaded.


Another similar bug report:
http://www.openradar.me/24426241