Chapter 15: Lots of warnings

I’m following the text, adding to the starter/HNReader.xcodeproj

Looking for the first numbers to appear when adding .onAppear method, I find my debug output cluttered with lots of warnings (I’m on Xcode Version 13.2.1 (13C100), M1)

2022-01-21 17:54:29.419932+0100 HNReader[49602:1200988] [SceneConfiguration] Info.plist configuration "(no name)" for UIWindowSceneSessionRoleApplication contained UISceneDelegateClassName key, but could not load class with name "HNReader.SceneDelegate".
2022-01-21 17:54:29.420160+0100 HNReader[49602:1200988] [SceneConfiguration] Info.plist configuration "(no name)" for UIWindowSceneSessionRoleApplication contained UISceneDelegateClassName key, but could not load class with name "HNReader.SceneDelegate".
2022-01-21 17:54:29.420393+0100 HNReader[49602:1200988] [SceneConfiguration] Info.plist configuration "(no name)" for UIWindowSceneSessionRoleApplication contained UISceneDelegateClassName key, but could not load class with name "HNReader.SceneDelegate".
2022-01-21 17:54:29.459626+0100 HNReader[49602:1200988] [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:0x60000079e3f0 'BIB_Trailing_CB_Leading' H:[_UIModernBarButton:0x1530160c0]-(6)-[_UIModernBarButton:0x153013a20'0 Stories']   (active)>",
    "<NSLayoutConstraint:0x60000079e440 'CB_Trailing_Trailing' _UIModernBarButton:0x153013a20'0 Stories'.trailing <= _UIButtonBarButton:0x153013640.trailing   (active)>",
    "<NSLayoutConstraint:0x60000079f110 'UINav_static_button_horiz_position' _UIModernBarButton:0x1530160c0.leading == UILayoutGuide:0x600001de5dc0'UIViewLayoutMarginsGuide'.leading   (active)>",
    "<NSLayoutConstraint:0x60000079f160 'UINavItemContentGuide-leading' H:[_UIButtonBarButton:0x153013640]-(6)-[UILayoutGuide:0x600001de5ce0'UINavigationBarItemContentLayoutGuide']   (active)>",
    "<NSLayoutConstraint:0x60000079c230 'UINavItemContentGuide-trailing' UILayoutGuide:0x600001de5ce0'UINavigationBarItemContentLayoutGuide'.trailing == _UINavigationBarContentView:0x153006ab0.trailing   (active)>",
    "<NSLayoutConstraint:0x6000007919a0 'UIView-Encapsulated-Layout-Width' _UINavigationBarContentView:0x153006ab0.width == 0   (active)>",
    "<NSLayoutConstraint:0x60000079c5f0 'UIView-leftMargin-guide-constraint' H:|-(8)-[UILayoutGuide:0x600001de5dc0'UIViewLayoutMarginsGuide'](LTR)   (active, names: '|':_UINavigationBarContentView:0x153006ab0 )>"
)

