You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using a popover presented from a button in a nav bar. It works fine, but there's an issue on iPad. After the popover is presented, if you resize the app, the content view no longer resizes accordingly. I made a few simple changes to the example app that demonstrates this. Here is a screenshot and movie that shows the issue. Also attached is a modified RootView.swift with my changes. They are marked with "// MAK".
Hey @markkrenek, thanks for well-described bug report.
I was able to reproduce the issue, however, I believe this is the system SwiftUI issue. You can see on the screenshot below that it's not just ContentView that is incorrectly resized, it's the whole UIHostingView and its view controller. Which makes me think that SwiftUI.NavigationView somehow incorrectly handles window scene resizing in this case. You can submit bug report to apple and let's see what they answer.
Excellent! This indeed solves the issue. I've tried multiple libs like this but all get it wrong when presenting from a nav bar. Detached view controller complaints from the runtime. My main goal was to use a popover and have it convert to a half size sheet in compact environments - the standard popover always uses a fullscreen sheet in this case. Being able to set adaptiveSheetProperties for the popover is perfect. Thanks for the solution.
I'm using a popover presented from a button in a nav bar. It works fine, but there's an issue on iPad. After the popover is presented, if you resize the app, the content view no longer resizes accordingly. I made a few simple changes to the example app that demonstrates this. Here is a screenshot and movie that shows the issue. Also attached is a modified RootView.swift with my changes. They are marked with "// MAK".
Simulator.Screen.Recording.-.iPad.mov
RootView.txt
The text was updated successfully, but these errors were encountered: