Created
November 16, 2017 05:58
-
-
Save nadeemkhan/d4ef568050116be1b0218aaffb497a90 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2017-11-16 11:24:57.823498+0530 Viddiflash[6666:5492122] API error: <_UIKBCompatInputView: 0x104f292a0; frame = (0 0; 0 0); layer = <CALayer: 0x1c422c8a0>> returned 0 width, assuming UIViewNoIntrinsicMetric | |
2017-11-16 11:24:57.823700+0530 Viddiflash[6666:5492122] API error: <_UIKBCompatInputView: 0x104f292a0; frame = (0 0; 0 0); layer = <CALayer: 0x1c422c8a0>> returned 0 width, assuming UIViewNoIntrinsicMetric | |
2017-11-16 11:24:57.881862+0530 Viddiflash[6666:5492122] [LayoutConstraints] 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) | |
( | |
"<NSAutoresizingMaskLayoutConstraint:0x1c02896a0 h=-&- v=-&- UIToolbar:0x105826f40.width == _UIInputViewContent:0x1058781a0.width (active)>", | |
"<NSAutoresizingMaskLayoutConstraint:0x1c02897e0 h=--& v=--& _UIInputViewContent:0x1058781a0.width == 0 (active)>", | |
"<NSLayoutConstraint:0x1c0094c30 H:|-(8)-[_UIButtonBarStackView:0x1058c70b0] (active, names: '|':_UIToolbarContentView:0x1058c5af0 )>", | |
"<NSLayoutConstraint:0x1c0094e10 _UIButtonBarStackView:0x1058c70b0.trailing == _UIToolbarContentView:0x1058c5af0.trailing (active)>", | |
"<NSLayoutConstraint:0x1c0096440 _UIToolbarContentView:0x1058c5af0.trailing == UIToolbar:0x105826f40.trailing (active)>", | |
"<NSLayoutConstraint:0x1c00913f0 H:|-(0)-[_UIToolbarContentView:0x1058c5af0] (active, names: '|':UIToolbar:0x105826f40 )>", | |
"<NSLayoutConstraint:0x1c4287030 H:|-(>=5)-[_UIModernBarButton:0x104fb4550] (active, names: '|':_UIButtonBarButton:0x104fb3f10 )>", | |
"<NSLayoutConstraint:0x1c4287080 H:[_UIModernBarButton:0x104fb4550]-(>=5)-| (active, names: '|':_UIButtonBarButton:0x104fb3f10 )>", | |
"<NSLayoutConstraint:0x1c4287ee0 'UISV-canvas-connection' UILayoutGuide:0x1c01b2b40'UIViewLayoutMarginsGuide'.leading == _UIButtonBarButton:0x104fb2bd0.leading (active)>", | |
"<NSLayoutConstraint:0x1c4288250 'UISV-canvas-connection' UILayoutGuide:0x1c01b2b40'UIViewLayoutMarginsGuide'.trailing == _UIButtonBarButton:0x104fb4a60.trailing (active)>", | |
"<NSLayoutConstraint:0x1c42882a0 'UISV-spacing' H:[_UIButtonBarButton:0x104fb2bd0]-(0)-[UIView:0x104fb2e10] (active)>", | |
"<NSLayoutConstraint:0x1c42882f0 'UISV-spacing' H:[UIView:0x104fb2e10]-(0)-[_UIButtonBarButton:0x104fb3f10] (active)>", | |
"<NSLayoutConstraint:0x1c4288340 'UISV-spacing' H:[_UIButtonBarButton:0x104fb3f10]-(0)-[UIView:0x104fb4880] (active)>", | |
"<NSLayoutConstraint:0x1c4288390 'UISV-spacing' H:[UIView:0x104fb4880]-(0)-[_UIButtonBarButton:0x104fb4a60] (active)>", | |
"<NSLayoutConstraint:0x1c008fdc0 'UIView-leftMargin-guide-constraint' H:|-(0)-[UILayoutGuide:0x1c01b2b40'UIViewLayoutMarginsGuide'](LTR) (active, names: '|':_UIButtonBarStackView:0x1058c70b0 )>", | |
"<NSLayoutConstraint:0x1c0094ff0 'UIView-rightMargin-guide-constraint' H:[UILayoutGuide:0x1c01b2b40'UIViewLayoutMarginsGuide']-(0)-|(LTR) (active, names: '|':_UIButtonBarStackView:0x1058c70b0 )>" | |
) | |
Will attempt to recover by breaking constraint | |
<NSLayoutConstraint:0x1c4287080 H:[_UIModernBarButton:0x104fb4550]-(>=5)-| (active, names: '|':_UIButtonBarButton:0x104fb3f10 )> | |
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. | |
2017-11-16 11:24:57.887214+0530 Viddiflash[6666:5492122] [LayoutConstraints] 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) | |
( | |
"<NSAutoresizingMaskLayoutConstraint:0x1c02896a0 h=-&- v=-&- UIToolbar:0x105826f40.width == _UIInputViewContent:0x1058781a0.width (active)>", | |
"<NSAutoresizingMaskLayoutConstraint:0x1c02897e0 h=--& v=--& _UIInputViewContent:0x1058781a0.width == 0 (active)>", | |
"<NSLayoutConstraint:0x1c0094c30 H:|-(8)-[_UIButtonBarStackView:0x1058c70b0] (active, names: '|':_UIToolbarContentView:0x1058c5af0 )>", | |
"<NSLayoutConstraint:0x1c0094e10 _UIButtonBarStackView:0x1058c70b0.trailing == _UIToolbarContentView:0x1058c5af0.trailing (active)>", | |
"<NSLayoutConstraint:0x1c0096440 _UIToolbarContentView:0x1058c5af0.trailing == UIToolbar:0x105826f40.trailing (active)>", | |
"<NSLayoutConstraint:0x1c00913f0 H:|-(0)-[_UIToolbarContentView:0x1058c5af0] (active, names: '|':UIToolbar:0x105826f40 )>", | |
"<NSLayoutConstraint:0x1c4287ee0 'UISV-canvas-connection' UILayoutGuide:0x1c01b2b40'UIViewLayoutMarginsGuide'.leading == _UIButtonBarButton:0x104fb2bd0.leading (active)>", | |
"<NSLayoutConstraint:0x1c4288250 'UISV-canvas-connection' UILayoutGuide:0x1c01b2b40'UIViewLayoutMarginsGuide'.trailing == _UIButtonBarButton:0x104fb4a60.trailing (active)>", | |
"<NSLayoutConstraint:0x1c42882a0 'UISV-spacing' H:[_UIButtonBarButton:0x104fb2bd0]-(0)-[UIView:0x104fb2e10] (active)>", | |
"<NSLayoutConstraint:0x1c42882f0 'UISV-spacing' H:[UIView:0x104fb2e10]-(0)-[_UIButtonBarButton:0x104fb3f10] (active)>", | |
"<NSLayoutConstraint:0x1c4288340 'UISV-spacing' H:[_UIButtonBarButton:0x104fb3f10]-(0)-[UIView:0x104fb4880] (active)>", | |
"<NSLayoutConstraint:0x1c4288390 'UISV-spacing' H:[UIView:0x104fb4880]-(0)-[_UIButtonBarButton:0x104fb4a60] (active)>", | |
"<NSLayoutConstraint:0x1c008fdc0 'UIView-leftMargin-guide-constraint' H:|-(0)-[UILayoutGuide:0x1c01b2b40'UIViewLayoutMarginsGuide'](LTR) (active, names: '|':_UIButtonBarStackView:0x1058c70b0 )>", | |
"<NSLayoutConstraint:0x1c0094ff0 'UIView-rightMargin-guide-constraint' H:[UILayoutGuide:0x1c01b2b40'UIViewLayoutMarginsGuide']-(0)-|(LTR) (active, names: '|':_UIButtonBarStackView:0x1058c70b0 )>" | |
) | |
Will attempt to recover by breaking constraint | |
<NSLayoutConstraint:0x1c4288390 'UISV-spacing' H:[UIView:0x104fb4880]-(0)-[_UIButtonBarButton:0x104fb4a60] (active)> | |
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. | |
2017-11-16 11:24:57.889645+0530 Viddiflash[6666:5492122] [LayoutConstraints] 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) | |
( | |
"<NSAutoresizingMaskLayoutConstraint:0x1c02896a0 h=-&- v=-&- UIToolbar:0x105826f40.width == _UIInputViewContent:0x1058781a0.width (active)>", | |
"<NSAutoresizingMaskLayoutConstraint:0x1c02897e0 h=--& v=--& _UIInputViewContent:0x1058781a0.width == 0 (active)>", | |
"<NSLayoutConstraint:0x1c0094c30 H:|-(8)-[_UIButtonBarStackView:0x1058c70b0] (active, names: '|':_UIToolbarContentView:0x1058c5af0 )>", | |
"<NSLayoutConstraint:0x1c0094e10 _UIButtonBarStackView:0x1058c70b0.trailing == _UIToolbarContentView:0x1058c5af0.trailing (active)>", | |
"<NSLayoutConstraint:0x1c0096440 _UIToolbarContentView:0x1058c5af0.trailing == UIToolbar:0x105826f40.trailing (active)>", | |
"<NSLayoutConstraint:0x1c00913f0 H:|-(0)-[_UIToolbarContentView:0x1058c5af0] (active, names: '|':UIToolbar:0x105826f40 )>" | |
) | |
Will attempt to recover by breaking constraint | |
<NSLayoutConstraint:0x1c0094e10 _UIButtonBarStackView:0x1058c70b0.trailing == _UIToolbarContentView:0x1058c5af0.trailing (active)> | |
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. | |
2017-11-16 11:25:03.890177+0530 Viddiflash[6666:5492122] -[__NSDictionaryM stringByReplacingOccurrencesOfString:withString:]: unrecognized selector sent to instance 0x1c0625f00 | |
2017-11-16 11:25:03.892838+0530 Viddiflash[6666:5492122] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[__NSDictionaryM stringByReplacingOccurrencesOfString:withString:]: unrecognized selector sent to instance 0x1c0625f00' | |
*** First throw call stack: | |
(0x1828bfd38 0x181dd4528 0x1828cd1f8 0x1828c56e4 0x1827ab0dc 0x1046d5b70 0x1046d454c 0x1046d309c 0x1046d43f0 0x10478bb40 0x10478b434 0x104781738 0x10478e3e4 0x104781598 0x1832afa50 0x182868358 0x1828682d8 0x182867bb4 0x182865738 0x1827862d8 0x184617f84 0x18bd33880 0x1046d07ac 0x1822aa56c) | |
libc++abi.dylib: terminating with uncaught exception of type NSException | |
(lldb) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment