search

parley-messaging / ios-library

Parley iOS app library
MIT License
2 stars 2 forks source link

Constraints issues #97

Open igashev opened 1 month ago

igashev commented 1 month ago

Hi,

There seems to be some issues with satisfying constraints. I haven't seen any visual glitches apart from that the message are being choppy when scrolling which might very well be caused by the wrong constraints. Could you please take a look?

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:0x60000221ec10 UILayoutGuide:0x600003b11f80'UIViewSafeAreaLayoutGuide'.bottom == UIImageView:0x1767ddf60.bottom   (active)>",
    "<NSLayoutConstraint:0x6000022359a0 UIView:0x10e3c0420.bottom == UIImageView:0x1767ddf60.bottom   (active)>",
    "<NSLayoutConstraint:0x60000221c7d0 UIView:0x10e3c0420.top == UIImageView:0x1767ddf60.top   (active)>",
    "<NSLayoutConstraint:0x60000221fde0 UIImageView:0x1767ddf60.top == UILayoutGuide:0x600003b11f80'UIViewSafeAreaLayoutGuide'.top   (active)>",
    "<NSLayoutConstraint:0x60000221c550 Parley.ParleyMessageView:0x10e3bfa80.top == UIView:0x1767de160.top   (active)>",
    "<NSLayoutConstraint:0x60000221cb90 V:[UIView:0x1767de160]-(0)-|   (active, names: '|':Parley.ParleyMessageView:0x10e3bfa80 )>",
    "<NSLayoutConstraint:0x60000221f750 V:[Parley.ParleyMessageView:0x10e3bfa80]-(4)-|   (active, names: '|':UIView:0x10e3bf340 )>",
    "<NSLayoutConstraint:0x60000221c5a0 V:|-(4)-[Parley.ParleyMessageView:0x10e3bfa80]   (active, names: '|':UIView:0x10e3bf340 )>",
    "<NSLayoutConstraint:0x60000221f5c0 V:|-(0)-[UIView:0x10e3bf340]   (active, names: '|':UIStackView:0x10e3c1710 )>",
    "<NSLayoutConstraint:0x60000221cc30 V:[UICollectionView:0x10fafd600]-(0)-|   (active, names: '|':UIStackView:0x10e3c1710 )>",
    "<NSLayoutConstraint:0x60000221cff0 V:[UIView:0x10e3bf340]-(0)-[UICollectionView:0x10fafd600]   (active)>",
    "<NSLayoutConstraint:0x600002219860 V:[UIStackView:0x10e3c1710]-(0)-|   (active, names: '|':UITableViewCellContentView:0x17675bc10 )>",
    "<NSLayoutConstraint:0x600002218320 V:|-(0)-[UIStackView:0x10e3c1710]   (active, names: '|':UITableViewCellContentView:0x17675bc10 )>",
    "<NSLayoutConstraint:0x60000226b430 'UIView-Encapsulated-Layout-Height' UITableViewCellContentView:0x17675bc10.height == 0   (active)>",
    "<NSLayoutConstraint:0x60000221c8c0 'UIViewSafeAreaLayoutGuide-bottom' V:[UILayoutGuide:0x600003b11f80'UIViewSafeAreaLayoutGuide']-(0)-|   (active, names: '|':UIView:0x1767de160 )>",
    "<NSLayoutConstraint:0x60000221ce60 'UIViewSafeAreaLayoutGuide-top' V:|-(0)-[UILayoutGuide:0x600003b11f80'UIViewSafeAreaLayoutGuide']   (active, names: '|':UIView:0x1767de160 )>"
)

Will attempt to recover by breaking constraint 
<NSLayoutConstraint:0x6000022359a0 UIView:0x10e3c0420.bottom == UIImageView:0x1767ddf60.bottom   (active)>

