martinsben
commented
9 months ago Hi,
Thank you for your feedback, I can't reproduce the bug, can you describe all the steps and send me the log when the contact is created? Please.
Best regards.
Closed petervnv closed 5 months ago
martinsben
commented
9 months ago Hi,
Thank you for your feedback, I can't reproduce the bug, can you describe all the steps and send me the log when the contact is created? Please.
Best regards.
petervnv
commented
9 months ago Hi @martinsben,
Sure. Here are the steps: 1) Start a call to another SIP number. Hangup after successful call. 2) Go to history view and click on the SIP number 3) Click on add contact 4) It saves the new SIP contact but with the chat icon missing 5) Go to chat view and click on create new chat 6) Start searching for the SIP contact (using number or assigned name) 7) Screenshot as above where no results are displayed and thus no right arrow to continue the process
And here are the xcode logs from creating the new contact to trying to start a new chat
[Message] [SHARED] resetSharedCoreLastUpdateTime
Background Task 27 ("belle-sip transaction(0x600003a15fb0)"), was created over 30 seconds ago. In applications running in the background, this creates a risk of termination. Remember to call UIApplication.endBackgroundTask(_:) for your task in a timely manner to avoid this.
[Message] ( PhoneMainView.m:645 ) Change current view to HistoryListView
Calling -viewDidDisappear: directly on a view controller is not supported, and may result in out-of-order callbacks and other inconsistent behavior. Use the -beginAppearanceTransition:animated: and -endAppearanceTransition APIs on UIViewController to manually drive appearance callbacks instead. Make a symbolic breakpoint at UIViewControllerAlertForAppearanceCallbackMisuse to catch this in the debugger. View controller: <SideMenuView: 0x1078dc7f0>
[Message] [SHARED] resetSharedCoreLastUpdateTime
[Message] channel [0x1211d0000]: keep alive sent to [TLS://my.domain.com:5061]
[Message] Background task belle-sip recv channel started. Unknown remaining time since application is not fully in background.
[Message] channel [0x1211d0000]: starting recv background task with id=[27].
[Message] channel [0x1211d0000]: ending recv background task with id=[27].
[Message] Changing [client] [INVITE] transaction [0x600003a15fb0], from state [ACCEPTED] to [TERMINATED]
[Message] Client INVITE transaction [0x600003a15fb0] terminated
[Message] transaction [0x600003a15fb0]: ending transaction background task with id=[1b].
Couldn't find match for UIView => UIView => UIView => UIImageView
Couldn't find match for UIView => UIView => UIView => UIIconButton => UIButtonLabel
Couldn't find match for UIView => UIView => UIView => UIIconButton => UIButtonLabel
[Message] Start measurement of [Get call history 2.].
[Message] Duration of [Get call history 2.]: 1ms.
[Message] ( PhoneMainView.m:645 ) Change current view to HistoryDetailsView
[Message] Start measurement of [Get call history 2.].
[Message] Duration of [Get call history 2.]: 0ms.
[Message] Start measurement of [Get call history 2.].
[Message] Duration of [Get call history 2.]: 0ms.
[Message] ( PhoneMainView.m:645 ) Change current view to ContactsListView
Debuglog viewDidLoad
Debuglog changeView
[Message] (tsListTableView.m:257 ) Load search contact list
Debuglog viewWillAppear
Debuglog changeView
Debuglog viewDidAppear
-[RTIInputSystemClient remoteTextInputSessionWithID:performInputOperation:] perform input operation requires a valid sessionID
[Message] [Magic Search] Found 0 results in friends
[Message] [Magic Search] Found 0 results after sorting, aggregation & removing duplicates
[Message] Contact magic search -- filter = -- 0 contact founds
[Message] Changing [client] [INVITE] transaction [0x600003a2ecb0], from state [ACCEPTED] to [TERMINATED]
[Message] Client INVITE transaction [0x600003a2ecb0] terminated
[Message] Destroying op [0x10d9b3a00] of type [SalOpCall]
[Message] Transaction [0x6000077b7480] deleted
[Message] transaction [0x600003a2ecb0]: ending transaction background task with id=[21].
[Message] Transaction [0x600003a2ecb0] deleted
-[RTIInputSystemClient remoteTextInputSessionWithID:performInputOperation:] perform input operation requires a valid sessionID
Couldn't find match for UIView => UIView => UIView => UIImageView
Couldn't find match for UIView => UIView => UIView => UIIconButton => UIButtonLabel
Couldn't find match for UIView => UIView => UIView => UIIconButton => UIButtonLabel
[Message] ( PhoneMainView.m:645 ) Change current view to ContactDetailsView
[Warning] Skipping vCard validation
[Warning] Trying to set an invalid vCard (no fullname) to friend, aborting
[Error] linphone_friend_list_add_friend(): invalid friend, no vCard, SIP URI or phone number
[Message] (FastAddressBook.m:124 ) Parsing contact with username : 1002 and service : SIP
[Warning] (etailsTableView.m:97 ) Cannot add entry '' in section 4, skipping
[Warning] (etailsTableView.m:97 ) Cannot add entry '' in section 5, skipping
-[RTIInputSystemClient remoteTextInputSessionWithID:performInputOperation:] perform input operation requires a valid sessionID
[Message] [SHARED] resetSharedCoreLastUpdateTime
[Warning] Skipping vCard validation
48135 HALC_ProxyIOContext.cpp:1328 HALC_ProxyIOContext::IOWorkLoop: skipping cycle due to overload
Error for queryMetaDataSync: 2
Error for queryMetaDataSync: 2
48135 HALC_ProxyIOContext.cpp:1328 HALC_ProxyIOContext::IOWorkLoop: skipping cycle due to overload
[Message] Updating friend list [0x600003925ee0](_default) subscriptions
[Message] Friend list [0x600003925ee0] subscription update skipped since subscriptions not enabled yet
[Debug] (FastAddressBook.m:252 ) address book has changed
Success 1
[Debug] (FastAddressBook.m:218 ) CNContactStore authorization granted
This method should not be called on the main thread as it may lead to UI unresponsiveness.
[Message] (FastAddressBook.m:124 ) Parsing contact with username : 1002 and service : SIP
[Warning] Skipping vCard validation
[Message] Updating friend list [0x600003925ee0](_default) subscriptions
[Message] Friend list [0x600003925ee0] subscription update skipped since subscriptions not enabled yet
[Debug] (FastAddressBook.m:538 ) dumpContactsDisplayNamesToUserDefaults
[Debug] (FastAddressBook.m:559 ) add sip:5556106679@my.domain.com to userdefaults
[Debug] (FastAddressBook.m:559 ) add sip:8885555512@my.domain.com to userdefaults
[Debug] (FastAddressBook.m:559 ) add sip:5554787672@my.domain.com to userdefaults
[Debug] (FastAddressBook.m:559 ) add sip:4085555270@my.domain.com to userdefaults
[Debug] (FastAddressBook.m:559 ) add sip:4155553695@my.domain.com to userdefaults
[Debug] (FastAddressBook.m:559 ) add sip:4085553514@my.domain.com to userdefaults
[Debug] (FastAddressBook.m:559 ) add sip:7075551854@my.domain.com to userdefaults
[Debug] (FastAddressBook.m:559 ) add sip:5555648583@my.domain.com to userdefaults
[Debug] (FastAddressBook.m:559 ) add sip:8885551212@my.domain.com to userdefaults
[Debug] (FastAddressBook.m:559 ) add sip:5555228243@my.domain.com to userdefaults
[Debug] (FastAddressBook.m:559 ) add sip:5557664823@my.domain.com to userdefaults
[Debug] (FastAddressBook.m:559 ) add sip:1002@my.domain.com to userdefaults
[Debug] (FastAddressBook.m:252 ) address book has changed
[Message] [SHARED] resetSharedCoreLastUpdateTime
[Message] ( PhoneMainView.m:645 ) Change current view to HistoryListView
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
[Message] ( PhoneMainView.m:645 ) Change current view to DialerView
[Message] [SHARED] resetSharedCoreLastUpdateTime
[Message] channel [0x1211d0000]: keep alive sent to [TLS://my.domain.com:5061]
[Message] Background task belle-sip recv channel started. Unknown remaining time since application is not fully in background.
[Message] channel [0x1211d0000]: starting recv background task with id=[28].
[Message] channel [0x1211d0000]: ending recv background task with id=[28].
[Message] ( PhoneMainView.m:645 ) Change current view to ChatsListView
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
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.
(
"<SnapKit.LayoutConstraint:0x600006667c60@UIVIewExtensions.swift#83 UIView:0x123224f00.height == 66.0>",
"<SnapKit.LayoutConstraint:0x6000066f8ae0@UIVIewExtensions.swift#68 linphoneapp.CallControlButton:0x123227330.height == 50.0>",
"<SnapKit.LayoutConstraint:0x6000066f7e40@UIVIewExtensions.swift#203 linphoneapp.CallControlButton:0x123227330.top == UIView:0x123224f00.top>",
"<SnapKit.LayoutConstraint:0x600006700000@UIVIewExtensions.swift#203 linphoneapp.CallControlButton:0x123227330.bottom == UIView:0x123224f00.bottom>"
)
Will attempt to recover by breaking constraint
<SnapKit.LayoutConstraint:0x6000066f8ae0@UIVIewExtensions.swift#68 linphoneapp.CallControlButton:0x123227330.height == 50.0>
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.
(
"<SnapKit.LayoutConstraint:0x600006667c60@UIVIewExtensions.swift#83 UIView:0x123224f00.height == 66.0>",
"<SnapKit.LayoutConstraint:0x6000066edb00@UIVIewExtensions.swift#68 linphoneapp.CallControlButton:0x1230695a0.height == 50.0>",
"<SnapKit.LayoutConstraint:0x6000066fe280@UIVIewExtensions.swift#203 linphoneapp.CallControlButton:0x1230695a0.top == UIView:0x123224f00.top>",
"<SnapKit.LayoutConstraint:0x6000066fe2e0@UIVIewExtensions.swift#203 linphoneapp.CallControlButton:0x1230695a0.bottom == UIView:0x123224f00.bottom>"
)
Will attempt to recover by breaking constraint
<SnapKit.LayoutConstraint:0x6000066edb00@UIVIewExtensions.swift#68 linphoneapp.CallControlButton:0x1230695a0.height == 50.0>
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.
(
"<SnapKit.LayoutConstraint:0x600006667c60@UIVIewExtensions.swift#83 UIView:0x123224f00.height == 66.0>",
"<SnapKit.LayoutConstraint:0x6000066fb300@UIVIewExtensions.swift#68 linphoneapp.CallControlButton:0x12306f020.height == 50.0>",
"<SnapKit.LayoutConstraint:0x6000066fe520@UIVIewExtensions.swift#203 linphoneapp.CallControlButton:0x12306f020.top == UIView:0x123224f00.top>",
"<SnapKit.LayoutConstraint:0x6000066fe580@UIVIewExtensions.swift#203 linphoneapp.CallControlButton:0x12306f020.bottom == UIView:0x123224f00.bottom>"
)
Will attempt to recover by breaking constraint
<SnapKit.LayoutConstraint:0x6000066fb300@UIVIewExtensions.swift#68 linphoneapp.CallControlButton:0x12306f020.height == 50.0>
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.
(
"<SnapKit.LayoutConstraint:0x600006667c60@UIVIewExtensions.swift#83 UIView:0x123224f00.height == 66.0>",
"<SnapKit.LayoutConstraint:0x6000066fbde0@UIVIewExtensions.swift#68 linphoneapp.CallControlButton:0x1230759d0.height == 50.0>",
"<SnapKit.LayoutConstraint:0x6000067001e0@UIVIewExtensions.swift#203 linphoneapp.CallControlButton:0x1230759d0.top == UIView:0x123224f00.top>",
"<SnapKit.LayoutConstraint:0x600006700240@UIVIewExtensions.swift#203 linphoneapp.CallControlButton:0x1230759d0.bottom == UIView:0x123224f00.bottom>"
)
Will attempt to recover by breaking constraint
<SnapKit.LayoutConstraint:0x6000066fbde0@UIVIewExtensions.swift#68 linphoneapp.CallControlButton:0x1230759d0.height == 50.0>
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.
(
"<SnapKit.LayoutConstraint:0x600006667c60@UIVIewExtensions.swift#83 UIView:0x123224f00.height == 66.0>",
"<SnapKit.LayoutConstraint:0x6000066f7c60@UIVIewExtensions.swift#68 linphoneapp.CallControlButton:0x11dc97fc0.height == 50.0>",
"<SnapKit.LayoutConstraint:0x6000066fe820@UIVIewExtensions.swift#203 linphoneapp.CallControlButton:0x11dc97fc0.top == UIView:0x123224f00.top>",
"<SnapKit.LayoutConstraint:0x6000066fe880@UIVIewExtensions.swift#203 linphoneapp.CallControlButton:0x11dc97fc0.bottom == UIView:0x123224f00.bottom>"
)
Will attempt to recover by breaking constraint
<SnapKit.LayoutConstraint:0x6000066f7c60@UIVIewExtensions.swift#68 linphoneapp.CallControlButton:0x11dc97fc0.height == 50.0>
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.
(
"<SnapKit.LayoutConstraint:0x600006667c60@UIVIewExtensions.swift#83 UIView:0x123224f00.height == 66.0>",
"<SnapKit.LayoutConstraint:0x6000066fc840@UIVIewExtensions.swift#68 linphoneapp.CallControlButton:0x12322d470.height == 50.0>",
"<SnapKit.LayoutConstraint:0x6000066fea00@UIVIewExtensions.swift#203 linphoneapp.CallControlButton:0x12322d470.top == UIView:0x123224f00.top>",
"<SnapKit.LayoutConstraint:0x6000066fea60@UIVIewExtensions.swift#203 linphoneapp.CallControlButton:0x12322d470.bottom == UIView:0x123224f00.bottom>"
)
Will attempt to recover by breaking constraint
<SnapKit.LayoutConstraint:0x6000066fc840@UIVIewExtensions.swift#68 linphoneapp.CallControlButton:0x12322d470.height == 50.0>
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.
(
"<SnapKit.LayoutConstraint:0x6000066f7c00@UIVIewExtensions.swift#67 linphoneapp.CallControlButton:0x11dc97fc0.width == 50.0>",
"<SnapKit.LayoutConstraint:0x600006700300@UIVIewExtensions.swift#67 linphoneapp.CallControlButton:0x11dc97fc0.width == 34.0>"
)
Will attempt to recover by breaking constraint
<SnapKit.LayoutConstraint:0x6000066f7c00@UIVIewExtensions.swift#67 linphoneapp.CallControlButton:0x11dc97fc0.width == 50.0>
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.
(
"<SnapKit.LayoutConstraint:0x600006667c60@UIVIewExtensions.swift#83 UIView:0x123224f00.height == 66.0>",
"<SnapKit.LayoutConstraint:0x6000066fe820@UIVIewExtensions.swift#203 linphoneapp.CallControlButton:0x11dc97fc0.top == UIView:0x123224f00.top>",
"<SnapKit.LayoutConstraint:0x6000066fe880@UIVIewExtensions.swift#203 linphoneapp.CallControlButton:0x11dc97fc0.bottom == UIView:0x123224f00.bottom>",
"<SnapKit.LayoutConstraint:0x600006700360@UIVIewExtensions.swift#68 linphoneapp.CallControlButton:0x11dc97fc0.height == 34.0>"
)
Will attempt to recover by breaking constraint
<SnapKit.LayoutConstraint:0x600006700360@UIVIewExtensions.swift#68 linphoneapp.CallControlButton:0x11dc97fc0.height == 34.0>
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.
(
"<SnapKit.LayoutConstraint:0x600006667c60@UIVIewExtensions.swift#83 UIView:0x123224f00.height == 66.0>",
"<SnapKit.LayoutConstraint:0x6000066fdb60@UIVIewExtensions.swift#68 linphoneapp.CallControlButton:0x1232303e0.height == 50.0>",
"<SnapKit.LayoutConstraint:0x6000066fed60@UIVIewExtensions.swift#203 linphoneapp.CallControlButton:0x1232303e0.top == UIView:0x123224f00.top>",
"<SnapKit.LayoutConstraint:0x6000066fedc0@UIVIewExtensions.swift#203 linphoneapp.CallControlButton:0x1232303e0.bottom == UIView:0x123224f00.bottom>"
)
Will attempt to recover by breaking constraint
<SnapKit.LayoutConstraint:0x6000066fdb60@UIVIewExtensions.swift#68 linphoneapp.CallControlButton:0x1232303e0.height == 50.0>
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.
(
"<SnapKit.LayoutConstraint:0x600006667c60@UIVIewExtensions.swift#83 UIView:0x123224f00.height == 66.0>",
"<SnapKit.LayoutConstraint:0x6000066f9e00@UIVIewExtensions.swift#68 linphoneapp.CallControlButton:0x1232367b0.height == 50.0>",
"<SnapKit.LayoutConstraint:0x6000066fef40@UIVIewExtensions.swift#203 linphoneapp.CallControlButton:0x1232367b0.top == UIView:0x123224f00.top>",
"<SnapKit.LayoutConstraint:0x6000066fefa0@UIVIewExtensions.swift#203 linphoneapp.CallControlButton:0x1232367b0.bottom == UIView:0x123224f00.bottom>"
)
Will attempt to recover by breaking constraint
<SnapKit.LayoutConstraint:0x6000066f9e00@UIVIewExtensions.swift#68 linphoneapp.CallControlButton:0x1232367b0.height == 50.0>
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.
(
"<SnapKit.LayoutConstraint:0x600006701320@UIVIewExtensions.swift#238 linphoneapp.StyledLabel:0x123050750.top == UIView:0x1230505c0.top + 10.0>",
"<SnapKit.LayoutConstraint:0x6000067014a0@UIVIewExtensions.swift#203 linphoneapp.StyledLabel:0x123050750.top == UIView:0x1230505c0.top>"
)
Will attempt to recover by breaking constraint
<SnapKit.LayoutConstraint:0x600006701320@UIVIewExtensions.swift#238 linphoneapp.StyledLabel:0x123050750.top == UIView:0x1230505c0.top + 10.0>
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.
(
"<SnapKit.LayoutConstraint:0x6000066ff120@UIVIewExtensions.swift#274 UIStackView:0x123224d50.bottom == UIView:0x123222390.bottom - 10.0>",
"<SnapKit.LayoutConstraint:0x6000066ff660@UIVIewExtensions.swift#203 UIStackView:0x123224d50.bottom == UIView:0x123222390.bottom>"
)
Will attempt to recover by breaking constraint
<SnapKit.LayoutConstraint:0x6000066ff660@UIVIewExtensions.swift#203 UIStackView:0x123224d50.bottom == UIView:0x123222390.bottom>
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.
(
"<SnapKit.LayoutConstraint:0x6000066f6940@UIVIewExtensions.swift#83 UIView:0x123058950.height == 66.0>",
"<SnapKit.LayoutConstraint:0x6000066e7840@UIVIewExtensions.swift#68 linphoneapp.CallControlButton:0x123058c70.height == 40.0>",
"<SnapKit.LayoutConstraint:0x6000066e4fc0@UIVIewExtensions.swift#203 linphoneapp.CallControlButton:0x123058c70.top == UIView:0x123058950.top>",
"<SnapKit.LayoutConstraint:0x600006667900@UIVIewExtensions.swift#203 linphoneapp.CallControlButton:0x123058c70.bottom == UIView:0x123058950.bottom>"
)
Will attempt to recover by breaking constraint
<SnapKit.LayoutConstraint:0x6000066e7840@UIVIewExtensions.swift#68 linphoneapp.CallControlButton:0x123058c70.height == 40.0>
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.
(
"<SnapKit.LayoutConstraint:0x6000066f6940@UIVIewExtensions.swift#83 UIView:0x123058950.height == 66.0>",
"<SnapKit.LayoutConstraint:0x6000066d73c0@UIVIewExtensions.swift#68 linphoneapp.CallControlButton:0x12305f690.height == 40.0>",
"<SnapKit.LayoutConstraint:0x600006704120@UIVIewExtensions.swift#203 linphoneapp.CallControlButton:0x12305f690.top == UIView:0x123058950.top>",
"<SnapKit.LayoutConstraint:0x600006704180@UIVIewExtensions.swift#203 linphoneapp.CallControlButton:0x12305f690.bottom == UIView:0x123058950.bottom>"
)
Will attempt to recover by breaking constraint
<SnapKit.LayoutConstraint:0x6000066d73c0@UIVIewExtensions.swift#68 linphoneapp.CallControlButton:0x12305f690.height == 40.0>
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.
(
"<SnapKit.LayoutConstraint:0x6000066f6940@UIVIewExtensions.swift#83 UIView:0x123058950.height == 66.0>",
"<SnapKit.LayoutConstraint:0x6000066c7420@UIVIewExtensions.swift#68 linphoneapp.CallControlButton:0x1230649f0.height == 40.0>",
"<SnapKit.LayoutConstraint:0x600006704360@UIVIewExtensions.swift#203 linphoneapp.CallControlButton:0x1230649f0.top == UIView:0x123058950.top>",
"<SnapKit.LayoutConstraint:0x6000067043c0@UIVIewExtensions.swift#203 linphoneapp.CallControlButton:0x1230649f0.bottom == UIView:0x123058950.bottom>"
)
Will attempt to recover by breaking constraint
<SnapKit.LayoutConstraint:0x6000066c7420@UIVIewExtensions.swift#68 linphoneapp.CallControlButton:0x1230649f0.height == 40.0>
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.
(
"<SnapKit.LayoutConstraint:0x6000066f0360@UIVIewExtensions.swift#68 linphoneapp.CallControlButton:0x1224fcca0.height == 50.0>",
"<SnapKit.LayoutConstraint:0x6000066f3240@UIVIewExtensions.swift#68 linphoneapp.CallControlButton:0x123211d70.height == 50.0>",
"<SnapKit.LayoutConstraint:0x6000066f4f00@UIVIewExtensions.swift#203 linphoneapp.CallControlButton:0x123211d70.top == UIStackView:0x1232172b0.top>",
"<SnapKit.LayoutConstraint:0x6000066f4f60@UIVIewExtensions.swift#203 linphoneapp.CallControlButton:0x123211d70.bottom == UIStackView:0x1232172b0.bottom>",
"<SnapKit.LayoutConstraint:0x6000066f4a80@UIVIewExtensions.swift#156 UIStackView:0x1232172b0.top == UIView:0x123216800.top + 10.0>",
"<SnapKit.LayoutConstraint:0x6000066f4a20@UIVIewExtensions.swift#157 UIStackView:0x1232172b0.bottom == UIView:0x123216800.bottom - 10.0>",
"<SnapKit.LayoutConstraint:0x6000066f4240@UIVIewExtensions.swift#203 linphoneapp.CallControlButton:0x1224fcca0.top == linphoneapp.MessageView:0x1224fca80.top>",
"<SnapKit.LayoutConstraint:0x6000066f42a0@UIVIewExtensions.swift#203 linphoneapp.CallControlButton:0x1224fcca0.bottom == linphoneapp.MessageView:0x1224fca80.bottom>",
"<SnapKit.LayoutConstraint:0x6000066f4840@UIVIewExtensions.swift#203 UIView:0x123216800.top == linphoneapp.MessageView:0x1224fca80.top>",
"<SnapKit.LayoutConstraint:0x6000066f4900@UIVIewExtensions.swift#203 UIView:0x123216800.bottom == linphoneapp.MessageView:0x1224fca80.bottom>"
)
Will attempt to recover by breaking constraint
<SnapKit.LayoutConstraint:0x6000066f3240@UIVIewExtensions.swift#68 linphoneapp.CallControlButton:0x123211d70.height == 50.0>
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.
(
"<SnapKit.LayoutConstraint:0x6000066f0360@UIVIewExtensions.swift#68 linphoneapp.CallControlButton:0x1224fcca0.height == 50.0>",
"<SnapKit.LayoutConstraint:0x6000066f4240@UIVIewExtensions.swift#203 linphoneapp.CallControlButton:0x1224fcca0.top == linphoneapp.MessageView:0x1224fca80.top>",
"<SnapKit.LayoutConstraint:0x6000066f42a0@UIVIewExtensions.swift#203 linphoneapp.CallControlButton:0x1224fcca0.bottom == linphoneapp.MessageView:0x1224fca80.bottom>",
"<SnapKit.LayoutConstraint:0x6000067015c0@UIVIewExtensions.swift#83 linphoneapp.MessageView:0x1224fca80.height == 57.5>"
)
Will attempt to recover by breaking constraint
<SnapKit.LayoutConstraint:0x6000066f0360@UIVIewExtensions.swift#68 linphoneapp.CallControlButton:0x1224fcca0.height == 50.0>
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.
(
"<SnapKit.LayoutConstraint:0x6000066f1380@UIVIewExtensions.swift#68 linphoneapp.CallControlButton:0x123206ae0.height == 50.0>",
"<SnapKit.LayoutConstraint:0x6000066f4360@UIVIewExtensions.swift#203 linphoneapp.CallControlButton:0x123206ae0.top == linphoneapp.MessageView:0x1224fca80.top>",
"<SnapKit.LayoutConstraint:0x6000066f43c0@UIVIewExtensions.swift#203 linphoneapp.CallControlButton:0x123206ae0.bottom == linphoneapp.MessageView:0x1224fca80.bottom>",
"<SnapKit.LayoutConstraint:0x6000067015c0@UIVIewExtensions.swift#83 linphoneapp.MessageView:0x1224fca80.height == 57.5>"
)
Will attempt to recover by breaking constraint
<SnapKit.LayoutConstraint:0x6000066f1380@UIVIewExtensions.swift#68 linphoneapp.CallControlButton:0x123206ae0.height == 50.0>
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.
(
"<SnapKit.LayoutConstraint:0x6000066f23a0@UIVIewExtensions.swift#68 linphoneapp.CallControlButton:0x12320c200.height == 50.0>",
"<SnapKit.LayoutConstraint:0x6000066f46c0@UIVIewExtensions.swift#203 linphoneapp.CallControlButton:0x12320c200.top == linphoneapp.MessageView:0x1224fca80.top>",
"<SnapKit.LayoutConstraint:0x6000066f4720@UIVIewExtensions.swift#203 linphoneapp.CallControlButton:0x12320c200.bottom == linphoneapp.MessageView:0x1224fca80.bottom>",
"<SnapKit.LayoutConstraint:0x6000067015c0@UIVIewExtensions.swift#83 linphoneapp.MessageView:0x1224fca80.height == 57.5>"
)
Will attempt to recover by breaking constraint
<SnapKit.LayoutConstraint:0x6000066f23a0@UIVIewExtensions.swift#68 linphoneapp.CallControlButton:0x12320c200.height == 50.0>
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:0x6000024b83c0 UIStackView:0x123224ba0.centerY == UIView:0x12307cd40.centerY (active)>",
"<SnapKit.LayoutConstraint:0x600006700d80@UIVIewExtensions.swift#238 UIStackView:0x123224ba0.top == UIView:0x12307cd40.top>",
"<SnapKit.LayoutConstraint:0x600006700f60@UIVIewExtensions.swift#274 UIStackView:0x123224ba0.bottom == UIView:0x12307cd40.bottom - 17.0>"
)
Will attempt to recover by breaking constraint
<NSLayoutConstraint:0x6000024b83c0 UIStackView:0x123224ba0.centerY == UIView:0x12307cd40.centerY (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.
[Message] ( PhoneMainView.m:645 ) Change current view to ChatConversationCreateView
[Message] [Magic Search] Cancelling :
[Message] [Magic Search] Found 1 results in friends
[Message] [Magic Search] Found 1 results in call logs
[Message] [Magic Search] Found 0 results in chat rooms
[Message] Start measurement of [Get conference infos.].
[Message] Duration of [Get conference infos.]: 0ms.
[Message] [Magic Search] Found 0 results in conferences info
[Message] [Magic Search] Found 1 results after sorting, aggregation & removing duplicates
[Message] Contact magic search -- filter = -- 1 contact founds
-[RTIInputSystemClient remoteTextInputSessionWithID:performInputOperation:] perform input operation requires a valid sessionID
[Message] [SHARED] resetSharedCoreLastUpdateTime
[Message] [Magic Search] Found 1 results in friends
[Message] [Magic Search] Found 1 results in call logs
[Message] [Magic Search] Found 0 results in chat rooms
[Message] Start measurement of [Get conference infos.].
[Message] Duration of [Get conference infos.]: 0ms.
[Message] [Magic Search] Found 0 results in conferences info
[Message] [Magic Search] Found 1 results after sorting, aggregation & removing duplicates
[Message] Contact magic search -- filter = 1 -- 2 contact founds
Warning once only: UITableView was told to layout its visible cells and other contents without being in the view hierarchy (the table view or one of its superviews has not been added to a window). This may cause bugs by forcing views inside the table view to load and perform layout without accurate information (e.g. table view bounds, trait collection, layout margins, safe area insets, etc), and will also cause unnecessary performance overhead due to extra layout passes. Make a symbolic breakpoint at UITableViewAlertForLayoutOutsideViewHierarchy to catch this in the debugger and see what caused this to occur, so you can avoid this action altogether if possible, or defer it until the table view has been added to a window. Table view: <UITableView: 0x10e073200; frame = (0 122; 393 599); clipsToBounds = YES; autoresize = W+H+BM; gestureRecognizers = <NSArray: 0x60000156d710>; backgroundColor = <UIDynamicSystemColor: 0x600001857fc0; name = tableBackgroundColor>; layer = <CALayer: 0x600000719700>; contentOffset: {0, 0}; contentSize: {393, 132}; adjustedContentInset: {0, 0, 0, 0}; dataSource: <ContactsListTableView: 0x10612e000>>
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
fopen failed for data file: errno = 2 (No such file or directory)
Errors found! Invalidating cache...
fopen failed for data file: errno = 2 (No such file or directory)
Errors found! Invalidating cache...
[Message] [Magic Search] Found 1 results in friends
[Message] [Magic Search] Found 1 results in call logs
[Message] [Magic Search] Found 0 results in chat rooms
[Message] Start measurement of [Get conference infos.].
[Message] Duration of [Get conference infos.]: 0ms.
[Message] [Magic Search] Found 0 results in conferences info
[Message] [Magic Search] Found 1 results after sorting, aggregation & removing duplicates
[Message] Contact magic search -- filter = 10 -- 2 contact founds
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
[Message] [Magic Search] Found 1 results in friends
[Message] [Magic Search] Found 1 results in call logs
[Message] [Magic Search] Found 0 results in chat rooms
[Message] Start measurement of [Get conference infos.].
[Message] Duration of [Get conference infos.]: 0ms.
[Message] [Magic Search] Found 0 results in conferences info
[Message] [Magic Search] Found 1 results after sorting, aggregation & removing duplicates
[Message] Contact magic search -- filter = 100 -- 2 contact founds
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
[Message] [Magic Search] Found 1 results in friends
[Message] [Magic Search] Found 1 results in call logs
[Message] [Magic Search] Found 0 results in chat rooms
[Message] Start measurement of [Get conference infos.].
[Message] Duration of [Get conference infos.]: 0ms.
[Message] [Magic Search] Found 0 results in conferences info
[Message] [Magic Search] Found 1 results after sorting, aggregation & removing duplicates
[Message] Contact magic search -- filter = 1002 -- 2 contact founds
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
-[RTIInputSystemClient remoteTextInputSessionWithID:performInputOperation:] perform input operation requires a valid sessionID
[Message] [Magic Search] Found 1 results in friends
[Message] [Magic Search] Found 1 results in call logs
[Message] [Magic Search] Found 0 results in chat rooms
[Message] Start measurement of [Get conference infos.].
[Message] Duration of [Get conference infos.]: 0ms.
[Message] [Magic Search] Found 0 results in conferences info
[Message] [Magic Search] Found 1 results after sorting, aggregation & removing duplicates
[Message] Contact magic search -- filter = -- 1 contact founds
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
[Message] [Magic Search] Found 1 results in friends
[Message] [Magic Search] Found 0 results in call logs
[Message] [Magic Search] Found 0 results in chat rooms
[Message] Start measurement of [Get conference infos.].
[Message] Duration of [Get conference infos.]: 0ms.
[Message] [Magic Search] Found 0 results in conferences info
[Message] [Magic Search] Found 1 results after sorting, aggregation & removing duplicates
[Message] Contact magic search -- filter = A -- 2 contact founds
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
[Message] [Magic Search] Found 1 results in friends
[Message] [Magic Search] Found 0 results in call logs
[Message] [Magic Search] Found 0 results in chat rooms
[Message] Start measurement of [Get conference infos.].
[Message] Duration of [Get conference infos.]: 0ms.
[Message] [Magic Search] Found 0 results in conferences info
[Message] [Magic Search] Found 1 results after sorting, aggregation & removing duplicates
[Message] Contact magic search -- filter = An -- 2 contact founds
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
[Message] [Magic Search] Found 1 results in friends
[Message] [Magic Search] Found 0 results in call logs
[Message] [Magic Search] Found 0 results in chat rooms
[Message] Start measurement of [Get conference infos.].
[Message] Duration of [Get conference infos.]: 0ms.
[Message] [Magic Search] Found 0 results in conferences info
[Message] [Magic Search] Found 1 results after sorting, aggregation & removing duplicates
[Message] Contact magic search -- filter = And -- 2 contact founds
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
[Message] [Magic Search] Found 0 results in friends
[Message] [Magic Search] Found 0 results in call logs
[Message] [Magic Search] Found 0 results in chat rooms
[Message] Start measurement of [Get conference infos.].
[Message] Duration of [Get conference infos.]: 0ms.
[Message] [Magic Search] Found 0 results in conferences info
[Message] [Magic Search] Found 0 results after sorting, aggregation & removing duplicates
[Message] Contact magic search -- filter = Andy -- 1 contact founds
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
CUICatalog: Invalid asset name supplied: ''
[Message] [SHARED] resetSharedCoreLastUpdateTime
[Message] [SHARED] resetSharedCoreLastUpdateTime
[Message] channel [0x1211d0000]: keep alive sent to [TLS://my.domain.com:5061]
[Message] Background task belle-sip recv channel started. Unknown remaining time since application is not fully in background.
[Message] channel [0x1211d0000]: starting recv background task with id=[2a].
[Message] channel [0x1211d0000]: ending recv background task with id=[2a].Cheers, Peter
petervnv
commented
9 months ago On another possibly related note, I tried setting contact_filter_on_default_domain=1 to see if it made any difference.
The result is a crash in xcode as soon as I allow contacts access permission
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.
(
"<SnapKit.LayoutConstraint:0x6000026e10e0@UIVIewExtensions.swift#134 UIStackView:0x1076c1400.left == UIStackView:0x1076c0f40.left>",
"<SnapKit.LayoutConstraint:0x6000026e2580@UIVIewExtensions.swift#135 UIStackView:0x1076c1400.right == UIStackView:0x1076c0f40.right>",
"<SnapKit.LayoutConstraint:0x6000026e0b40@UIVIewExtensions.swift#134 UIStackView:0x1076c0f40.left == linphoneapp.VoipConferenceActiveSpeakerView:0x1076b3a40.left>",
"<SnapKit.LayoutConstraint:0x6000026e0c60@UIVIewExtensions.swift#135 UIStackView:0x1076c0f40.right == linphoneapp.VoipConferenceActiveSpeakerView:0x1076b3a40.right>",
"<NSLayoutConstraint:0x6000021843c0 '_UITemporaryLayoutWidth' linphoneapp.VoipConferenceActiveSpeakerView:0x1076b3a40.width == 0 (active)>",
"<NSLayoutConstraint:0x60000216ff20 'UISV-canvas-connection' UIStackView:0x1076c1400.leading == UIView:0x1076c10f0.leading (active)>",
"<NSLayoutConstraint:0x60000216ff70 'UISV-canvas-connection' H:[UIStackView:0x1076c5010]-(0)-| (active, names: '|':UIStackView:0x1076c1400 )>",
"<NSLayoutConstraint:0x6000021880f0 'UISV-spacing' H:[UIView:0x1076c10f0]-(>=10)-[UIStackView:0x1076c5010] (active)>"
)
Will attempt to recover by breaking constraint
<NSLayoutConstraint:0x6000021880f0 'UISV-spacing' H:[UIView:0x1076c10f0]-(>=10)-[UIStackView:0x1076c5010] (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.
(
"<SnapKit.LayoutConstraint:0x6000026e0d20@UIVIewExtensions.swift#238 UIStackView:0x1076c1400.top == UIStackView:0x1076c0f40.top + 20.0>",
"<NSLayoutConstraint:0x600002184690 'UISV-canvas-connection' UIStackView:0x1076c0f40.top == UIStackView:0x1076c1400.top (active)>"
)
Will attempt to recover by breaking constraint
<NSLayoutConstraint:0x600002184690 'UISV-canvas-connection' UIStackView:0x1076c0f40.top == UIStackView:0x1076c1400.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.
[Message] ( PhoneMainView.m:645 ) Change current view to DialerView
[Message] [ToneManager] stopDtmfStream
Calling -viewWillAppear: directly on a view controller is not supported, and may result in out-of-order callbacks and other inconsistent behavior. Use the -beginAppearanceTransition:animated: and -endAppearanceTransition APIs on UIViewController to manually drive appearance callbacks instead. Make a symbolic breakpoint at UIViewControllerAlertForAppearanceCallbackMisuse to catch this in the debugger. View controller: <SideMenuTableView: 0x1143649c0>
Calling -viewDidDisappear: directly on a view controller is not supported, and may result in out-of-order callbacks and other inconsistent behavior. Use the -beginAppearanceTransition:animated: and -endAppearanceTransition APIs on UIViewController to manually drive appearance callbacks instead. Make a symbolic breakpoint at UIViewControllerAlertForAppearanceCallbackMisuse to catch this in the debugger. View controller: <SideMenuView: 0x11432a020>
Calling -viewDidAppear: directly on a view controller is not supported, and may result in out-of-order callbacks and other inconsistent behavior. Use the -beginAppearanceTransition:animated: and -endAppearanceTransition APIs on UIViewController to manually drive appearance callbacks instead. Make a symbolic breakpoint at UIViewControllerAlertForAppearanceCallbackMisuse to catch this in the debugger. View controller: <DialerView: 0x10d90f000>
Calling -viewDidAppear: directly on a view controller is not supported, and may result in out-of-order callbacks and other inconsistent behavior. Use the -beginAppearanceTransition:animated: and -endAppearanceTransition APIs on UIViewController to manually drive appearance callbacks instead. Make a symbolic breakpoint at UIViewControllerAlertForAppearanceCallbackMisuse to catch this in the debugger. View controller: <TabBarView: 0x10d8aba00>
Calling -viewDidAppear: directly on a view controller is not supported, and may result in out-of-order callbacks and other inconsistent behavior. Use the -beginAppearanceTransition:animated: and -endAppearanceTransition APIs on UIViewController to manually drive appearance callbacks instead. Make a symbolic breakpoint at UIViewControllerAlertForAppearanceCallbackMisuse to catch this in the debugger. View controller: <StatusBarView: 0x10d074c00>
Calling -viewDidAppear: directly on a view controller is not supported, and may result in out-of-order callbacks and other inconsistent behavior. Use the -beginAppearanceTransition:animated: and -endAppearanceTransition APIs on UIViewController to manually drive appearance callbacks instead. Make a symbolic breakpoint at UIViewControllerAlertForAppearanceCallbackMisuse to catch this in the debugger. View controller: <SideMenuView: 0x11432a020>
[Message] [PushKit] credentials updated with voip token: {length = 80, bytes = 0x80a119ba 2781dc29 f0a91f3f fa21a6a2 ... d935ebde 65c803a0 }
[Debug] (FastAddressBook.m:218 ) CNContactStore authorization granted
This method should not be called on the main thread as it may lead to UI unresponsiveness.
[Warning] Skipping vCard validation
[Warning] Skipping vCard validation
[Warning] Skipping vCard validation
[Warning] Skipping vCard validation
[Warning] Skipping vCard validation
[Warning] Skipping vCard validation
[Message] Updating friend list [0x600003904270](_default) subscriptions
[Message] Friend list [0x600003904270] subscription update skipped since subscriptions not enabled yet
[Debug] (FastAddressBook.m:538 ) dumpContactsDisplayNamesToUserDefaults
Message from debugger: killedI'm running xcode 15.2
petervnv
commented
9 months ago Hi @martinsben
Hope this report was useful. Are you able to reproduce the bug now?
martinsben
commented
9 months ago Hi,
No, I still can't reproduce the bug.
"Trying to set an invalid vCard (no fullname) to friend, aborting" Error when creating the vCard, it doesn't have a name. Normally, it's impossible to create a friend (and a VCard) without name, did you set a name when you created the friend? Can you send me a video recording?
petervnv
commented
9 months ago Hi, Hmm, weird. I do create a new contact with first and last name, just not a normal phone number. Screen recording attached.
Cheers, Peter
Edit: I just tried adding a normal phone number but the result is the same
petervnv
commented
9 months ago I have been trying to test with your infrastructure since yesterday but your subscribe.linphone.org server seems to be down (always replies with 500 error code). You can confirm this by trying to login through your web portal.
Viish
commented
9 months ago Thanks @petervnv we'll fix it, we weren't aware of this issue...
petervnv
commented
8 months ago You're welcome @Viish Your server is working normally again
Viish
commented
8 months ago Almost, devices management still isn't restored.
petervnv
commented
8 months ago @martinsben Now that your server has somewhat been restored I was able to continue testing.
Indeed I was now able to confirm that when using the release/5.2 branch completely unmodified and pointing to your infrastructure I cannot reproduce the bugs I described.
But as soon as I try pointing to my own infrastructure the bugs I described appear. Not sure where the problem lies since my infrastructure works as expected with the linphone-android app, just not with linphone-iphone.
I will continue testing to see if I can figure out why this happens.
petervnv
commented
8 months ago Hi again @martinsben and @Viish
I have been performing multiple tests and am still struggling to understand why this bug only shows up with non sip.linphone.org contacts.
Is that sip.linphone.org domain hardcoded somewhere in Core? After I add a (non linphone) SIP account in contacts I do see that strange Vcard error message in Xcode logs which is probably the origin on this bug:
[Warning] Trying to set an invalid vCard (no fullname) to friend, aborting
Type: Notice | Timestamp: 2024-03-05 19:24:16.048669Z | Process: linphone | Library: linphone | TID: 0x8d00e
[Error] linphone_friend_list_add_friend(): invalid friend, no vCard, SIP URI or phone numberHere's the actual vcard created in linphone and then exported from the simulator:
BEGIN:VCARD
VERSION:3.0
PRODID:-//Apple Inc.//iPhone OS 17.2//EN
N:Pix6;andy;;;
FN:andy Pix6
NICKNAME:andy Pix6
TEL;type=CELL;type=VOICE;type=pref:+1 (555) 121-2
IMPP;X-SERVICE-TYPE=SIP;type=pref:x-apple:1002@my.domain.com
END:VCARDI don't see any problem with the Vcard so I don't understand why linphone doesn't seem to like it even though it is a new contact created in linphone. Also I don't see any fullname field that the error mentions, but I am assuming it is FN?
I only see mention of a "fullname" variable in the LinphoneWrapper.swift Pod on line 36426:
public var fullName: String?
Any idea as to what is wrong?
Cheers
martinsben
commented
8 months ago Hi @petervnv, Thanks for your support and help. I've tested with non-Linphone accounts, but it's still impossible to reproduce. I'll take a closer look at this problem as soon as possible. I'll get back to you as soon as I've found a solution.
petervnv
commented
8 months ago Hi @martinsben,
Any progress on this? Is there anything I can do to help?
Cheers
martinsben
commented
7 months ago Hi @petervnv,
Sorry for the late reply, I may have found the problem. Are you forcing the lime_chat_rooms ?
petervnv
commented
7 months ago Hi @martinsben,
Yes I am forcing lime_chat_rooms
Edit: @martinsben I did some more testing after your message. If I disable forcing lime_chat_rooms I can now pick the contact to message but only in plain text. As soon as I toggle LIME encryption the contact becomes greyed out and is not selectable any more. So there seems to be a bug with LIME chats in iOS, maybe similar to the one I reported for Android and @Viish promptly fixed?
Even stranger is that LIME messages do work with the iOS client as long as I initiate the encrypted chat from the android client, just not the other way around
petervnv
commented
7 months ago Hi again @martinsben,
Now that the bug has been identified do you have an estimate of when it will be fixed?
Cheers
martinsben
commented
7 months ago Hi, Have you correctly configured your own LIME server URL? Which sip domain do you use?
petervnv
commented
7 months ago Hi @martinsben,
Yes I am sure the LIME server URL is correct and working, specially since I can receive (and reply) to LIME IM messages without any issues. The only problem is that I can't start a new LIME IM message from the iOS client because the LIME contact is always greyed out. But the fact I can reply to LIME messages when the room is created from Android and/or Desktop clients (always using the same LIME URL obviously) is proof that there is nothing wrong with the LIME URL.
Since the behavior is similar to what I experienced before in the android client before Viish fixed it, I suspect the issue is similar.
Cheers
Edit: Forgot to add that the SIP domain I am using is rudis.vip I can give you full access if you like since it is only a test deployment with nothing sensitive. Let me know if you need access. @Viish has my email address for direct contact
petervnv
commented
7 months ago As you can see in the attached video LIME messages work as expected when the room is created from the android client, but when trying to create a new room in the iPhone client the LIME contacts are not selectable, only plain text IMs work.
petervnv
commented
6 months ago Hi,
Just did a fresh compilation of both iphone (release/5.2) and android (release/5.2) and left all the defaults (except I changed sip.linphone.org to my rudis.vip domain and keyserver). I also changed (in android only since there's no equivalent option in iphone client) allow_lime_friend_without_capability and allow_group_friend_without_capability to true.
After some testing it seems my hunch was correct since before changing allow_lime_friend_without_capability the android client was behaving the same as iphone video above. After changing that setting I can now start an encrypted IM from Android but still not the other way around...
Video from Android side attached.
Cheers, Peter
petervnv
commented
6 months ago Hi @martinsben, I appreciate you are busy with other things but can you please point me to the source code file that does the check function if the peer has presence before allowing it to be added to a new LIME chat so I can change it myself?
Basically looking for the ios source code equivalent to this.
Thanks, Peter
martinsben
commented
6 months ago Hi @petervnv Sorry for the wait, these settings are not available in the iOS application. Check shouldHideEncryptedChatView calls in HistoryDetailsView and UIContactDetailsCell. Maybe, you can set : _encryptedChatView.hidden = false;
petervnv
commented
6 months ago Hi @martinsben
No problem. I know you're busy and I appreciate you taking the time to point me in the right direction.
I think I'm almost there. I tried setting _encryptedChatView.hidden = false; in HistoryDetailsView as well as UIContactDetailsCell and indeed there does seem to be some improvements. Now in the contact view I can start a LIME encrypted message directly and it does work :)
Unfortunately the problem still remains when trying to start a new 1to1 or group chat from the Chat view. I'm looking through the source of ChatConversationCreateView.m and trying to figure out what I need to change there to fix that last problem.
Any ideas?
All ok now in the contact view
All ok for starting new plaintext IM from the chat view
But as soon as I toggle encryption the contact becomes greyed out and can't be selected. Can you point me to the where in the source this logic is triggered so I can disable it and force the contact to be selectable?
Cheers, Peter
martinsben
commented
6 months ago Try this in ChatConversationCreateTableView (270-272): BOOL greyCellForEncryptedChat = true; BOOL greyCellForGroupChat = true; cell.userInteractionEnabled = cell.greyView.hidden = greyCellForEncryptedChat && greyCellForGroupChat;
petervnv
commented
6 months ago Thanks for the tip @martinsben, I feel like we're almost there.
Indeed now I can select the contacts from that view and start a new chat but I noticed that it was always starting plain text chats instead of LIME ones. I guess there must be some part of the code to force it to use LIME just like in the contact details view (which works as expected - I confirmed the chats started through the contact detail view is LIME encrypted).
It seems the app doesn't recognize the contact as a LIME capable friend (at least in the chat view) because I then tried setting force_lime_chat_rooms to true and now I get the old behavior of no contacts at all being displayed when trying to start a new chat.
Any ideas?
Cheers, Peter
petervnv
commented
5 months ago I finally got it working as desired. Going to go ahead and close this ticket.
@martinsben thanks so much for your help!
Cheers
Hi,
5.2 release running on SDK 5.3.21 All works as expected except for 2 bugs:
1) After adding a new sip contact the contact details view only displays the phone icon but is missing the chat one In the logs you get the error message: CUICatalog: Invalid asset name supplied: ''
2) Probably related to 1): When trying to start a new chat it seems the results table is also not being displayed, effectively making it impossible to start a new chat from iOS. You can see in the logs that it does find the contact:
[Magic Search] Found 1 results in friendsRelevant logs from xcode:
Hope these bug reports are useful.
Cheers, Peter