|
Dear all, I am pretty new to the swift community so please apologize if this is a low-brainer. I have the following problem: I have an app that is throwing the following warning since I changed to a TabView Layout: "[TableView] Warning once only: UITableView was told to layout its visible cells and other contents without being in the view hierarchy (the table view or one of its superviews has not been added to a window). This may cause bugs by forcing views inside the table view to load and perform layout without accurate information (e.g. table view bounds, trait collection, layout margins, safe area insets, etc), and will also cause unnecessary performance overhead due to extra layout passes. Make a symbolic breakpoint at UITableViewAlertForLayoutOutsideViewHierarchy to catch this in the debugger and see what caused this to occur, so you can avoid this action altogether if possible, or defer it until the table view has been added to a window. Table view: <_TtC7SwiftUIP33_BFB370BA5F1BADDC9D83021565761A4925UpdateCoalescingTableView: 0x7fcc03055600; baseClass = UITableView; frame = (0 0; 414 852); clipsToBounds = YES; autoresize = W+H; gestureRecognizers = <NSArray: 0x600002e25500>; layer = <CALayer: 0x60000200bf20>; contentOffset: {0, 0}; contentSize: {414, 0}; adjustedContentInset: {0, 0, 83, 0}; dataSource: (null)>" I successfully re-created the problem with a straight-forward structure (see below). I would be very happy for any suggestions what's going on here: 1) Model
2) Single Tab View
3) Content View that includes two Tabs
The problem arises as soon as you click on tab 2 and then go back to tab 1. Many thanks in advance and best regards, Julian |
|
This is an internal Apple message, and not for us to worry about. We're all seeing the same message no matter what, so it's definitely for Apple to fix! |
|
SPONSORED Take the pain out of configuring and testing your paywalls. RevenueCat's all new Paywall Editor allow you to remotely configure your paywall view without any code changes or app updates. Sponsor Hacking with Swift and reach the world's largest Swift community! |
|
|
|
I encountered this today. I found that it occurs when going from a tab with a non-list view to a tab with a list view. If both tabs have list views the error is not reported. I would like to find a work around, because while I am learning it is very distacting to have the console filled with noise - hiding any important messages that might be scrolled away. I tend to be a bit obsessive about keeping my console empty of warnings, errors, and extraneous messages. Any help appreciated. |
|
|
|
I also noticed this same issue. I even took out the This is my
and this is the
and lastly, my
Is anyone else experiencing this behavior? It doesn't seem to matter how I construct the list. At first I was getting the collection of Lesson's using an ObservableObject and thought maybe that's what the issue was, so I replaced it with essentially a hard-coded single item (shown above) and it STILL does the same thing. Any help would be greatly appreciated! |
|
|
|
I get the ''This is an internal Apple message, and not for us to worry about. We're all seeing the same message no matter what, so it's definitely for Apple to fix!' Then I have a TextField and when I make the first character change to it I immediately get '[general] Connection to daemon was invalidated'. Google search for this gives no useful information. Then if I do one or more things the app dies with Thread 1: signal SIGABRT and no other output. So Is there at least a way to avoid hitting the 'internal Apple message' even its for Apple to fix? I'm guessing it causing the app in my case to crash soon after. |
|
@roblack, I dealt with the same issue when using diffable data source. I realized I wasn't setting tableView.dataSource = myDiffableDataSource. After I did that, the error went away! |
|
I encountered this error. It disappeared after I tracked down and eliminated a nested NavigationView. |
SPONSORED Take the pain out of configuring and testing your paywalls. RevenueCat's all new Paywall Editor allow you to remotely configure your paywall view without any code changes or app updates.
Sponsor Hacking with Swift and reach the world's largest Swift community!
This topic has been closed due to inactivity, so you can't reply. Please create a new topic if you need to.
All interactions here are governed by our code of conduct.
Link copied to your pasteboard.