keymanapp / keyman

Keyman cross platform input methods system running on Android, iOS, Linux, macOS, Windows and mobile and desktop web
https://keyman.com/
Other
394 stars 110 forks source link

bug(ios): Error when choosing the KMSample2 keyboard using "globe" icon #7020

Open khashashin opened 2 years ago

khashashin commented 2 years ago

Describe the bug I followed this guide to install the keyboard I created with Keyman Developer 15: https://help.keyman.com/developer/engine/iphone-and-ipad/15.0/guides/system-keyboard/

I was able to successfully create the project and install it on the physical iPhone 13 Pro with the latest system updates.

I added the keyboard as a system keyboard in the settings, but when I select it with the "globe" icon, the app freezes and I get the following error in xCode:

image

In logs there are this:

2022-07-30 13:11:05.186469+0200 SWKeyboard[13173:874152] [Info] [KeymanEngine] > SWKeyboard Version: 1.0 Build: 1 PID: 13173
2022-07-30 13:11:05.186522+0200 SWKeyboard[13173:874152] [Info] [KeymanEngine] > XCGLogger Version: 6.1.0 - Level: Info
dyld[13173]: missing symbol called
(lldb) 

During the startup process, before I select the keyboard with the "globe" icon, the following logs are displayed (maybe this can also be useful for troubleshooting):

