#SwiftUI, the size class is set to regular when the iPad app enters background. WTF. Apparently, it’s not a bug, as the iPad needs to take snapshots. Good luck in SwiftUI keeping the whole view hierarchy state when transitioning between a sidebar (custom) and a tabbar. This thing was built only with the NavigationSplitView in mind. Very stupid you can’t disable it.
@dimillian Another approach could be to only use a TabView, and hide the tab bar when the size class is compact. This can be done easily with introspect. Tab state is managed by tabview, which also makes it easier to keep state of all tabs compared to using a switch (And in Ice Cubes case, probably also faster as the views don’t need to be rebuilt on a tab change).
Tested the idea out real quick, seems to work great
@wouter01 Nice side effect is that swapping tabs is now much faster as it use the UITabViewController backed thing instead of my horrible ZStack view stacking + opacity.
@dimillian it is incredible that since the beginning of iPad some kind of Split View/navigator is always pushed down our throats but it has few customisations and practical use after you leave the prototype version.
@dimillian oh I did not know that! I’ll check how it goes for my apps. Have you thought about using SceneStorage to persist and restore the state? This is what I use for apps that can be resized on iPad (thus using either a NavigationSplitView or a NavigationStack based on the horizontalClass).
@dimillian oh yeah, I know, it sucks performance wise… but we don’t have any other options right now afaik, until Apple finally fixes the NavigationSplitView component. When they will focus less on visionOS and more on the other platforms?!
@alpennec as it was since the beginning. I've made the slide over change very recently. A solution could be to build a custom tab bar. Display the sidebar at the bottom.
Add comment