iPadOS 17.7.7

I'm struggling to find the correct way to use the new Sidebar on iPadOS with Split View Controllers (or NavigationView as it's called in SwiftUI). If you want a Sidebar with a layout like so: Sidebar -> Main View -> Detail View It can be achieved with the following code: NavigationView { ttSidebarView() ttText(Main) ttText(Detail) } Then SwiftUI will always expect that the main and detail views can be filled. Ideally, for some but not all of the side bar items, I'd like a structure of: Sidebar -> Main View Note the detail view is missing, so ideally the Main View would take up the remainder of the screen. This is not what happens currently - SwiftUI still leaves a lot of space for a detail view. By writing the initial Navigation View like so we lose the ability to have that detail even for the views that want it: NavigationView { ttSidebarView() ttText(Main) } I've tried doing things such as using the modifier .navigationViewStyle(StackNavigationViewStyle()) specifically on the detail view t

I used standard font styles in an iOS app. For example .font(.headline). I hoped that developing this way would allow the adoption of the app to other platforms, relatively easy. However, when trying to run for iPadOS, the text did not increase in size to occupy the more abundant space offered by larger screen, but it actually shrank. Overall, the app does not look great automatically. Why does it happen? What is the best practice for cross platform development with SwiftUI (with regards to font sizes). I want to make as little as possible human interface design decisions on my own and just let SwiftUI take care of everything. (But I also want the results to look as Apple would consider great looking)

Problem - any time I open up keyboard in any app, keyboard floats over page on the middle of the app blocking form input and is just a bad experience. Usage blocker. Has anyone seen this? very debilitating. ipad mini 6 ipados 1.16.4 - at the latest update as of writing this post. help! see in screenshot of this page the keyboard is right in middle of screen blocking actual input.