Make a symbolic breakpoint at UIViewAlertForUnsatisfiableConstraints to catch this in the debugger.
The methods in the UIConstraintBasedLayoutDebugging category on UIView listed in <UIKitCore/UIView.h> may also be helpful.
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:0x60000221ec10 UILayoutGuide:0x600003b11f80'UIViewSafeAreaLayoutGuide'.bottom == UIImageView:0x1767ddf60.bottom   (active)>",
    "<NSLayoutConstraint:0x60000221fde0 UIImageView:0x1767ddf60.top == UILayoutGuide:0x600003b11f80'UIViewSafeAreaLayoutGuide'.top   (active)>",
    "<NSLayoutConstraint:0x60000221c550 Parley.ParleyMessageView:0x10e3bfa80.top == UIView:0x1767de160.top   (active)>",
    "<NSLayoutConstraint:0x60000221cb90 V:[UIView:0x1767de160]-(0)-|   (active, names: '|':Parley.ParleyMessageView:0x10e3bfa80 )>",
    "<NSLayoutConstraint:0x60000221f750 V:[Parley.ParleyMessageView:0x10e3bfa80]-(4)-|   (active, names: '|':UIView:0x10e3bf340 )>",
    "<NSLayoutConstraint:0x60000221c5a0 V:|-(4)-[Parley.ParleyMessageView:0x10e3bfa80]   (active, names: '|':UIView:0x10e3bf340 )>",
    "<NSLayoutConstraint:0x60000221f5c0 V:|-(0)-[UIView:0x10e3bf340]   (active, names: '|':UIStackView:0x10e3c1710 )>",
    "<NSLayoutConstraint:0x60000221cc30 V:[UICollectionView:0x10fafd600]-(0)-|   (active, names: '|':UIStackView:0x10e3c1710 )>",
    "<NSLayoutConstraint:0x60000221cff0 V:[UIView:0x10e3bf340]-(0)-[UICollectionView:0x10fafd600]   (active)>",
    "<NSLayoutConstraint:0x600002219860 V:[UIStackView:0x10e3c1710]-(0)-|   (active, names: '|':UITableViewCellContentView:0x17675bc10 )>",
    "<NSLayoutConstraint:0x600002218320 V:|-(0)-[UIStackView:0x10e3c1710]   (active, names: '|':UITableViewCellContentView:0x17675bc10 )>",
    "<NSLayoutConstraint:0x60000226b430 'UIView-Encapsulated-Layout-Height' UITableViewCellContentView:0x17675bc10.height == 0   (active)>",
    "<NSLayoutConstraint:0x60000221c8c0 'UIViewSafeAreaLayoutGuide-bottom' V:[UILayoutGuide:0x600003b11f80'UIViewSafeAreaLayoutGuide']-(0)-|   (active, names: '|':UIView:0x1767de160 )>",
    "<NSLayoutConstraint:0x60000221ce60 'UIViewSafeAreaLayoutGuide-top' V:|-(0)-[UILayoutGuide:0x600003b11f80'UIViewSafeAreaLayoutGuide']   (active, names: '|':UIView:0x1767de160 )>"
)

Will attempt to recover by breaking constraint 
<NSLayoutConstraint:0x60000221ec10 UILayoutGuide:0x600003b11f80'UIViewSafeAreaLayoutGuide'.bottom == UIImageView:0x1767ddf60.bottom   (active)>

Make a symbolic breakpoint at UIViewAlertForUnsatisfiableConstraints to catch this in the debugger.
The methods in the UIConstraintBasedLayoutDebugging category on UIView listed in <UIKitCore/UIView.h> may also be helpful.
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:0x60000221c550 Parley.ParleyMessageView:0x10e3bfa80.top == UIView:0x1767de160.top   (active)>",
    "<NSLayoutConstraint:0x60000221cb90 V:[UIView:0x1767de160]-(0)-|   (active, names: '|':Parley.ParleyMessageView:0x10e3bfa80 )>",
    "<NSLayoutConstraint:0x60000221f750 V:[Parley.ParleyMessageView:0x10e3bfa80]-(4)-|   (active, names: '|':UIView:0x10e3bf340 )>",
    "<NSLayoutConstraint:0x60000221c5a0 V:|-(4)-[Parley.ParleyMessageView:0x10e3bfa80]   (active, names: '|':UIView:0x10e3bf340 )>",
    "<NSLayoutConstraint:0x60000221f5c0 V:|-(0)-[UIView:0x10e3bf340]   (active, names: '|':UIStackView:0x10e3c1710 )>",
    "<NSLayoutConstraint:0x60000221cc30 V:[UICollectionView:0x10fafd600]-(0)-|   (active, names: '|':UIStackView:0x10e3c1710 )>",
    "<NSLayoutConstraint:0x60000221cff0 V:[UIView:0x10e3bf340]-(0)-[UICollectionView:0x10fafd600]   (active)>",
    "<NSLayoutConstraint:0x600002219860 V:[UIStackView:0x10e3c1710]-(0)-|   (active, names: '|':UITableViewCellContentView:0x17675bc10 )>",
    "<NSLayoutConstraint:0x600002218320 V:|-(0)-[UIStackView:0x10e3c1710]   (active, names: '|':UITableViewCellContentView:0x17675bc10 )>",
    "<NSLayoutConstraint:0x60000226b430 'UIView-Encapsulated-Layout-Height' UITableViewCellContentView:0x17675bc10.height == 0   (active)>"
)

Will attempt to recover by breaking constraint 
<NSLayoutConstraint:0x60000221c550 Parley.ParleyMessageView:0x10e3bfa80.top == UIView:0x1767de160.top   (active)>

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

Thanks for reporting. We'll take a look at it after the other incoming reports, since visually there are no issues seen yet that are caused by this. Ofcourse, we want to resolve it anyway in the end.

In case a visual issue is detected related to this, feel free to let us know.