Will attempt to recover by breaking constraint 
<NSLayoutConstraint:0x60000079e3f0 'BIB_Trailing_CB_Leading' H:[_UIModernBarButton:0x1530160c0]-(6)-[_UIModernBarButton:0x153013a20'0 Stories']   (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-01-21 17:54:29.460134+0100 HNReader[49602:1200988] [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:0x60000079e3a0 'BIB_Leading_Leading' H:|-(0)-[_UIModernBarButton:0x1530160c0]   (active, names: '|':_UIButtonBarButton:0x153013640 )>",
    "<NSLayoutConstraint:0x60000079f110 'UINav_static_button_horiz_position' _UIModernBarButton:0x1530160c0.leading == UILayoutGuide:0x600001de5dc0'UIViewLayoutMarginsGuide'.leading   (active)>",
    "<NSLayoutConstraint:0x60000079f160 'UINavItemContentGuide-leading' H:[_UIButtonBarButton:0x153013640]-(6)-[UILayoutGuide:0x600001de5ce0'UINavigationBarItemContentLayoutGuide']   (active)>",
    "<NSLayoutConstraint:0x60000079c230 'UINavItemContentGuide-trailing' UILayoutGuide:0x600001de5ce0'UINavigationBarItemContentLayoutGuide'.trailing == _UINavigationBarContentView:0x153006ab0.trailing   (active)>",
    "<NSLayoutConstraint:0x6000007919a0 'UIView-Encapsulated-Layout-Width' _UINavigationBarContentView:0x153006ab0.width == 0   (active)>",
    "<NSLayoutConstraint:0x60000079c5f0 'UIView-leftMargin-guide-constraint' H:|-(8)-[UILayoutGuide:0x600001de5dc0'UIViewLayoutMarginsGuide'](LTR)   (active, names: '|':_UINavigationBarContentView:0x153006ab0 )>"
)

Will attempt to recover by breaking constraint 
<NSLayoutConstraint:0x60000079e3a0 'BIB_Leading_Leading' H:|-(0)-[_UIModernBarButton:0x1530160c0]   (active, names: '|':_UIButtonBarButton:0x153013640 )>

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-01-21 17:54:29.460478+0100 HNReader[49602:1200988] [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:0x60000079d8b0 UIView:0x15301b080.trailing == _UIBackButtonMaskView:0x153015060.trailing   (active)>",
    "<NSLayoutConstraint:0x60000079e9e0 'Mask_Trailing_Trailing' _UIBackButtonMaskView:0x153015060.trailing == _UIButtonBarButton:0x153013640.trailing   (active)>",
    "<NSLayoutConstraint:0x60000079eb20 'MaskEV_Leading_BIB_Trailing' H:[_UIModernBarButton:0x1530160c0]-(0)-[UIView:0x15301b080]   (active)>",
    "<NSLayoutConstraint:0x60000079f110 'UINav_static_button_horiz_position' _UIModernBarButton:0x1530160c0.leading == UILayoutGuide:0x600001de5dc0'UIViewLayoutMarginsGuide'.leading   (active)>",
    "<NSLayoutConstraint:0x60000079f160 'UINavItemContentGuide-leading' H:[_UIButtonBarButton:0x153013640]-(6)-[UILayoutGuide:0x600001de5ce0'UINavigationBarItemContentLayoutGuide']   (active)>",
    "<NSLayoutConstraint:0x60000079c230 'UINavItemContentGuide-trailing' UILayoutGuide:0x600001de5ce0'UINavigationBarItemContentLayoutGuide'.trailing == _UINavigationBarContentView:0x153006ab0.trailing   (active)>",
    "<NSLayoutConstraint:0x6000007919a0 'UIView-Encapsulated-Layout-Width' _UINavigationBarContentView:0x153006ab0.width == 0   (active)>",
    "<NSLayoutConstraint:0x60000079c5f0 'UIView-leftMargin-guide-constraint' H:|-(8)-[UILayoutGuide:0x600001de5dc0'UIViewLayoutMarginsGuide'](LTR)   (active, names: '|':_UINavigationBarContentView:0x153006ab0 )>"
)

Will attempt to recover by breaking constraint 
<NSLayoutConstraint:0x60000079d8b0 UIView:0x15301b080.trailing == _UIBackButtonMaskView:0x153015060.trailing   (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-01-21 17:54:29.738624+0100 HNReader[49602:1201186] [boringssl] boringssl_metrics_log_metric_block_invoke(151) Failed to log metrics
1
2
2022-01-21 17:54:30.119436+0100 HNReader[49602:1201186] [boringssl] boringssl_metrics_log_metric_block_invoke(151) Failed to log metrics
2022-01-21 17:54:30.129628+0100 HNReader[49602:1201186] [boringssl] boringssl_metrics_log_metric_block_invoke(151) Failed to log metrics
2022-01-21 17:54:30.131681+0100 HNReader[49602:1201186] [boringssl] boringssl_metrics_log_metric_block_invoke(151) Failed to log metrics
2022-01-21 17:54:30.133458+0100 HNReader[49602:1201186] [boringssl] boringssl_metrics_log_metric_block_invoke(151) Failed to log metrics
2022-01-21 17:54:30.134930+0100 HNReader[49602:1201186] [boringssl] boringssl_metrics_log_metric_block_invoke(151) Failed to log metrics
3
4
5
6
7
8
9

First thing I see is that there’s an Info.plist which I don’t have when I start a new SwiftUI project from scratch. Removing it only (thought about left overs from non SwiftUI version due to SceneDelegator class, etc.) “solves” the first warning, but keeps me from installing the app on any simulator device because a bundle identifier is missing (although one is given in the corresponding target field).
Since I’m starting again with Xcode dev after some time I wonder what’s going on and how to fix it. I can’t really work with this noise in the debug window.
Any clues?

Thanks for the help.

I solved the first one by creating a new project with SwiftUI, copying all the files instead of Info.plist.
Solved the UI warnings by adding

.navigationViewStyle(StackNavigationViewStyle())

to the NavigationView in ReaderView.swift.

No clue about the [boringssl] warnings. Couldn’t find helpful information on those.

Interestingly I see differing amount of nubers being printed (sometimes up to 7, sometimes up to 5) so I’m not sure whether calls to external API are also dropped here.