Message from debugger: Terminated due to signal 9
2022-07-30 13:06:41.871046+0200 MobileSafari[12732:867504] [core] "Exceeded the maximum number of connections (2) to accountsd: 3 connections open. Consider switching to +[ACAccountStore defaultStore]"
2022-07-30 13:06:41.872037+0200 MobileSafari[12732:867457] [MobileSafari] CGImageSourceCopyPropertiesAtIndex:4182: *** ERROR: CGImageSourceCopyPropertiesAtIndex: source is nil
2022-07-30 13:06:41.872105+0200 MobileSafari[12732:867457] [MobileSafari] CGImageSourceCreateThumbnailAtIndex:4097: *** ERROR: CGImageSourceCreateThumbnailAtIndex: source is nil
2022-07-30 13:06:41.872528+0200 MobileSafari[12732:867544] [MobileSafari] CGImageSourceCreateImageAtIndex:4058: *** ERROR: CGImageSourceCreateImageAtIndex: source is nil
2022-07-30 13:06:41.911463+0200 MobileSafari[12732:867457] [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. 
(
    "<NSLayoutConstraint:0x2839de8a0 H:[UILayoutGuide:0x2823dc380'SFCapsuleTextVerticalAlignmentGuide']-(>=18)-|   (active, names: CapsuleNavigationBar?isSe...:0x113d36710, '|':CapsuleNavigationBar?isSe...:0x113d36710 )>",
    "<NSLayoutConstraint:0x2839de760 H:|-(>=18)-[UILayoutGuide:0x2823dc380'SFCapsuleTextVerticalAlignmentGuide']   (active, names: CapsuleNavigationBar?isSe...:0x113d36710, '|':CapsuleNavigationBar?isSe...:0x113d36710 )>",
    "<NSLayoutConstraint:0x2839de620 '_UITemporaryLayoutWidth' CapsuleNavigationBar?isSe....width == 0   (active, names: CapsuleNavigationBar?isSe...:0x113d36710 )>"
)

Will attempt to recover by breaking constraint 
<NSLayoutConstraint:0x2839de8a0 H:[UILayoutGuide:0x2823dc380'SFCapsuleTextVerticalAlignmentGuide']-(>=18)-|   (active, names: CapsuleNavigationBar?isSe...:0x113d36710, '|':CapsuleNavigationBar?isSe...:0x113d36710 )>

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.
2022-07-30 13:06:41.911845+0200 MobileSafari[12732:867457] [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. 
(
    "<NSLayoutConstraint:0x2839dead0 UILayoutGuide:0x2823dc380'SFCapsuleTextVerticalAlignmentGuide'.bottom <= CapsuleNavigationBar?isSe....bottom - 4   (active, names: CapsuleNavigationBar?isSe...:0x113d36710 )>",
    "<NSLayoutConstraint:0x2839dea80 V:|-(>=4)-[UILayoutGuide:0x2823dc380'SFCapsuleTextVerticalAlignmentGuide']   (active, names: CapsuleNavigationBar?isSe...:0x113d36710, '|':CapsuleNavigationBar?isSe...:0x113d36710 )>",
    "<NSLayoutConstraint:0x2839de670 '_UITemporaryLayoutHeight' CapsuleNavigationBar?isSe....height == 0   (active, names: CapsuleNavigationBar?isSe...:0x113d36710 )>"
)

Will attempt to recover by breaking constraint 
<NSLayoutConstraint:0x2839dead0 UILayoutGuide:0x2823dc380'SFCapsuleTextVerticalAlignmentGuide'.bottom <= CapsuleNavigationBar?isSe....bottom - 4   (active, names: CapsuleNavigationBar?isSe...:0x113d36710 )>

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.
2022-07-30 13:06:41.912055+0200 MobileSafari[12732:867457] [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. 
(
    "<NSLayoutConstraint:0x2839dcdc0 H:|-(14)-[TabBarItemTitle]   (active, names: TabBarItemTitle:0x113d36d30, CapsuleNavigationBar?isSe...:0x113d36710, '|':CapsuleNavigationBar?isSe...:0x113d36710 )>",
    "<NSLayoutConstraint:0x2839de760 H:|-(>=18)-[UILayoutGuide:0x2823dc380'SFCapsuleTextVerticalAlignmentGuide']   (active, names: CapsuleNavigationBar?isSe...:0x113d36710, '|':CapsuleNavigationBar?isSe...:0x113d36710 )>",
    "<NSLayoutConstraint:0x2839dce10 TabBarItemTitle.leading >= UILayoutGuide:0x2823dc380'SFCapsuleTextVerticalAlignmentGuide'.leading   (active, names: TabBarItemTitle:0x113d36d30 )>"
)

Will attempt to recover by breaking constraint 
<NSLayoutConstraint:0x2839dce10 TabBarItemTitle.leading >= UILayoutGuide:0x2823dc380'SFCapsuleTextVerticalAlignmentGuide'.leading   (active, names: TabBarItemTitle:0x113d36d30 )>

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.
2022-07-30 13:06:41.912598+0200 MobileSafari[12732:867457] [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. 
(
    "<NSLayoutConstraint:0x2839dea80 V:|-(>=4)-[UILayoutGuide:0x2823dc380'SFCapsuleTextVerticalAlignmentGuide']   (active, names: CapsuleNavigationBar?isSe...:0x113d36710, '|':CapsuleNavigationBar?isSe...:0x113d36710 )>",
    "<NSLayoutConstraint:0x2839de9e0 UILayoutGuide:0x2823dc380'SFCapsuleTextVerticalAlignmentGuide'.centerY == UILayoutGuide:0x2823db8e0'UIViewLayoutMarginsGuide'.centerY   (active)>",
    "<NSLayoutConstraint:0x2839de670 '_UITemporaryLayoutHeight' CapsuleNavigationBar?isSe....height == 0   (active, names: CapsuleNavigationBar?isSe...:0x113d36710 )>",
    "<NSLayoutConstraint:0x2839c5680 'UIView-bottomMargin-guide-constraint' V:[UILayoutGuide:0x2823db8e0'UIViewLayoutMarginsGuide']-(8)-|   (active, names: CapsuleNavigationBar?isSe...:0x113d36710, '|':CapsuleNavigationBar?isSe...:0x113d36710 )>",
    "<NSLayoutConstraint:0x2839c5630 'UIView-topMargin-guide-constraint' V:|-(8)-[UILayoutGuide:0x2823db8e0'UIViewLayoutMarginsGuide']   (active, names: CapsuleNavigationBar?isSe...:0x113d36710, '|':CapsuleNavigationBar?isSe...:0x113d36710 )>"
)

Will attempt to recover by breaking constraint 
<NSLayoutConstraint:0x2839de9e0 UILayoutGuide:0x2823dc380'SFCapsuleTextVerticalAlignmentGuide'.centerY == UILayoutGuide:0x2823db8e0'UIViewLayoutMarginsGuide'.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.
2022-07-30 13:06:41.914356+0200 MobileSafari[12732:867457] [Assert] Trying to decrement _unsatisfiableConstraintsLoggingSuspensionCount when it's already 0. We lost count one way or another, or else we had a stack recursion. self = <SFCapsuleCollectionView: 0x113d2a330; frame = (0 0; 390 844); gestureRecognizers = <NSArray: 0x2814ba190>; layer = <CALayer: 0x281aca600>>
2022-07-30 13:06:41.916660+0200 MobileSafari[12732:867457] [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:0x2839c2ad0 h=--& v=--& _UIToolbarContentView:0x113d17be0.height == 0   (active)>",
    "<NSLayoutConstraint:0x2839ee580 V:|-(0)-[_UIButtonBarStackView:0x113d18630]   (active, names: '|':_UIToolbarContentView:0x113d17be0 )>",
    "<NSLayoutConstraint:0x2839ee5d0 _UIButtonBarStackView:0x113d18630.bottom == _UIToolbarContentView:0x113d17be0.bottom   (active)>",
    "<NSLayoutConstraint:0x2839c2f30 UIImageView:0x113d51750.centerY == _UIModernBarButton:0x113d503f0.centerY   (active)>",
    "<NSLayoutConstraint:0x2839c07d0 'IB_Baseline_Baseline' _UIModernBarButton:0x113d503f0.lastBaseline == UILayoutGuide:0x2823c50a0'UIViewLayoutMarginsGuide'.bottom   (active)>",
    "<NSLayoutConstraint:0x2839c0820 'IB_Top_Top' V:|-(>=0)-[_UIModernBarButton:0x113d503f0]   (active, names: '|':_UIButtonBarButton:0x113d4ee70 )>",
    "<NSLayoutConstraint:0x2839c0910 'UIButtonBar.maximumAlignmentSize' _UIButtonBarButton:0x113d4ee70.height == UILayoutGuide:0x2823ee3e0'UIViewLayoutMarginsGuide'.height   (active)>",
    "<NSLayoutConstraint:0x2839ee3f0 'UIView-bottomMargin-guide-constraint' V:[UILayoutGuide:0x2823ee3e0'UIViewLayoutMarginsGuide']-(0)-|   (active, names: '|':_UIButtonBarStackView:0x113d18630 )>",
    "<NSLayoutConstraint:0x2839c0730 'UIView-bottomMargin-guide-constraint' V:[UILayoutGuide:0x2823c50a0'UIViewLayoutMarginsGuide']-(11)-|   (active, names: '|':_UIButtonBarButton:0x113d4ee70 )>",
    "<NSLayoutConstraint:0x2839ee350 'UIView-topMargin-guide-constraint' V:|-(0)-[UILayoutGuide:0x2823ee3e0'UIViewLayoutMarginsGuide']   (active, names: '|':_UIButtonBarStackView:0x113d18630 )>"
)

Will attempt to recover by breaking constraint 
<NSLayoutConstraint:0x2839c2f30 UIImageView:0x113d51750.centerY == _UIModernBarButton:0x113d503f0.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.
2022-07-30 13:06:41.917219+0200 MobileSafari[12732:867457] [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:0x2839c2ad0 h=--& v=--& _UIToolbarContentView:0x113d17be0.height == 0   (active)>",
    "<NSLayoutConstraint:0x2839ee580 V:|-(0)-[_UIButtonBarStackView:0x113d18630]   (active, names: '|':_UIToolbarContentView:0x113d17be0 )>",
    "<NSLayoutConstraint:0x2839ee5d0 _UIButtonBarStackView:0x113d18630.bottom == _UIToolbarContentView:0x113d17be0.bottom   (active)>",
    "<NSLayoutConstraint:0x2839c3250 UIImageView:0x113d50ed0.centerY == _UIModernBarButton:0x113d51ed0.centerY   (active)>",
    "<NSLayoutConstraint:0x2839c0c80 'IB_Baseline_Baseline' _UIModernBarButton:0x113d51ed0.lastBaseline == UILayoutGuide:0x2823c55e0'UIViewLayoutMarginsGuide'.bottom   (active)>",
    "<NSLayoutConstraint:0x2839c0cd0 'IB_Top_Top' V:|-(>=0)-[_UIModernBarButton:0x113d51ed0]   (active, names: '|':_UIButtonBarButton:0x113d51930 )>",
    "<NSLayoutConstraint:0x2839c0dc0 'UIButtonBar.maximumAlignmentSize' _UIButtonBarButton:0x113d51930.height == UILayoutGuide:0x2823ee3e0'UIViewLayoutMarginsGuide'.height   (active)>",
    "<NSLayoutConstraint:0x2839ee3f0 'UIView-bottomMargin-guide-constraint' V:[UILayoutGuide:0x2823ee3e0'UIViewLayoutMarginsGuide']-(0)-|   (active, names: '|':_UIButtonBarStackView:0x113d18630 )>",
    "<NSLayoutConstraint:0x2839c0be0 'UIView-bottomMargin-guide-constraint' V:[UILayoutGuide:0x2823c55e0'UIViewLayoutMarginsGuide']-(11)-|   (active, names: '|':_UIButtonBarButton:0x113d51930 )>",
    "<NSLayoutConstraint:0x2839ee350 'UIView-topMargin-guide-constraint' V:|-(0)-[UILayoutGuide:0x2823ee3e0'UIViewLayoutMarginsGuide']   (active, names: '|':_UIButtonBarStackView:0x113d18630 )>"
)

Will attempt to recover by breaking constraint 
<NSLayoutConstraint:0x2839c3250 UIImageView:0x113d50ed0.centerY == _UIModernBarButton:0x113d51ed0.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.
2022-07-30 13:06:41.917613+0200 MobileSafari[12732:867457] [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:0x2839c2ad0 h=--& v=--& _UIToolbarContentView:0x113d17be0.height == 0   (active)>",
    "<NSLayoutConstraint:0x2839ee580 V:|-(0)-[_UIButtonBarStackView:0x113d18630]   (active, names: '|':_UIToolbarContentView:0x113d17be0 )>",
    "<NSLayoutConstraint:0x2839ee5d0 _UIButtonBarStackView:0x113d18630.bottom == _UIToolbarContentView:0x113d17be0.bottom   (active)>",
    "<NSLayoutConstraint:0x2839c3430 UIImageView:0x113d52b30.centerY == _UIModernBarButton:0x113d52ef0.centerY   (active)>",
    "<NSLayoutConstraint:0x2839c1130 'IB_Baseline_Baseline' _UIModernBarButton:0x113d52ef0.lastBaseline == UILayoutGuide:0x2823c5b20'UIViewLayoutMarginsGuide'.bottom   (active)>",
    "<NSLayoutConstraint:0x2839c1180 'IB_Top_Top' V:|-(>=0)-[_UIModernBarButton:0x113d52ef0]   (active, names: '|':_UIButtonBarButton:0x113d52950 )>",
    "<NSLayoutConstraint:0x2839c1270 'UIButtonBar.maximumAlignmentSize' _UIButtonBarButton:0x113d52950.height == UILayoutGuide:0x2823ee3e0'UIViewLayoutMarginsGuide'.height   (active)>",
    "<NSLayoutConstraint:0x2839ee3f0 'UIView-bottomMargin-guide-constraint' V:[UILayoutGuide:0x2823ee3e0'UIViewLayoutMarginsGuide']-(0)-|   (active, names: '|':_UIButtonBarStackView:0x113d18630 )>",
    "<NSLayoutConstraint:0x2839c1090 'UIView-bottomMargin-guide-constraint' V:[UILayoutGuide:0x2823c5b20'UIViewLayoutMarginsGuide']-(11)-|   (active, names: '|':_UIButtonBarButton:0x113d52950 )>",
    "<NSLayoutConstraint:0x2839ee350 'UIView-topMargin-guide-constraint' V:|-(0)-[UILayoutGuide:0x2823ee3e0'UIViewLayoutMarginsGuide']   (active, names: '|':_UIButtonBarStackView:0x113d18630 )>"
)

Will attempt to recover by breaking constraint 
<NSLayoutConstraint:0x2839c3430 UIImageView:0x113d52b30.centerY == _UIModernBarButton:0x113d52ef0.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.
2022-07-30 13:06:41.917984+0200 MobileSafari[12732:867457] [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:0x2839c2ad0 h=--& v=--& _UIToolbarContentView:0x113d17be0.height == 0   (active)>",
    "<NSLayoutConstraint:0x2839ee580 V:|-(0)-[_UIButtonBarStackView:0x113d18630]   (active, names: '|':_UIToolbarContentView:0x113d17be0 )>",
    "<NSLayoutConstraint:0x2839ee5d0 _UIButtonBarStackView:0x113d18630.bottom == _UIToolbarContentView:0x113d17be0.bottom   (active)>",
    "<NSLayoutConstraint:0x2839c3750 UIImageView:0x113d53a70.centerY == _UIModernBarButton:0x113d53e30.centerY   (active)>",
    "<NSLayoutConstraint:0x2839c1630 'IB_Baseline_Baseline' _UIModernBarButton:0x113d53e30.lastBaseline == UILayoutGuide:0x2823c6060'UIViewLayoutMarginsGuide'.bottom   (active)>",
    "<NSLayoutConstraint:0x2839c1680 'IB_Top_Top' V:|-(>=0)-[_UIModernBarButton:0x113d53e30]   (active, names: '|':_UIButtonBarButton:0x113d53890 )>",
    "<NSLayoutConstraint:0x2839c1770 'UIButtonBar.maximumAlignmentSize' _UIButtonBarButton:0x113d53890.height == UILayoutGuide:0x2823ee3e0'UIViewLayoutMarginsGuide'.height   (active)>",
    "<NSLayoutConstraint:0x2839ee3f0 'UIView-bottomMargin-guide-constraint' V:[UILayoutGuide:0x2823ee3e0'UIViewLayoutMarginsGuide']-(0)-|   (active, names: '|':_UIButtonBarStackView:0x113d18630 )>",
    "<NSLayoutConstraint:0x2839c1590 'UIView-bottomMargin-guide-constraint' V:[UILayoutGuide:0x2823c6060'UIViewLayoutMarginsGuide']-(11)-|   (active, names: '|':_UIButtonBarButton:0x113d53890 )>",
    "<NSLayoutConstraint:0x2839ee350 'UIView-topMargin-guide-constraint' V:|-(0)-[UILayoutGuide:0x2823ee3e0'UIViewLayoutMarginsGuide']   (active, names: '|':_UIButtonBarStackView:0x113d18630 )>"
)

Will attempt to recover by breaking constraint 
<NSLayoutConstraint:0x2839c3750 UIImageView:0x113d53a70.centerY == _UIModernBarButton:0x113d53e30.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.
2022-07-30 13:06:41.918390+0200 MobileSafari[12732:867457] [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:0x2839c2ad0 h=--& v=--& _UIToolbarContentView:0x113d17be0.height == 0   (active)>",
    "<NSLayoutConstraint:0x2839ee580 V:|-(0)-[_UIButtonBarStackView:0x113d18630]   (active, names: '|':_UIToolbarContentView:0x113d17be0 )>",
    "<NSLayoutConstraint:0x2839ee5d0 _UIButtonBarStackView:0x113d18630.bottom == _UIToolbarContentView:0x113d17be0.bottom   (active)>",
    "<NSLayoutConstraint:0x2839c5540 UIImageView:0x113d549b0.centerY == _UIModernBarButton:0x113d54d70.centerY   (active)>",
    "<NSLayoutConstraint:0x2839c1ae0 'IB_Baseline_Baseline' _UIModernBarButton:0x113d54d70.lastBaseline == UILayoutGuide:0x2823c65a0'UIViewLayoutMarginsGuide'.bottom   (active)>",
    "<NSLayoutConstraint:0x2839c1b30 'IB_Top_Top' V:|-(>=0)-[_UIModernBarButton:0x113d54d70]   (active, names: '|':_UIButtonBarButton:0x113d547d0 )>",
    "<NSLayoutConstraint:0x2839c1c20 'UIButtonBar.maximumAlignmentSize' _UIButtonBarButton:0x113d547d0.height == UILayoutGuide:0x2823ee3e0'UIViewLayoutMarginsGuide'.height   (active)>",
    "<NSLayoutConstraint:0x2839ee3f0 'UIView-bottomMargin-guide-constraint' V:[UILayoutGuide:0x2823ee3e0'UIViewLayoutMarginsGuide']-(0)-|   (active, names: '|':_UIButtonBarStackView:0x113d18630 )>",
    "<NSLayoutConstraint:0x2839c1a40 'UIView-bottomMargin-guide-constraint' V:[UILayoutGuide:0x2823c65a0'UIViewLayoutMarginsGuide']-(11)-|   (active, names: '|':_UIButtonBarButton:0x113d547d0 )>",
    "<NSLayoutConstraint:0x2839ee350 'UIView-topMargin-guide-constraint' V:|-(0)-[UILayoutGuide:0x2823ee3e0'UIViewLayoutMarginsGuide']   (active, names: '|':_UIButtonBarStackView:0x113d18630 )>"
)

Will attempt to recover by breaking constraint 
<NSLayoutConstraint:0x2839c5540 UIImageView:0x113d549b0.centerY == _UIModernBarButton:0x113d54d70.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.
2022-07-30 13:06:41.920261+0200 MobileSafari[12732:867457] [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. 
(
    "<NSLayoutConstraint:0x2839eb660 TabBarItemTitle.leading >= UILayoutGuide:0x2823e8b60'SFCapsuleTextVerticalAlignmentGuide'.leading   (active, names: TabBarItemTitle:0x113e82830 )>",
    "<NSLayoutConstraint:0x2839eba20 H:|-(14)-[TabBarItemTitle]   (active, names: TabBarItemTitle:0x113e82830, CapsuleNavigationBar?isSe...:0x113e824f0, '|':CapsuleNavigationBar?isSe...:0x113e824f0 )>",
    "<NSLayoutConstraint:0x2839c6710 H:[_SFDimmingButton:0x113d162d0]-(24)-[_SFDimmingButton:0x113d34220]   (active)>",
    "<NSLayoutConstraint:0x2839c6800 H:|-(>=13)-[_SFDimmingButton:0x113d162d0]   (active, names: CapsuleNavigationBar?isSe...:0x113e824f0, '|':CapsuleNavigationBar?isSe...:0x113e824f0 )>",
    "<NSLayoutConstraint:0x2839c6850 H:[_SFDimmingButton:0x113d34220]-(>=13)-[UILayoutGuide:0x2823e8b60'SFCapsuleTextVerticalAlignmentGuide']   (active)>"
)

Will attempt to recover by breaking constraint 
<NSLayoutConstraint:0x2839c6850 H:[_SFDimmingButton:0x113d34220]-(>=13)-[UILayoutGuide:0x2823e8b60'SFCapsuleTextVerticalAlignmentGuide']   (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.
2022-07-30 13:06:41.920933+0200 MobileSafari[12732:867457] [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. 
(
    "<NSLayoutConstraint:0x2839eb660 TabBarItemTitle.leading >= UILayoutGuide:0x2823e8b60'SFCapsuleTextVerticalAlignmentGuide'.leading   (active, names: TabBarItemTitle:0x113e82830 )>",
    "<NSLayoutConstraint:0x2839eba20 H:|-(14)-[TabBarItemTitle]   (active, names: TabBarItemTitle:0x113e82830, CapsuleNavigationBar?isSe...:0x113e824f0, '|':CapsuleNavigationBar?isSe...:0x113e824f0 )>",
    "<NSLayoutConstraint:0x2839c6710 H:[_SFDimmingButton:0x113d162d0]-(24)-[_SFDimmingButton:0x113d34220]   (active)>",
    "<NSLayoutConstraint:0x2839c6800 H:|-(>=13)-[_SFDimmingButton:0x113d162d0]   (active, names: CapsuleNavigationBar?isSe...:0x113e824f0, '|':CapsuleNavigationBar?isSe...:0x113e824f0 )>",
    "<NSLayoutConstraint:0x2839c6850 H:[_SFDimmingButton:0x113d34220]-(>=13)-[UILayoutGuide:0x2823e8b60'SFCapsuleTextVerticalAlignmentGuide']   (active)>"
)

Will attempt to recover by breaking constraint 
<NSLayoutConstraint:0x2839c6850 H:[_SFDimmingButton:0x113d34220]-(>=13)-[UILayoutGuide:0x2823e8b60'SFCapsuleTextVerticalAlignmentGuide']   (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.
2022-07-30 13:06:41.921085+0200 MobileSafari[12732:867457] [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. 
(
    "<NSLayoutConstraint:0x2839eba20 H:|-(14)-[TabBarItemTitle]   (active, names: TabBarItemTitle:0x113e82830, CapsuleNavigationBar?isSe...:0x113e824f0, '|':CapsuleNavigationBar?isSe...:0x113e824f0 )>",
    "<NSLayoutConstraint:0x2839c6710 H:[_SFDimmingButton:0x113d162d0]-(24)-[_SFDimmingButton:0x113d34220]   (active)>",
    "<NSLayoutConstraint:0x2839c6800 H:|-(>=13)-[_SFDimmingButton:0x113d162d0]   (active, names: CapsuleNavigationBar?isSe...:0x113e824f0, '|':CapsuleNavigationBar?isSe...:0x113e824f0 )>",
    "<NSLayoutConstraint:0x2839c5310 H:[_SFDimmingButton:0x113d34220]-(>=0)-[TabBarItemTitle]   (active, names: TabBarItemTitle:0x113e82830 )>"
)

Will attempt to recover by breaking constraint 
<NSLayoutConstraint:0x2839c5310 H:[_SFDimmingButton:0x113d34220]-(>=0)-[TabBarItemTitle]   (active, names: TabBarItemTitle:0x113e82830 )>

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.
2022-07-30 13:06:41.922406+0200 MobileSafari[12732:867457] [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. 
(
    "<NSLayoutConstraint:0x2839d7d40 TabBarItemTitle.leading >= UILayoutGuide:0x2823ea300'SFCapsuleTextVerticalAlignmentGuide'.leading   (active, names: TabBarItemTitle:0x113e8b830 )>",
    "<NSLayoutConstraint:0x2839d7cf0 H:|-(14)-[TabBarItemTitle]   (active, names: TabBarItemTitle:0x113e8b830, CapsuleNavigationBar?isSe...:0x113d0c180, '|':CapsuleNavigationBar?isSe...:0x113d0c180 )>",
    "<NSLayoutConstraint:0x2839c78e0 H:|-(>=18)-[UILayoutGuide:0x2823ea300'SFCapsuleTextVerticalAlignmentGuide']   (active, names: CapsuleNavigationBar?isSe...:0x113d0c180, '|':CapsuleNavigationBar?isSe...:0x113d0c180 )>"
)

Will attempt to recover by breaking constraint 
<NSLayoutConstraint:0x2839d7d40 TabBarItemTitle.leading >= UILayoutGuide:0x2823ea300'SFCapsuleTextVerticalAlignmentGuide'.leading   (active, names: TabBarItemTitle:0x113e8b830 )>

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.
2022-07-30 13:06:41.923435+0200 MobileSafari[12732:867457] [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. 
(
    "<NSLayoutConstraint:0x2839d7cf0 H:|-(14)-[TabBarItemTitle]   (active, names: TabBarItemTitle:0x113e8b830, CapsuleNavigationBar?isSe...:0x113d0c180, '|':CapsuleNavigationBar?isSe...:0x113d0c180 )>",
    "<NSLayoutConstraint:0x2839c78e0 H:|-(>=18)-[UILayoutGuide:0x2823ea300'SFCapsuleTextVerticalAlignmentGuide']   (active, names: CapsuleNavigationBar?isSe...:0x113d0c180, '|':CapsuleNavigationBar?isSe...:0x113d0c180 )>",
    "<NSLayoutConstraint:0x2839d7d40 TabBarItemTitle.leading >= UILayoutGuide:0x2823ea300'SFCapsuleTextVerticalAlignmentGuide'.leading   (active, names: TabBarItemTitle:0x113e8b830 )>"
)

Will attempt to recover by breaking constraint 
<NSLayoutConstraint:0x2839d7d40 TabBarItemTitle.leading >= UILayoutGuide:0x2823ea300'SFCapsuleTextVerticalAlignmentGuide'.leading   (active, names: TabBarItemTitle:0x113e8b830 )>

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.
2022-07-30 13:06:41.929373+0200 MobileSafari[12732:867457] [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. 
(
    "<NSLayoutConstraint:0x2839d3cf0 UILayoutGuide:0x2823dcee0'SFCapsuleTextVerticalAlignmentGuide'.centerY == UILayoutGuide:0x2823d7aa0'UIViewLayoutMarginsGuide'.centerY   (active)>",
    "<NSLayoutConstraint:0x2839eb430 V:|-(>=4)-[UILayoutGuide:0x2823dcee0'SFCapsuleTextVerticalAlignmentGuide']   (active, names: CapsuleNavigationBar?isSe...:0x113ebfdc0, '|':CapsuleNavigationBar?isSe...:0x113ebfdc0 )>",
    "<NSLayoutConstraint:0x2839cccd0 '_UITemporaryLayoutHeight' CapsuleNavigationBar?isSe....height == 0   (active, names: CapsuleNavigationBar?isSe...:0x113ebfdc0 )>",
    "<NSLayoutConstraint:0x2839cce60 'UIView-bottomMargin-guide-constraint' V:[UILayoutGuide:0x2823d7aa0'UIViewLayoutMarginsGuide']-(8)-|   (active, names: CapsuleNavigationBar?isSe...:0x113ebfdc0, '|':CapsuleNavigationBar?isSe...:0x113ebfdc0 )>",
    "<NSLayoutConstraint:0x2839ccdc0 'UIView-topMargin-guide-constraint' V:|-(8)-[UILayoutGuide:0x2823d7aa0'UIViewLayoutMarginsGuide']   (active, names: CapsuleNavigationBar?isSe...:0x113ebfdc0, '|':CapsuleNavigationBar?isSe...:0x113ebfdc0 )>"
)

Will attempt to recover by breaking constraint 
<NSLayoutConstraint:0x2839d3cf0 UILayoutGuide:0x2823dcee0'SFCapsuleTextVerticalAlignmentGuide'.centerY == UILayoutGuide:0x2823d7aa0'UIViewLayoutMarginsGuide'.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.
2022-07-30 13:06:41.929600+0200 MobileSafari[12732:867457] [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. 
(
    "<NSLayoutConstraint:0x2839efa20 UILayoutGuide:0x2823dcee0'SFCapsuleTextVerticalAlignmentGuide'.bottom <= CapsuleNavigationBar?isSe....bottom - 4   (active, names: CapsuleNavigationBar?isSe...:0x113ebfdc0 )>",
    "<NSLayoutConstraint:0x2839eb430 V:|-(>=4)-[UILayoutGuide:0x2823dcee0'SFCapsuleTextVerticalAlignmentGuide']   (active, names: CapsuleNavigationBar?isSe...:0x113ebfdc0, '|':CapsuleNavigationBar?isSe...:0x113ebfdc0 )>",
    "<NSLayoutConstraint:0x2839cccd0 '_UITemporaryLayoutHeight' CapsuleNavigationBar?isSe....height == 0   (active, names: CapsuleNavigationBar?isSe...:0x113ebfdc0 )>"
)

Will attempt to recover by breaking constraint 
<NSLayoutConstraint:0x2839efa20 UILayoutGuide:0x2823dcee0'SFCapsuleTextVerticalAlignmentGuide'.bottom <= CapsuleNavigationBar?isSe....bottom - 4   (active, names: CapsuleNavigationBar?isSe...:0x113ebfdc0 )>

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.
2022-07-30 13:06:41.929760+0200 MobileSafari[12732:867457] [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. 
(
    "<NSLayoutConstraint:0x2839cc8c0 H:|-(14)-[TabBarItemTitle]   (active, names: TabBarItemTitle:0x113ec0590, CapsuleNavigationBar?isSe...:0x113ebfdc0, '|':CapsuleNavigationBar?isSe...:0x113ebfdc0 )>",
    "<NSLayoutConstraint:0x2839d8000 H:|-(>=18)-[UILayoutGuide:0x2823dcee0'SFCapsuleTextVerticalAlignmentGuide']   (active, names: CapsuleNavigationBar?isSe...:0x113ebfdc0, '|':CapsuleNavigationBar?isSe...:0x113ebfdc0 )>",
    "<NSLayoutConstraint:0x2839cc910 TabBarItemTitle.leading >= UILayoutGuide:0x2823dcee0'SFCapsuleTextVerticalAlignmentGuide'.leading   (active, names: TabBarItemTitle:0x113ec0590 )>"
)

Will attempt to recover by breaking constraint 
<NSLayoutConstraint:0x2839cc910 TabBarItemTitle.leading >= UILayoutGuide:0x2823dcee0'SFCapsuleTextVerticalAlignmentGuide'.leading   (active, names: TabBarItemTitle:0x113ec0590 )>

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.
2022-07-30 13:06:41.929888+0200 MobileSafari[12732:867457] [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. 
(
    "<NSLayoutConstraint:0x2839d8000 H:|-(>=18)-[UILayoutGuide:0x2823dcee0'SFCapsuleTextVerticalAlignmentGuide']   (active, names: CapsuleNavigationBar?isSe...:0x113ebfdc0, '|':CapsuleNavigationBar?isSe...:0x113ebfdc0 )>",
    "<NSLayoutConstraint:0x2839d1c70 H:[UILayoutGuide:0x2823dcee0'SFCapsuleTextVerticalAlignmentGuide']-(>=18)-|   (active, names: CapsuleNavigationBar?isSe...:0x113ebfdc0, '|':CapsuleNavigationBar?isSe...:0x113ebfdc0 )>",
    "<NSLayoutConstraint:0x2839cc730 '_UITemporaryLayoutWidth' CapsuleNavigationBar?isSe....width == 0   (active, names: CapsuleNavigationBar?isSe...:0x113ebfdc0 )>"
)

Will attempt to recover by breaking constraint 
<NSLayoutConstraint:0x2839d1c70 H:[UILayoutGuide:0x2823dcee0'SFCapsuleTextVerticalAlignmentGuide']-(>=18)-|   (active, names: CapsuleNavigationBar?isSe...:0x113ebfdc0, '|':CapsuleNavigationBar?isSe...:0x113ebfdc0 )>

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.
2022-07-30 13:06:41.967549+0200 MobileSafari[12732:867534] Metal API Validation Enabled
2022-07-30 13:06:42.074076+0200 MobileSafari[12732:867547] [Client] Updating selectors after delegate removal failed with: Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service with pid 93 named com.apple.commcenter.coretelephony.xpc was invalidated from this process." UserInfo={NSDebugDescription=The connection to service with pid 93 named com.apple.commcenter.coretelephony.xpc was invalidated from this process.}
2022-07-30 13:06:42.140707+0200 MobileSafari[12732:867548] [MLPhishing] Failed to load asset: Error Domain=MADownLoadResult Code=18 "Failed to find matching asset for com.apple.MobileAsset.PhishingImageClassifier2"
2022-07-30 13:06:42.407153+0200 MobileSafari[12732:867534] [General] Failed to get any results from PersonalizationPortrait. (null)
2022-07-30 13:06:42.743544+0200 MobileSafari[12732:867505] Detected stale pending counter; resetting to 0
2022-07-30 13:06:44.901034+0200 MobileSafari[12732:867457] Successfully load keyboard extensions
2022-07-30 13:06:44.913411+0200 MobileSafari[12732:867457] API error: <_UIKBCompatInputView: 0x113e2f310; frame = (0 0; 0 0); layer = <CALayer: 0x281a61580>> returned 0 width, assuming UIViewNoIntrinsicMetric
2022-07-30 13:06:44.913472+0200 MobileSafari[12732:867457] API error: <_UIKBCompatInputView: 0x113e2f310; frame = (0 0; 0 0); layer = <CALayer: 0x281a61580>> returned 0 width, assuming UIViewNoIntrinsicMetric
2022-07-30 13:06:44.927868+0200 MobileSafari[12732:867457] [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:0x28394c2d0 h=--& v=--& _UIToolbarContentView:0x113da38e0.width == 0   (active)>",
    "<NSLayoutConstraint:0x283944f00 H:|-(0)-[_UIButtonBarStackView:0x113d9e8d0]   (active, names: '|':_UIToolbarContentView:0x113da38e0 )>",
    "<NSLayoutConstraint:0x283944f50 H:[_UIButtonBarStackView:0x113d9e8d0]-(0)-|   (active, names: '|':_UIToolbarContentView:0x113da38e0 )>",
    "<NSLayoutConstraint:0x283942a80 'IB_Leading_Leading' H:|-(0)-[_UIModernBarButton:0x113e1e880]   (active, names: '|':_UIButtonBarButton:0x113e1e6a0 )>",
    "<NSLayoutConstraint:0x283942120 'IB_Leading_Leading' H:|-(>=5)-[_UIModernBarButton:0x113e1f5d0]   (active, names: '|':_UIButtonBarButton:0x113e1f3f0 )>",
    "<NSLayoutConstraint:0x283942ad0 'IB_Trailing_Trailing' H:[_UIModernBarButton:0x113e1e880]-(>=8)-|   (active, names: '|':_UIButtonBarButton:0x113e1e6a0 )>",
    "<NSLayoutConstraint:0x283942170 'IB_Trailing_Trailing' H:[_UIModernBarButton:0x113e1f5d0]-(>=5)-|   (active, names: '|':_UIButtonBarButton:0x113e1f3f0 )>",
    "<NSLayoutConstraint:0x283943390 'TB_Leading_Leading' H:|-(8)-[_UIModernBarButton:0x113e20680'Done']   (active, names: '|':_UIButtonBarButton:0x113e20140 )>",
    "<NSLayoutConstraint:0x2839432a0 'TB_Trailing_Trailing' H:[_UIModernBarButton:0x113e20680'Done']-(0)-|   (active, names: '|':_UIButtonBarButton:0x113e20140 )>",
    "<NSLayoutConstraint:0x283942990 'UISV-canvas-connection' UILayoutGuide:0x2823db560'UIViewLayoutMarginsGuide'.leading == _UIButtonBarButton:0x113e1e6a0.leading   (active)>",
    "<NSLayoutConstraint:0x2839421c0 'UISV-canvas-connection' UILayoutGuide:0x2823db560'UIViewLayoutMarginsGuide'.trailing == _UIButtonBarButton:0x113e20140.trailing   (active)>",
    "<NSLayoutConstraint:0x283940000 'UISV-spacing' H:[_UIButtonBarButton:0x113e1e6a0]-(0)-[UIView:0x113e1f280]   (active)>",
    "<NSLayoutConstraint:0x283940280 'UISV-spacing' H:[UIView:0x113e1f280]-(0)-[_UIButtonBarButton:0x113e1f3f0]   (active)>",
    "<NSLayoutConstraint:0x2839404b0 'UISV-spacing' H:[_UIButtonBarButton:0x113e1f3f0]-(0)-[UIView:0x113e1ffd0]   (active)>",
    "<NSLayoutConstraint:0x283940730 'UISV-spacing' H:[UIView:0x113e1ffd0]-(0)-[_UIButtonBarButton:0x113e20140]   (active)>",
    "<NSLayoutConstraint:0x283944d70 'UIView-leftMargin-guide-constraint' H:|-(0)-[UILayoutGuide:0x2823db560'UIViewLayoutMarginsGuide'](LTR)   (active, names: '|':_UIButtonBarStackView:0x113d9e8d0 )>",
    "<NSLayoutConstraint:0x283944e10 'UIView-rightMargin-guide-constraint' H:[UILayoutGuide:0x2823db560'UIViewLayoutMarginsGuide']-(0)-|(LTR)   (active, names: '|':_UIButtonBarStackView:0x113d9e8d0 )>"
)

Will attempt to recover by breaking constraint 
<NSLayoutConstraint:0x283942ad0 'IB_Trailing_Trailing' H:[_UIModernBarButton:0x113e1e880]-(>=8)-|   (active, names: '|':_UIButtonBarButton:0x113e1e6a0 )>

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.
2022-07-30 13:06:44.928237+0200 MobileSafari[12732:867457] [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:0x28394c2d0 h=--& v=--& _UIToolbarContentView:0x113da38e0.width == 0   (active)>",
    "<NSLayoutConstraint:0x283944f00 H:|-(0)-[_UIButtonBarStackView:0x113d9e8d0]   (active, names: '|':_UIToolbarContentView:0x113da38e0 )>",
    "<NSLayoutConstraint:0x283944f50 H:[_UIButtonBarStackView:0x113d9e8d0]-(0)-|   (active, names: '|':_UIToolbarContentView:0x113da38e0 )>",
    "<NSLayoutConstraint:0x283942120 'IB_Leading_Leading' H:|-(>=5)-[_UIModernBarButton:0x113e1f5d0]   (active, names: '|':_UIButtonBarButton:0x113e1f3f0 )>",
    "<NSLayoutConstraint:0x283942170 'IB_Trailing_Trailing' H:[_UIModernBarButton:0x113e1f5d0]-(>=5)-|   (active, names: '|':_UIButtonBarButton:0x113e1f3f0 )>",
    "<NSLayoutConstraint:0x283943390 'TB_Leading_Leading' H:|-(8)-[_UIModernBarButton:0x113e20680'Done']   (active, names: '|':_UIButtonBarButton:0x113e20140 )>",
    "<NSLayoutConstraint:0x2839432a0 'TB_Trailing_Trailing' H:[_UIModernBarButton:0x113e20680'Done']-(0)-|   (active, names: '|':_UIButtonBarButton:0x113e20140 )>",
    "<NSLayoutConstraint:0x283942990 'UISV-canvas-connection' UILayoutGuide:0x2823db560'UIViewLayoutMarginsGuide'.leading == _UIButtonBarButton:0x113e1e6a0.leading   (active)>",
    "<NSLayoutConstraint:0x2839421c0 'UISV-canvas-connection' UILayoutGuide:0x2823db560'UIViewLayoutMarginsGuide'.trailing == _UIButtonBarButton:0x113e20140.trailing   (active)>",
    "<NSLayoutConstraint:0x283940000 'UISV-spacing' H:[_UIButtonBarButton:0x113e1e6a0]-(0)-[UIView:0x113e1f280]   (active)>",
    "<NSLayoutConstraint:0x283940280 'UISV-spacing' H:[UIView:0x113e1f280]-(0)-[_UIButtonBarButton:0x113e1f3f0]   (active)>",
    "<NSLayoutConstraint:0x2839404b0 'UISV-spacing' H:[_UIButtonBarButton:0x113e1f3f0]-(0)-[UIView:0x113e1ffd0]   (active)>",
    "<NSLayoutConstraint:0x283940730 'UISV-spacing' H:[UIView:0x113e1ffd0]-(0)-[_UIButtonBarButton:0x113e20140]   (active)>",
    "<NSLayoutConstraint:0x283944d70 'UIView-leftMargin-guide-constraint' H:|-(0)-[UILayoutGuide:0x2823db560'UIViewLayoutMarginsGuide'](LTR)   (active, names: '|':_UIButtonBarStackView:0x113d9e8d0 )>",
    "<NSLayoutConstraint:0x283944e10 'UIView-rightMargin-guide-constraint' H:[UILayoutGuide:0x2823db560'UIViewLayoutMarginsGuide']-(0)-|(LTR)   (active, names: '|':_UIButtonBarStackView:0x113d9e8d0 )>"
)

Will attempt to recover by breaking constraint 
<NSLayoutConstraint:0x283942170 'IB_Trailing_Trailing' H:[_UIModernBarButton:0x113e1f5d0]-(>=5)-|   (active, names: '|':_UIButtonBarButton:0x113e1f3f0 )>

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.
2022-07-30 13:06:44.928505+0200 MobileSafari[12732:867457] [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:0x28394c2d0 h=--& v=--& _UIToolbarContentView:0x113da38e0.width == 0   (active)>",
    "<NSLayoutConstraint:0x283944f00 H:|-(0)-[_UIButtonBarStackView:0x113d9e8d0]   (active, names: '|':_UIToolbarContentView:0x113da38e0 )>",
    "<NSLayoutConstraint:0x283944f50 H:[_UIButtonBarStackView:0x113d9e8d0]-(0)-|   (active, names: '|':_UIToolbarContentView:0x113da38e0 )>",
    "<NSLayoutConstraint:0x283943390 'TB_Leading_Leading' H:|-(8)-[_UIModernBarButton:0x113e20680'Done']   (active, names: '|':_UIButtonBarButton:0x113e20140 )>",
    "<NSLayoutConstraint:0x2839432a0 'TB_Trailing_Trailing' H:[_UIModernBarButton:0x113e20680'Done']-(0)-|   (active, names: '|':_UIButtonBarButton:0x113e20140 )>",
    "<NSLayoutConstraint:0x283942990 'UISV-canvas-connection' UILayoutGuide:0x2823db560'UIViewLayoutMarginsGuide'.leading == _UIButtonBarButton:0x113e1e6a0.leading   (active)>",
    "<NSLayoutConstraint:0x2839421c0 'UISV-canvas-connection' UILayoutGuide:0x2823db560'UIViewLayoutMarginsGuide'.trailing == _UIButtonBarButton:0x113e20140.trailing   (active)>",
    "<NSLayoutConstraint:0x283940000 'UISV-spacing' H:[_UIButtonBarButton:0x113e1e6a0]-(0)-[UIView:0x113e1f280]   (active)>",
    "<NSLayoutConstraint:0x283940280 'UISV-spacing' H:[UIView:0x113e1f280]-(0)-[_UIButtonBarButton:0x113e1f3f0]   (active)>",
    "<NSLayoutConstraint:0x2839404b0 'UISV-spacing' H:[_UIButtonBarButton:0x113e1f3f0]-(0)-[UIView:0x113e1ffd0]   (active)>",
    "<NSLayoutConstraint:0x283940730 'UISV-spacing' H:[UIView:0x113e1ffd0]-(0)-[_UIButtonBarButton:0x113e20140]   (active)>",
    "<NSLayoutConstraint:0x283944d70 'UIView-leftMargin-guide-constraint' H:|-(0)-[UILayoutGuide:0x2823db560'UIViewLayoutMarginsGuide'](LTR)   (active, names: '|':_UIButtonBarStackView:0x113d9e8d0 )>",
    "<NSLayoutConstraint:0x283944e10 'UIView-rightMargin-guide-constraint' H:[UILayoutGuide:0x2823db560'UIViewLayoutMarginsGuide']-(0)-|(LTR)   (active, names: '|':_UIButtonBarStackView:0x113d9e8d0 )>"
)

Will attempt to recover by breaking constraint 
<NSLayoutConstraint:0x2839432a0 'TB_Trailing_Trailing' H:[_UIModernBarButton:0x113e20680'Done']-(0)-|   (active, names: '|':_UIButtonBarButton:0x113e20140 )>

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.
2022-07-30 13:06:44.928961+0200 MobileSafari[12732:867457] [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:0x28394c370 h=--& v=--& _UIToolbarContentView:0x113da38e0.height == 0   (active)>",
    "<NSLayoutConstraint:0x283944fa0 V:|-(0)-[_UIButtonBarStackView:0x113d9e8d0]   (active, names: '|':_UIToolbarContentView:0x113da38e0 )>",
    "<NSLayoutConstraint:0x283944ff0 _UIButtonBarStackView:0x113d9e8d0.bottom == _UIToolbarContentView:0x113da38e0.bottom   (active)>",
    "<NSLayoutConstraint:0x283948460 UIImageView:0x113e1ee60.centerY == _UIModernBarButton:0x113e1e880.centerY   (active)>",
    "<NSLayoutConstraint:0x283941ea0 'IB_Baseline_Baseline' _UIModernBarButton:0x113e1e880.lastBaseline == UILayoutGuide:0x2823f89a0'UIViewLayoutMarginsGuide'.bottom   (active)>",
    "<NSLayoutConstraint:0x2839423a0 'IB_Top_Top' V:|-(>=0)-[_UIModernBarButton:0x113e1e880]   (active, names: '|':_UIButtonBarButton:0x113e1e6a0 )>",
    "<NSLayoutConstraint:0x283941770 'UIButtonBar.maximumAlignmentSize' _UIButtonBarButton:0x113e1e6a0.height == UILayoutGuide:0x2823db560'UIViewLayoutMarginsGuide'.height   (active)>",
    "<NSLayoutConstraint:0x283944dc0 'UIView-bottomMargin-guide-constraint' V:[UILayoutGuide:0x2823db560'UIViewLayoutMarginsGuide']-(0)-|   (active, names: '|':_UIButtonBarStackView:0x113d9e8d0 )>",
    "<NSLayoutConstraint:0x283943890 'UIView-bottomMargin-guide-constraint' V:[UILayoutGuide:0x2823f89a0'UIViewLayoutMarginsGuide']-(11)-|   (active, names: '|':_UIButtonBarButton:0x113e1e6a0 )>",
    "<NSLayoutConstraint:0x283944780 'UIView-topMargin-guide-constraint' V:|-(0)-[UILayoutGuide:0x2823db560'UIViewLayoutMarginsGuide']   (active, names: '|':_UIButtonBarStackView:0x113d9e8d0 )>"
)

Will attempt to recover by breaking constraint 
<NSLayoutConstraint:0x283948460 UIImageView:0x113e1ee60.centerY == _UIModernBarButton:0x113e1e880.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.
2022-07-30 13:06:44.929975+0200 MobileSafari[12732:867457] [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:0x28394c370 h=--& v=--& _UIToolbarContentView:0x113da38e0.height == 0   (active)>",
    "<NSLayoutConstraint:0x283944fa0 V:|-(0)-[_UIButtonBarStackView:0x113d9e8d0]   (active, names: '|':_UIToolbarContentView:0x113da38e0 )>",
    "<NSLayoutConstraint:0x283944ff0 _UIButtonBarStackView:0x113d9e8d0.bottom == _UIToolbarContentView:0x113da38e0.bottom   (active)>",
    "<NSLayoutConstraint:0x283948690 UIImageView:0x113e1fbb0.centerY == _UIModernBarButton:0x113e1f5d0.centerY   (active)>",
    "<NSLayoutConstraint:0x283942490 'IB_Baseline_Baseline' _UIModernBarButton:0x113e1f5d0.lastBaseline == UILayoutGuide:0x2823d0700'UIViewLayoutMarginsGuide'.bottom   (active)>",
    "<NSLayoutConstraint:0x2839424e0 'IB_Top_Top' V:|-(>=0)-[_UIModernBarButton:0x113e1f5d0]   (active, names: '|':_UIButtonBarButton:0x113e1f3f0 )>",
    "<NSLayoutConstraint:0x283943cf0 'UIButtonBar.maximumAlignmentSize' _UIButtonBarButton:0x113e1f3f0.height == UILayoutGuide:0x2823db560'UIViewLayoutMarginsGuide'.height   (active)>",
    "<NSLayoutConstraint:0x283944dc0 'UIView-bottomMargin-guide-constraint' V:[UILayoutGuide:0x2823db560'UIViewLayoutMarginsGuide']-(0)-|   (active, names: '|':_UIButtonBarStackView:0x113d9e8d0 )>",
    "<NSLayoutConstraint:0x2839413b0 'UIView-bottomMargin-guide-constraint' V:[UILayoutGuide:0x2823d0700'UIViewLayoutMarginsGuide']-(11)-|   (active, names: '|':_UIButtonBarButton:0x113e1f3f0 )>",
    "<NSLayoutConstraint:0x283944780 'UIView-topMargin-guide-constraint' V:|-(0)-[UILayoutGuide:0x2823db560'UIViewLayoutMarginsGuide']   (active, names: '|':_UIButtonBarStackView:0x113d9e8d0 )>"
)

Will attempt to recover by breaking constraint 
<NSLayoutConstraint:0x283948690 UIImageView:0x113e1fbb0.centerY == _UIModernBarButton:0x113e1f5d0.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.
2022-07-30 13:06:44.930300+0200 MobileSafari[12732:867457] [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:0x28394c370 h=--& v=--& _UIToolbarContentView:0x113da38e0.height == 0   (active)>",
    "<NSLayoutConstraint:0x283944fa0 V:|-(0)-[_UIButtonBarStackView:0x113d9e8d0]   (active, names: '|':_UIToolbarContentView:0x113da38e0 )>",
    "<NSLayoutConstraint:0x283944ff0 _UIButtonBarStackView:0x113d9e8d0.bottom == _UIToolbarContentView:0x113da38e0.bottom   (active)>",
    "<NSLayoutConstraint:0x283948870 UIButtonLabel:0x113e22620.centerY == _UIModernBarButton:0x113e20680'Done'.centerY + 1.5   (active)>",
    "<NSLayoutConstraint:0x283942f30 'TB_Baseline_Baseline' _UIModernBarButton:0x113e20680'Done'.lastBaseline == UILayoutGuide:0x2823d1c00'UIViewLayoutMarginsGuide'.bottom   (active)>",
    "<NSLayoutConstraint:0x283942e90 'TB_Top_Top' V:|-(>=0)-[_UIModernBarButton:0x113e20680'Done']   (active, names: '|':_UIButtonBarButton:0x113e20140 )>",
    "<NSLayoutConstraint:0x283942b20 'UIButtonBar.maximumAlignmentSize' _UIButtonBarButton:0x113e20140.height == UILayoutGuide:0x2823db560'UIViewLayoutMarginsGuide'.height   (active)>",
    "<NSLayoutConstraint:0x283944dc0 'UIView-bottomMargin-guide-constraint' V:[UILayoutGuide:0x2823db560'UIViewLayoutMarginsGuide']-(0)-|   (active, names: '|':_UIButtonBarStackView:0x113d9e8d0 )>",
    "<NSLayoutConstraint:0x2839430c0 'UIView-bottomMargin-guide-constraint' V:[UILayoutGuide:0x2823d1c00'UIViewLayoutMarginsGuide']-(11)-|   (active, names: '|':_UIButtonBarButton:0x113e20140 )>",
    "<NSLayoutConstraint:0x283944780 'UIView-topMargin-guide-constraint' V:|-(0)-[UILayoutGuide:0x2823db560'UIViewLayoutMarginsGuide']   (active, names: '|':_UIButtonBarStackView:0x113d9e8d0 )>"
)

Will attempt to recover by breaking constraint 
<NSLayoutConstraint:0x283948870 UIButtonLabel:0x113e22620.centerY == _UIModernBarButton:0x113e20680'Done'.centerY + 1.5   (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.
2022-07-30 13:06:47.746184+0200 MobileSafari[12732:867534] Detected stale pending counter; resetting to 0
2022-07-30 13:06:53.148376+0200 MobileSafari[12732:867457] [Snapshotting] Snapshotting a view (0x113d36160, _SFFluidProgressView) that is not in a visible window requires afterScreenUpdates:YES.
2022-07-30 13:07:00.909937+0200 MobileSafari[12732:867534] Detected stale pending counter; resetting to 0
2022-07-30 13:07:03.063678+0200 MobileSafari[12732:867534] [TabSnapshots] Image does not exist for identifier: 5925A47F-217C-4E6B-9C92-EECA81752F40
2022-07-30 13:07:03.063961+0200 MobileSafari[12732:867534] [TabSnapshots] Image does not exist for identifier: A55BE07F-BAF4-4C70-9632-8AC217E70C2F
2022-07-30 13:07:08.114716+0200 MobileSafari[12732:867457] [Snapshotting] Snapshotting a view (0x113d36160, _SFFluidProgressView) that is not in a visible window requires afterScreenUpdates:YES.
2022-07-30 13:07:10.661978+0200 MobileSafari[12732:868394] [default] LaunchServices: disconnect event interruption received for service com.apple.lsd.mapdb
2022-07-30 13:07:19.220150+0200 MobileSafari[12732:868394] [TabSnapshots] Image does not exist for identifier: 5925A47F-217C-4E6B-9C92-EECA81752F40
2022-07-30 13:07:19.220720+0200 MobileSafari[12732:868394] [TabSnapshots] Image does not exist for identifier: A55BE07F-BAF4-4C70-9632-8AC217E70C2F
2022-07-30 13:07:25.442342+0200 SWKeyboard[12871:869212] [Info] [KeymanEngine] > SWKeyboard Version: 1.0 Build: 1 PID: 12871
2022-07-30 13:07:25.442415+0200 SWKeyboard[12871:869212] [Info] [KeymanEngine] > XCGLogger Version: 6.1.0 - Level: Info
dyld[12871]: missing symbol called
2022-07-30 13:07:42.724760+0200 MobileSafari[12732:867552] [lifecycle] [u 7FC8EBC3-07A9-469C-BA34-A104A49A0DDF:m (null)] [ce.latin.project.keyboard(1.0)] Connection to plugin interrupted while in use.
2022-07-30 13:07:42.725377+0200 MobileSafari[12732:867552] [lifecycle] [u 7FC8EBC3-07A9-469C-BA34-A104A49A0DDF:m (null)] [ce.latin.project.keyboard(1.0)] Connection to plugin invalidated while in use.
2022-07-30 13:07:42.726258+0200 MobileSafari[12732:867552] [NSExtension] __plugin endUsing for '4F113463-62B8-49C9-8A77-B90D5A27A8CD' returned error: [u {public}@:m {public}@] [7FC8EBC3-07A9-469C-BA34-A104A49A0DDF((null))] endUsingRequest: called with unknown/expired request [ce.latin.project.keyboard]
Program ended with exit code: 9

To Reproduce

  1. Build the project using stable-15.0 branch
  2. Install carthage dependencies
    • carthage bootstrap --platform iOS --new-resolver --use-xcframeworks
    • carthage update --platform iOS --new-resolver --use-xcframeworks --no-use-binaries
  3. Choose KeymanEngine in embedded frameworks
  4. Choose team for both targets
  5. Find and replace group name
  6. Run the project on physical phone

Keyman for iPhone/iPad/Android:

Keyman Developer:


Keyboard

jahorton commented 2 years ago

[...] and install it on the physical iPhone 13 Pro with the latest system updates.

Just making a note here that this was noted for a physical device, not (yet?) for Simulator

Keyman for iPhone/iPad/Android:

  • Device: iPhone 13 Pro

  • OS: latest update

  • Keyman version 15.0

  • Target application: Safari

Could you be a bit more explicit here? Particularly, about the "latest update" part - we know that there's an iOS 16.0 beta out there, so it's unclear if you're talking about iOS 15.x or 16.0-beta. Also, as a heads-up, we currently don't plan to address beta-specific issues, as due to the nature of a beta, there's a higher chance of bugs on their end that may be fixed on their end before they fully release 16.0.

I've skimmed through the log messages you attached, and unfortunately... most, if not all, of those constraints are external to the KeymanEngine's system keyboard structure. There's a bunch of stuff about UIButtonBar in there - that's not used in any way, shape, or form by the framework, nor is UIButtonBarStackView. There's also a number of mentions of something "Capsule" in there - that's the first time I've even seen those class names, so far as I can recall.

Also, I'm noticing that you indicate only testing against Safari. I'm not going to downplay that Safari-incompatibility is an issue, as it's definitely an issue... but Safari is fairly complex, so it may help to test against other apps and double-check logs there as well; that should be less to sift through. Have you tried running the keyboard extension in simpler apps like Messenger, Reminders, or Notes? Issues there may yield further insights.

Since you didn't mention either way about it, I'd like to confirm - the project works fine when you launch it as a standard application? Your only issues are when attempting to provide a system keyboard?

Another detail I'd like to check - did you test against Simulator? Does the same issue occur there, or is it only occurring when running the sample app on an actual device?


The most glaring thing to me from the logs is this line:

dyld[13173]: missing symbol called

My understanding is that dyld is iOS's dynamic-loading system; it's an OS component that helps to link all parts of a program together. (Still wondering what the final 'd' stands for.) The best Windows analogy is that dyld resolves the iOS equivalent to DLLs. So, even that is technically outside of our app, but it's possible that something went off in the build's linking process that's affecting dyld. I think.

Unfortunately, Google searches against that aren't yielding any clearly-related results. Most of what I'm seeing seems to indicate that this may be related to build settings or to dependencies in some way. You may want to try doing a clean build and see if that helps, too.

FWIW, I just compiled KMSample2 locally and installed it on my personal iPhone SE 2 (iOS 15.5). I experienced zero problems once I got past the app permissions stuff from the start of item 2 on the referenced help page. I don't have access to an iPhone 13 Pro, so that's the closest attempt to a reproduction I can make at this time.

khashashin commented 2 years ago

Could you be a bit more explicit here? Particularly, about the "latest update"

First of all sorry for the misinformation, the device I've tried to run it on was iPhone 12 Pro with Software Version 15.5

Just to be clear I want to describe the steps I've done (Please note this all was done on newly cloned repository:

  1. Create new folder and switch to it
  2. Clone keyman repository
  3. Checkout stable-15.0 branch
  4. Download Keyman Engine from here particularly this file keyman-engine-ios-15.0.267.zip
  5. extract everything from this zip file
  6. replace samples folder under newly cloned repository with that from keyman-engine-ios-15.0.267.zip file.
  7. switch in to keyman/ios and run:
    • carthage bootstrap --platform iOS --new-resolver --use-xcframeworks (successful but still missing Sentry)
    • carthage update --platform iOS --new-resolver --use-xcframeworks --no-use-binaries (successful Sentry is now available)
  8. copy chechen_latin.kmp in to keyman/ios/samples/KMSample2/Keyboards
  9. Fix missing KeymanEngine dependency in xCode by choosing the folder image
  10. Find and replace group.KMSample with group.ChechenLatin
  11. Change Bundle Identifier for KMSample2 ce.latin.project for SWKeyboard ce.latin.project.keyboard
  12. Choose SWKeyboard as running apllication
  13. Run the project on Physical device (iPhone 12 Pro Software Version 15.5) by choosing Messanger
  14. Click and hold "globe" icon and choose Keyboard settings
  15. Add KMSample2 as system keyboard and turn on Allow Full Access
  16. Switch back in to Messanger and click and hold "globe" icon
  17. Choose KMSample2 Keyboard

Here is the resulting log output of the steps above:

2022-08-01 05:29:48.522165+0200 SWKeyboard[23127:1537425] [Info] [KeymanEngine] > SWKeyboard Version: 1.0 Build: 1 PID: 23127
2022-08-01 05:29:48.522205+0200 SWKeyboard[23127:1537425] [Info] [KeymanEngine] > XCGLogger Version: 6.1.0 - Level: Info
dyld[23127]: missing symbol called
(lldb) 
jahorton commented 2 years ago

Have you tried running the app first, before running the system keyboard?

Since you didn't mention either way about it, I'd like to confirm - the project works fine when you launch it as a standard application? Your only issues are when attempting to provide a system keyboard?

Also, in my experience, I usually need to run the app first through Xcode in order for it to force-update it in Simulator (or on a device) before I launch a debug run for the keyboard extension. (I often find it runs an old version otherwise.) Granted, you do seem to be running a bit before hitting the error, so this probably won't fix it, but it'd be helpful to make sure. Not doing so has caused confusing behavior for me in the past, so I'd like to eliminate that possibility here.

khashashin commented 2 years ago

@jahorton are the steps I described correct? for what is there build.sh inside ios/samples/KMSample2? It seems that performing these steps on different devices produces the same error.

jahorton commented 2 years ago

for what is there build.sh inside ios/samples/KMSample2?

That build.sh is for compiling it from scratch, without steps 4-6 and 11 above.

  1. Download Keyman Engine from here particularly this file keyman-engine-ios-15.0.267.zip

  2. extract everything from this zip file

  3. replace samples folder under newly cloned repository with that from keyman-engine-ios-15.0.267.zip file.

  4. Fix missing KeymanEngine dependency in xCode by choosing the folder

Instead, that script will build the KeymanEngine dependency in place from the repository itself, including the needed KeymanEngine.xcframework file. Admittedly, when I attempted a reproduction, this is what I relied upon. There's little chance that this would be the difference in whether or not I can reproduce your issue, though I suppose I should check to be sure.


Also, just to reiterate a question from an earlier response:

Another detail I'd like to check - did you test against Simulator? Does the same issue occur there, or is it only occurring when running the sample app on an actual device?

You mention trying this against multiple devices, but still haven't made mention of any tests run on simulated devices via Xcode. Simulator's usually a perfect match, but occasionally there are some major differences - and if there are, there's a chance that may provide us with a needed clue.

khashashin commented 2 years ago

You mention trying this against multiple devices, but still haven't made mention of any tests run on simulated devices via Xcode.

Unfortunately, there is not much difference, if any. I got this error when I ran it on the iPhone 12 Pro Simulator.

First I started KMSample Application and it installed without any problems and I was able to launch it and there were no problems or errors in the logs Then I closed the application and also the simulator and started SWKeyboard. The build was also successful and I was able to add the keyboard and assign permissions without any problems. But then when I selected KMSample Keyboard by long pressing the global icon, the Messanger app froze and I got the following error:

2022-08-03 04:12:03.466818+0200 SWKeyboard[42237:489681] Failed to inherit CoreMedia permissions from 42216: (null)
2022-08-03 04:12:03.472046+0200 SWKeyboard[42237:489508] [Info] [KeymanEngine] > SWKeyboard Version: 1.0 Build: 1 PID: 42237
2022-08-03 04:12:03.472219+0200 SWKeyboard[42237:489508] [Info] [KeymanEngine] > XCGLogger Version: 6.1.0 - Level: Info
dyld[42237]: missing symbol called
CoreSimulator 802.6.1 - Device: iPhone 12 Pro (2E0E8004-FF8B-4E9A-8D7F-B5F7C7855ABF) - Runtime: iOS 15.5 (19F70) - DeviceType: iPhone 12 Pro
(lldb) 
jahorton commented 2 years ago

OK... so I'm not getting the same error as you are, but I am getting errors when I link in a downloaded version of the framework instead of rebuilding it locally. Granted, this may be because I was using a 15.0 version while on the master (16.0 development) branch; I'll double-check that, but I don't expect a difference. (Not that this prevented a difference for the test I'm reporting about now!)

Update: I got the same results as before when testing against stable-15.0, but with the caveat that I reused the Carthage checkout from my master branch. (My development machine currently has an issue with one of the Carthage builds after a recent macOS update.) This may be a significant point because the error I see is in relation to one of our dependencies retrieved through Carthage... but it will take significant, otherwise-unrelated effort to resolve the issue preventing a more direct test.

khashashin commented 2 years ago

well it's not quite that what I did, I mean you probably have now higher versions of dependencies as of master branch. To get the same result and to be able to debug it, I'd recommend you to follow the steps. Since the docs of system keyboard development suggests to download the engine and not to build. I mean others would probably also download it and maybe get this error.

jahorton commented 2 years ago

OK... so I'm not getting the same error as you are, but I am getting errors when I link in a downloaded version of the framework instead of rebuilding it locally.

That's what happened when I followed the steps. Not a perfect repro, but it's something tangible on our end to investigate, at least.

khashashin commented 2 years ago

Where does build.sh save the KeymanEngine.xcframework file?

gushmazuko commented 2 years ago

Where does build.sh save the KeymanEngine.xcframework file?

The framework will be built to engine/KMEI/build/(Debug|Release)-universal/KeymanEngine.framework.

jahorton commented 2 years ago

The KMSample2 build script will place a copy of that within its own folder.

gushmazuko commented 2 years ago

@jahorton I have builded KeymanEngine via keyman/ios/samples/KMSample2/build.sh, нow I can run the app in the simulator without the above error.

Screen Shot 2022-08-03 at 05 46 50

But I ran into another problem, the keyboard does not see chechen_latin layout, which I added to the project following the documentation..

Error:

[Error] [KeymanEngine] [ResourceFileManager.swift:360] install(resourcesWithIDs:from:) > Resource with full ID {keyboard: {id = chechen_latin, languageID=ce}} not in package
gushmazuko commented 2 years ago
Screenshot ![Simulator Screen Shot - iPhone 12 - 2022-08-03 at 07 42 42](https://user-images.githubusercontent.com/34921843/182638274-28b9a745-51e4-4677-973f-90e88ab9796a.png) ![Simulator Screen Shot - iPhone 12 - 2022-08-03 at 07 43 28](https://user-images.githubusercontent.com/34921843/182638278-4541db96-336f-44cf-85ed-8f9b01d91688.png) ![Simulator Screen Shot - iPhone 12 - 2022-08-03 at 07 43 38](https://user-images.githubusercontent.com/34921843/182638281-8c992945-44ed-4a69-b2e9-3bf587e17be4.png) ![Simulator Screen Shot - iPhone 12 - 2022-08-03 at 07 44 50](https://user-images.githubusercontent.com/34921843/182638282-c144a4ae-4ea8-43a4-aeb2-868ca3978b11.png)
Logs ```logs 2022-08-03 07:40:08.885193-0700 KMSample2[89452:695787] [Info] [KeymanEngine] > KMSample2 Version: 1.0 Build: 1 PID: 89452 2022-08-03 07:40:08.885417-0700 KMSample2[89452:695787] [Info] [KeymanEngine] > XCGLogger Version: 6.1.0 - Level: Info 2022-08-03 07:40:08.959961-0700 KMSample2[89452:695787] [Info] [KeymanEngine] [SentryManager.swift:174] breadcrumbAndLog(crumb:logLevel:) > User keyboard list or current keyboard missing. Skipping migration. 2022-08-03 07:40:08.963546-0700 KMSample2[89452:695787] [Info] [KeymanEngine] [SentryManager.swift:174] breadcrumbAndLog(crumb:logLevel:) > Migrating from base directory: file:///Users/gushmazuko/Library/Developer/CoreSimulator/Devices/6C51173C-CAB9-413F-9C5E-102D113E5824/data/Containers/Shared/AppGroup/CE8EEFAD-D9DF-4831-BF83-9D6CE7C12738/keyman 2022-08-03 07:40:08.963982-0700 KMSample2[89452:695787] [Info] [KeymanEngine] [SentryManager.swift:174] breadcrumbAndLog(crumb:logLevel:) > No user keyboards to migrate 2022-08-03 07:40:08.966054-0700 KMSample2[89452:695787] [Info] [KeymanEngine] [SentryManager.swift:174] breadcrumbAndLog(crumb:logLevel:) > Prior engine version unknown; attepting to auto-detect. 2022-08-03 07:40:08.968599-0700 KMSample2[89452:695787] [Info] [KeymanEngine] [SentryManager.swift:174] breadcrumbAndLog(crumb:logLevel:) > Opening KMP from file:///Users/gushmazuko/Library/Developer/Xcode/DerivedData/KMSample2-hccctbgxsljgjlazfhrtlwunksff/Build/Products/Debug-iphonesimulator/KeymanEngine.framework/Keyman.bundle/Contents/Resources/sil_euro_latin.kmp 2022-08-03 07:40:09.018087-0700 KMSample2[89452:695787] [Info] [KeymanEngine] [SentryManager.swift:174] breadcrumbAndLog(crumb:logLevel:) > Opening KMP from file:///Users/gushmazuko/Library/Developer/CoreSimulator/Devices/6C51173C-CAB9-413F-9C5E-102D113E5824/data/Containers/Shared/AppGroup/CE8EEFAD-D9DF-4831-BF83-9D6CE7C12738/keyman/keyboards/sil_euro_latin/sil_euro_latin.kmp 2022-08-03 07:40:09.057546-0700 KMSample2[89452:695787] [Info] [KeymanEngine] [SentryManager.swift:174] breadcrumbAndLog(crumb:logLevel:) > Added keyboard with ID: sil_euro_latin and language code: en 2022-08-03 07:40:09.059211-0700 KMSample2[89452:695787] [Info] [KeymanEngine] [SentryManager.swift:174] breadcrumbAndLog(crumb:logLevel:) > Added keyboard with ID: sil_euro_latin and language code: en 2022-08-03 07:40:09.062137-0700 KMSample2[89452:695787] [Info] [KeymanEngine] [SentryManager.swift:174] breadcrumbAndLog(crumb:logLevel:) > Opening KMP from file:///Users/gushmazuko/Library/Developer/Xcode/DerivedData/KMSample2-hccctbgxsljgjlazfhrtlwunksff/Build/Products/Debug-iphonesimulator/KeymanEngine.framework/Keyman.bundle/Contents/Resources/nrc.en.mtnt.model.kmp 2022-08-03 07:40:09.086818-0700 KMSample2[89452:695787] [Info] [KeymanEngine] [SentryManager.swift:174] breadcrumbAndLog(crumb:logLevel:) > Opening KMP from file:///Users/gushmazuko/Library/Developer/CoreSimulator/Devices/6C51173C-CAB9-413F-9C5E-102D113E5824/data/Containers/Shared/AppGroup/CE8EEFAD-D9DF-4831-BF83-9D6CE7C12738/keyman/lexicalModels/nrc.en.mtnt/nrc.en.mtnt.model.kmp 2022-08-03 07:40:09.113021-0700 KMSample2[89452:695787] [Info] [KeymanEngine] [SentryManager.swift:174] breadcrumbAndLog(crumb:logLevel:) > Added lexicalModel with ID: nrc.en.mtnt and language code: en 2022-08-03 07:40:09.114752-0700 KMSample2[89452:695787] [Info] [KeymanEngine] [SentryManager.swift:174] breadcrumbAndLog(crumb:logLevel:) > Added lexicalModel with ID: nrc.en.mtnt and language code: en-us 2022-08-03 07:40:09.116488-0700 KMSample2[89452:695787] [Info] [KeymanEngine] [SentryManager.swift:174] breadcrumbAndLog(crumb:logLevel:) > Added lexicalModel with ID: nrc.en.mtnt and language code: en-ca 2022-08-03 07:40:09.117744-0700 KMSample2[89452:695787] [Info] [KeymanEngine] [SentryManager.swift:174] breadcrumbAndLog(crumb:logLevel:) > Added lexicalModel with ID: nrc.en.mtnt and language code: en 2022-08-03 07:40:09.206777-0700 KMSample2[89452:695787] [Warning] [KeymanEngine] [KeyboardScaleMap.swift:231] getDeviceDefaultKeyboardScale(forPortrait:onDevice:screenSize:asPhone:) > Keyboard scaling definition missing for device Simulator (iPhone13,2) 2022-08-03 07:40:09.372772-0700 KMSample2[89452:695787] [Debug] [KeymanEngine] [SentryManager.swift:174] breadcrumbAndLog(crumb:logLevel:) > Changing banner's alwaysShow property to false. objc[89452]: Class _PathPoint is implemented in both /Users/gushmazuko/Downloads/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS.simruntime/Contents/Resources/RuntimeRoot/System/Library/PrivateFrameworks/UIKitCore.framework/UIKitCore (0x115f9d658) and /Users/gushmazuko/Downloads/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS.simruntime/Contents/Resources/RuntimeRoot/System/Library/PrivateFrameworks/TextInputUI.framework/TextInputUI (0x131fbc690). One of the two will be used. Which one is undefined. objc[89452]: Class _PointQueue is implemented in both /Users/gushmazuko/Downloads/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS.simruntime/Contents/Resources/RuntimeRoot/System/Library/PrivateFrameworks/UIKitCore.framework/UIKitCore (0x115f9d630) and /Users/gushmazuko/Downloads/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS.simruntime/Contents/Resources/RuntimeRoot/System/Library/PrivateFrameworks/TextInputUI.framework/TextInputUI (0x131fbc6b8). One of the two will be used. Which one is undefined. 2022-08-03 07:40:09.408538-0700 KMSample2[89452:695787] [Warning] [KeymanEngine] [KeyboardScaleMap.swift:231] getDeviceDefaultKeyboardScale(forPortrait:onDevice:screenSize:asPhone:) > Keyboard scaling definition missing for device Simulator (iPhone13,2) 2022-08-03 07:40:09.409026-0700 KMSample2[89452:695787] [Warning] [KeymanEngine] [KeyboardScaleMap.swift:231] getDeviceDefaultKeyboardScale(forPortrait:onDevice:screenSize:asPhone:) > Keyboard scaling definition missing for device Simulator (iPhone13,2) 2022-08-03 07:40:09.410301-0700 KMSample2[89452:695787] [ViewportSizing] maximumViewportInset cannot be larger than frame 2022-08-03 07:40:09.410457-0700 KMSample2[89452:695787] [ViewportSizing] minimumViewportInset cannot be larger than frame 2022-08-03 07:40:09.410723-0700 KMSample2[89452:695787] [ViewportSizing] maximumViewportInset cannot be larger than frame 2022-08-03 07:40:09.410846-0700 KMSample2[89452:695787] [ViewportSizing] minimumViewportInset cannot be larger than frame 2022-08-03 07:40:09.411531-0700 KMSample2[89452:695787] [Warning] [KeymanEngine] [KeyboardScaleMap.swift:231] getDeviceDefaultKeyboardScale(forPortrait:onDevice:screenSize:asPhone:) > Keyboard scaling definition missing for device Simulator (iPhone13,2) 2022-08-03 07:40:09.412214-0700 KMSample2[89452:695787] [Warning] [KeymanEngine] [KeyboardScaleMap.swift:231] getDeviceDefaultKeyboardScale(forPortrait:onDevice:screenSize:asPhone:) > Keyboard scaling definition missing for device Simulator (iPhone13,2) 2022-08-03 07:40:09.412505-0700 KMSample2[89452:695787] [Warning] [KeymanEngine] [KeyboardScaleMap.swift:231] getDeviceDefaultKeyboardScale(forPortrait:onDevice:screenSize:asPhone:) > Keyboard scaling definition missing for device Simulator (iPhone13,2) 2022-08-03 07:40:09.413353-0700 KMSample2[89452:695787] [Warning] [KeymanEngine] [KeyboardScaleMap.swift:231] getDeviceDefaultKeyboardScale(forPortrait:onDevice:screenSize:asPhone:) > Keyboard scaling definition missing for device Simulator (iPhone13,2) 2022-08-03 07:40:09.413788-0700 KMSample2[89452:695787] [Warning] [KeymanEngine] [KeyboardScaleMap.swift:231] getDeviceDefaultKeyboardScale(forPortrait:onDevice:screenSize:asPhone:) > Keyboard scaling definition missing for device Simulator (iPhone13,2) 2022-08-03 07:40:09.414120-0700 KMSample2[89452:695787] [Warning] [KeymanEngine] [KeyboardScaleMap.swift:231] getDeviceDefaultKeyboardScale(forPortrait:onDevice:screenSize:asPhone:) > Keyboard scaling definition missing for device Simulator (iPhone13,2) 2022-08-03 07:40:09.414999-0700 KMSample2[89452:695787] [ViewportSizing] maximumViewportInset cannot be larger than frame 2022-08-03 07:40:09.415124-0700 KMSample2[89452:695787] [ViewportSizing] minimumViewportInset cannot be larger than frame 2022-08-03 07:40:09.415452-0700 KMSample2[89452:695787] [ViewportSizing] maximumViewportInset cannot be larger than frame 2022-08-03 07:40:09.415594-0700 KMSample2[89452:695787] [ViewportSizing] minimumViewportInset cannot be larger than frame 2022-08-03 07:40:09.416592-0700 KMSample2[89452:695787] [Info] [KeymanEngine] [SentryManager.swift:174] breadcrumbAndLog(crumb:logLevel:) > Storage.nonShared: using path file:///Users/gushmazuko/Library/Developer/CoreSimulator/Devices/6C51173C-CAB9-413F-9C5E-102D113E5824/data/Containers/Data/Application/C1627A46-3BDA-48A3-B991-32AB334AA158/Library/ 2022-08-03 07:40:09.420551-0700 KMSample2[89452:695787] [Info] [KeymanEngine] [SentryManager.swift:174] breadcrumbAndLog(crumb:logLevel:) > Deleting file:///Users/gushmazuko/Library/Developer/CoreSimulator/Devices/6C51173C-CAB9-413F-9C5E-102D113E5824/data/Containers/Data/Application/C1627A46-3BDA-48A3-B991-32AB334AA158/Library/keyman for copy from file:///Users/gushmazuko/Library/Developer/CoreSimulator/Devices/6C51173C-CAB9-413F-9C5E-102D113E5824/data/Containers/Shared/AppGroup/CE8EEFAD-D9DF-4831-BF83-9D6CE7C12738/keyman to file:///Users/gushmazuko/Library/Developer/CoreSimulator/Devices/6C51173C-CAB9-413F-9C5E-102D113E5824/data/Containers/Data/Application/C1627A46-3BDA-48A3-B991-32AB334AA158/Library/keyman 2022-08-03 07:40:09.449811-0700 KMSample2[89452:695787] CoreText note: Someone attempted to (un)register one or more fonts with CTFontManager using scope kCTFontManagerScopeNone. That's not a valid scope for (un)registration, so we'll use kCTFontManagerProcess instead. This message will not be logged again. 2022-08-03 07:40:09.451067-0700 KMSample2[89452:695787] [Info] [KeymanEngine] [FontManager.swift:89] registerFont(at:) > Registered font DejaVuSans at file:///Users/gushmazuko/Library/Developer/CoreSimulator/Devices/6C51173C-CAB9-413F-9C5E-102D113E5824/data/Containers/Shared/AppGroup/CE8EEFAD-D9DF-4831-BF83-9D6CE7C12738/keyman/keyboards/sil_euro_latin/DejaVuSans.ttf 2022-08-03 07:40:09.452207-0700 KMSample2[89452:695787] [Debug] [KeymanEngine] [SentryManager.swift:174] breadcrumbAndLog(crumb:logLevel:) > Changing banner's alwaysShow property to false. 2022-08-03 07:40:09.456266-0700 KMSample2[89452:695787] [Info] [KeymanEngine] [SentryManager.swift:174] breadcrumbAndLog(crumb:logLevel:) > Opening KMP from file:///Users/gushmazuko/Library/Developer/CoreSimulator/Devices/6C51173C-CAB9-413F-9C5E-102D113E5824/data/Containers/Bundle/Application/0FD2750A-4E03-4844-B4AD-EA5A594D118D/KMSample2.app/chechen_latin.kmp 2022-08-03 07:40:09.472852-0700 KMSample2[89452:695787] [Info] [KeymanEngine] [SentryManager.swift:174] breadcrumbAndLog(crumb:logLevel:) > Added keyboard with ID: chechen_latin and language code: ce-latn 2022-08-03 07:40:09.473792-0700 KMSample2[89452:695787] [Info] [KeymanEngine] [SentryManager.swift:174] breadcrumbAndLog(crumb:logLevel:) > Setting language: 2022-08-03 07:40:09.474434-0700 KMSample2[89452:695787] [None] [KeymanEngine] [SentryManager.swift:174] breadcrumbAndLog(crumb:logLevel:) > Keyboard stub built for chechen_latin 2022-08-03 07:40:09.474745-0700 KMSample2[89452:695787] [Info] [KeymanEngine] [KeymanWebViewController.swift:348] setKeyboard(_:) > Keyboard stub: {"KP":"chechen_latin","KI":"Keyboard_chechen_latin","KLC":"ce-latn","KN":"Chechen Latin","KL":"Chechen","KF":"file:\/\/\/Users\/gushmazuko\/Library\/Developer\/CoreSimulator\/Devices\/6C51173C-CAB9-413F-9C5E-102D113E5824\/data\/Containers\/Shared\/AppGroup\/CE8EEFAD-D9DF-4831-BF83-9D6CE7C12738\/keyman\/keyboards\/chechen_latin\/chechen_latin.js"} 2022-08-03 07:40:09.477172-0700 KMSample2[89452:695787] [Debug] [KeymanEngine] [TextView.swift:141] keyboardChanged(_:) > TextView: 140466335143936 setFont: .AppleSystemUIFont 2022-08-03 07:40:09.480174-0700 KMSample2[89452:695787] [Debug] [KeymanEngine] [TextView.swift:95] setKeymanDelegate(_:) > TextView: 140466335143936 keymanDelegate set to: Optional() 2022-08-03 07:40:09.501896-0700 KMSample2[89452:695787] [Debug] [KeymanEngine] [TextView.swift:259] textViewDidBeginEditing(_:) > TextView: 140466335143936 setFont: .AppleSystemUIFont 2022-08-03 07:40:09.502926-0700 KMSample2[89452:695787] [Debug] [KeymanEngine] [TextView.swift:261] textViewDidBeginEditing(_:) > TextView: 140466335143936 Became first responder. Value: Optional("‎") 2022-08-03 07:40:09.598422-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 -108; 0 216); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:40:09.599421-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 -108; 0 216); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:40:09.863342-0700 KMSample2[89452:695787] [Debug] [KeymanEngine] [SentryManager.swift:174] breadcrumbAndLog(crumb:logLevel:) > Changing banner's alwaysShow property to false. 2022-08-03 07:40:09.889840-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:40:09.890089-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:40:09.905086-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:40:09.905355-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:40:09.916906-0700 KMSample2[89452:695787] [Warning] [KeymanEngine] [KeyboardScaleMap.swift:231] getDeviceDefaultKeyboardScale(forPortrait:onDevice:screenSize:asPhone:) > Keyboard scaling definition missing for device Simulator (iPhone13,2) 2022-08-03 07:40:09.918959-0700 KMSample2[89452:695787] [Warning] [KeymanEngine] [KeyboardScaleMap.swift:231] getDeviceDefaultKeyboardScale(forPortrait:onDevice:screenSize:asPhone:) > Keyboard scaling definition missing for device Simulator (iPhone13,2) 2022-08-03 07:40:09.919430-0700 KMSample2[89452:695787] [Warning] [KeymanEngine] [KeyboardScaleMap.swift:231] getDeviceDefaultKeyboardScale(forPortrait:onDevice:screenSize:asPhone:) > Keyboard scaling definition missing for device Simulator (iPhone13,2) 2022-08-03 07:40:09.922912-0700 KMSample2[89452:695787] [Debug] [KeymanEngine] [Manager.swift:698] reachabilityChanged(_:) > Reachability changed to 'Reachable Via WiFi' 2022-08-03 07:40:12.156016-0700 KMSample2[89452:695787] [Info] [KeymanEngine] [SentryManager.swift:174] breadcrumbAndLog(crumb:logLevel:) > Loaded keyboard. 2022-08-03 07:40:12.157253-0700 KMSample2[89452:695787] [Info] [KeymanEngine] [SentryManager.swift:174] breadcrumbAndLog(crumb:logLevel:) > Setting initial keyboard. 2022-08-03 07:40:12.157540-0700 KMSample2[89452:695787] [Info] [KeymanEngine] [SentryManager.swift:174] breadcrumbAndLog(crumb:logLevel:) > Setting language: 2022-08-03 07:40:12.158069-0700 KMSample2[89452:695787] [None] [KeymanEngine] [SentryManager.swift:174] breadcrumbAndLog(crumb:logLevel:) > Keyboard stub built for chechen_latin 2022-08-03 07:40:12.158270-0700 KMSample2[89452:695787] [Info] [KeymanEngine] [KeymanWebViewController.swift:348] setKeyboard(_:) > Keyboard stub: {"KF":"file:\/\/\/Users\/gushmazuko\/Library\/Developer\/CoreSimulator\/Devices\/6C51173C-CAB9-413F-9C5E-102D113E5824\/data\/Containers\/Shared\/AppGroup\/CE8EEFAD-D9DF-4831-BF83-9D6CE7C12738\/keyman\/keyboards\/chechen_latin\/chechen_latin.js","KP":"chechen_latin","KI":"Keyboard_chechen_latin","KL":"Chechen","KLC":"ce-latn","KN":"Chechen Latin"} 2022-08-03 07:40:12.175513-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:40:12.175804-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:40:12.181976-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:40:12.182220-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:40:12.183952-0700 KMSample2[89452:695787] [Warning] [KeymanEngine] [KeyboardScaleMap.swift:231] getDeviceDefaultKeyboardScale(forPortrait:onDevice:screenSize:asPhone:) > Keyboard scaling definition missing for device Simulator (iPhone13,2) 2022-08-03 07:40:12.185158-0700 KMSample2[89452:695787] [Warning] [KeymanEngine] [KeyboardScaleMap.swift:231] getDeviceDefaultKeyboardScale(forPortrait:onDevice:screenSize:asPhone:) > Keyboard scaling definition missing for device Simulator (iPhone13,2) 2022-08-03 07:40:12.185610-0700 KMSample2[89452:695787] [Warning] [KeymanEngine] [KeyboardScaleMap.swift:231] getDeviceDefaultKeyboardScale(forPortrait:onDevice:screenSize:asPhone:) > Keyboard scaling definition missing for device Simulator (iPhone13,2) 2022-08-03 07:40:12.193604-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:40:12.193832-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:40:12.196299-0700 KMSample2[89452:695787] [Debug] [KeymanEngine] [TextView.swift:259] textViewDidBeginEditing(_:) > TextView: 140466335143936 setFont: .AppleSystemUIFont 2022-08-03 07:40:12.196670-0700 KMSample2[89452:695787] [Debug] [KeymanEngine] [TextView.swift:261] textViewDidBeginEditing(_:) > TextView: 140466335143936 Became first responder. Value: Optional("‎") 2022-08-03 07:40:12.197158-0700 KMSample2[89452:695787] [Debug] [KeymanEngine] [TextView.swift:141] keyboardChanged(_:) > TextView: 140466335143936 setFont: .AppleSystemUIFont 2022-08-03 07:40:12.197564-0700 KMSample2[89452:695787] [Debug] [KeymanEngine] [SentryManager.swift:174] breadcrumbAndLog(crumb:logLevel:) > Changing banner's alwaysShow property to false. 2022-08-03 07:40:12.197729-0700 KMSample2[89452:695787] [Debug] [KeymanEngine] [KeymanWebViewController.swift:433] setBannerImage(to:) > Banner image path: '.' 2022-08-03 07:42:39.726651-0700 KMSample2[89452:695787] [Debug] [KeymanEngine] [TextView.swift:176] dismissKeyboard() > TextView: 140466335143936 dismissing keyboard. Was first responder: true 2022-08-03 07:42:39.757030-0700 KMSample2[89452:695787] [Info] [KeymanEngine] [KeyboardSwitcherViewController.swift:30] viewDidLoad() > didLoad: KeyboardSwitcherViewController 2022-08-03 07:42:45.208617-0700 KMSample2[89452:695787] [Info] [KeymanEngine] [SentryManager.swift:174] breadcrumbAndLog(crumb:logLevel:) > Keyboard unchanged: 2022-08-03 07:42:45.226001-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:42:45.226356-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:42:45.393468-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:42:45.393820-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:42:45.397415-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:42:45.397632-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:42:45.401103-0700 KMSample2[89452:695787] [Debug] [KeymanEngine] [TextView.swift:259] textViewDidBeginEditing(_:) > TextView: 140466335143936 setFont: .AppleSystemUIFont 2022-08-03 07:42:45.401413-0700 KMSample2[89452:695787] [Debug] [KeymanEngine] [TextView.swift:261] textViewDidBeginEditing(_:) > TextView: 140466335143936 Became first responder. Value: Optional("‎") 2022-08-03 07:42:45.413506-0700 KMSample2[89452:695787] [Warning] [KeymanEngine] [KeyboardScaleMap.swift:231] getDeviceDefaultKeyboardScale(forPortrait:onDevice:screenSize:asPhone:) > Keyboard scaling definition missing for device Simulator (iPhone13,2) 2022-08-03 07:42:45.413975-0700 KMSample2[89452:695787] [Warning] [KeymanEngine] [KeyboardScaleMap.swift:231] getDeviceDefaultKeyboardScale(forPortrait:onDevice:screenSize:asPhone:) > Keyboard scaling definition missing for device Simulator (iPhone13,2) 2022-08-03 07:42:45.414270-0700 KMSample2[89452:695787] [Warning] [KeymanEngine] [KeyboardScaleMap.swift:231] getDeviceDefaultKeyboardScale(forPortrait:onDevice:screenSize:asPhone:) > Keyboard scaling definition missing for device Simulator (iPhone13,2) 2022-08-03 07:42:52.833581-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:42:52.833914-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:42:52.836903-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:42:52.837195-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:42:52.838263-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:42:52.838568-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:42:52.843105-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:42:52.843464-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:10.393636-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:10.393891-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:10.397101-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:10.397358-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:10.399354-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:10.399579-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:10.404360-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:10.404781-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:28.636345-0700 KMSample2[89452:695787] [HardwareKeyboard] -[UIApplication getKeyboardDevicePropertiesForSenderID:shouldUpdate:usingSyntheticEvent:], failed to fetch device property for senderID (778835616971358211) use primary keyboard info instead. 2022-08-03 07:43:28.637524-0700 KMSample2[89452:695787] [HardwareKeyboard] -[UIApplication getKeyboardDevicePropertiesForSenderID:shouldUpdate:usingSyntheticEvent:], failed to fetch device property for senderID (778835616971358211) use primary keyboard info instead. 2022-08-03 07:43:52.104348-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:52.104701-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:52.105476-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:52.105696-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:52.138374-0700 KMSample2[89452:695787] [Warning] [KeymanEngine] [KeyboardScaleMap.swift:231] getDeviceDefaultKeyboardScale(forPortrait:onDevice:screenSize:asPhone:) > Keyboard scaling definition missing for device Simulator (iPhone13,2) 2022-08-03 07:43:52.139110-0700 KMSample2[89452:695787] [Warning] [KeymanEngine] [KeyboardScaleMap.swift:231] getDeviceDefaultKeyboardScale(forPortrait:onDevice:screenSize:asPhone:) > Keyboard scaling definition missing for device Simulator (iPhone13,2) 2022-08-03 07:43:52.139467-0700 KMSample2[89452:695787] [Warning] [KeymanEngine] [KeyboardScaleMap.swift:231] getDeviceDefaultKeyboardScale(forPortrait:onDevice:screenSize:asPhone:) > Keyboard scaling definition missing for device Simulator (iPhone13,2) 2022-08-03 07:43:52.144772-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:52.145512-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:52.146496-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:52.146706-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:52.149805-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:52.150055-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:52.158790-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:52.159159-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:52.163845-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:52.164197-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:52.166438-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:52.166996-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:52.168252-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:52.168553-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:52.646026-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:52.646367-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:52.650522-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:52.650795-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:52.659695-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:52.660102-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:53.336544-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:53.337061-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:53.341535-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:53.341841-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:53.348457-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:53.348787-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:53.349603-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:53.350093-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:53.354277-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:53.354693-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:53.549641-0700 KMSample2[89452:695787] [Warning] [KeymanEngine] [KeyboardScaleMap.swift:231] getDeviceDefaultKeyboardScale(forPortrait:onDevice:screenSize:asPhone:) > Keyboard scaling definition missing for device Simulator (iPhone13,2) 2022-08-03 07:43:53.550056-0700 KMSample2[89452:695787] [Warning] [KeymanEngine] [KeyboardScaleMap.swift:231] getDeviceDefaultKeyboardScale(forPortrait:onDevice:screenSize:asPhone:) > Keyboard scaling definition missing for device Simulator (iPhone13,2) 2022-08-03 07:43:53.550449-0700 KMSample2[89452:695787] [Warning] [KeymanEngine] [KeyboardScaleMap.swift:231] getDeviceDefaultKeyboardScale(forPortrait:onDevice:screenSize:asPhone:) > Keyboard scaling definition missing for device Simulator (iPhone13,2) 2022-08-03 07:43:53.555996-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:53.556265-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:53.557197-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:53.557378-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:53.560501-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:53.560750-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:53.561776-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:53.562002-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:53.566499-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:53.566886-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:53.589405-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:43:53.589655-0700 KMSample2[89452:695787] API error: <_TtC12KeymanEngineP33_A040B68C5FC55309C542C2F291E86AC915CustomInputView: 0x7fc0dd207e10; baseClass = UIInputView; frame = (0 0; 390 250); autoresize = W+H; layer = > returned 0 width, assuming UIViewNoIntrinsicMetric 2022-08-03 07:44:06.515911-0700 KMSample2[89452:695787] Successfully load keyboard extensions Message from debugger: Terminated due to signal 9 ```
jahorton commented 2 years ago

@jahorton I have builded KeymanEngine via keyman/ios/samples/KMSample2/build.sh, нow I can run the app in the simulator without the above error.

Apologies that you've had to resort to this for now; please bear with us as we figure out why the workaround is currently necessary.

This line from your log doesn't give us much unexpected info, but for future reference, I'll highlight it just the same:

2022-08-03 07:40:09.474745-0700 KMSample2[89452:695787] [Info] [KeymanEngine] [KeymanWebViewController.swift:348] setKeyboard(_:) > Keyboard stub: {"KP":"chechen_latin","KI":"Keyboard_chechen_latin","KLC":"ce-latn","KN":"Chechen Latin","KL":"Chechen","KF":"file:\/\/\/Users\/gushmazuko\/Library\/Developer\/CoreSimulator\/Devices\/6C51173C-CAB9-413F-9C5E-102D113E5824\/data\/Containers\/Shared\/AppGroup\/CE8EEFAD-D9DF-4831-BF83-9D6CE7C12738\/keyman\/keyboards\/chechen_latin\/chechen_latin.js"}

For both our sanities, allow me to pretty-format the 'stub' this logged:

{
  "KP":"chechen_latin",
  "KI":"Keyboard_chechen_latin",
  "KLC":"ce-latn",
  "KN":"Chechen Latin",
  "KL":"Chechen",
  "KF":"file:///Users/gushmazuko/Library/Developer/CoreSimulator/Devices/6C51173C-CAB9-413F-9C5E-102D113E5824/data/Containers/Shared/AppGroup/CE8EEFAD-D9DF-4831-BF83-9D6CE7C12738/keyman/keyboards/chechen_latin/chechen_latin.js"
}

That matches pretty much what I'd expect; I see no font-related entries, so there shouldn't be any font issues at play here. (If there were, I could see the blank key-cap thing happening that way.)

I also find it very interesting that the key-previews are functioning perfectly despite the standard key caps not displaying. That's very odd.

I see that there was a recent PR for the chechen_latin keyboard and tried out the currently-deployed version, and I don't see the issue happening with it when I install it within the Keyman app. I figure the answer is "no changes / it should match", but just in case, have you made any changes to the chechen_latin.kmp you're working with, or should it match the current version in our repository here?

One more important observation from the screenshots - I see that the keyboard appears blank both in-app and as the system keyboard. I wouldn't expect there to be a difference; just making a note of that.

khashashin commented 2 years ago

And finally was able to run the keyboard, but using KeymanEngine, which was compiled and imported using the build.sh command Using the downloaded version still doesn't work.

I see that there was a recent PR for the chechen_latin keyboard and tried out the currently-deployed version, and I don't see the issue happening with it when I install it within the Keyman app. I figure the answer is "no changes / it should match", but just in case, have you made any changes to the chechen_latin.kmp you're working with, or should it match the current version in our repository here?

No, there wasn't any changes its the same keyboard. We assume that the problem with the display of characters on the keyboard keys is due to the fact that the simulator was run in a virtual environment (virtual machine in a virtual machine)