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
Be careful when using safe areas. As described in the [WWDC "UIKit: Apps for Every Size and Shape" video](https://masterer.apple.com/videos/play/wwdc2018-235/?time=328), the safe area insets will not be updated if your views exceeds the screen bounds. This is specially the case when using the `OverlayStyle.flexibleHeight`.
458
+
Be careful when using safe areas. As described in the [WWDC "UIKit: Apps for Every Size and Shape" video](https://masterer.apple.com/videos/play/wwdc2018-235/?time=328), the safe area insets will not be updated if your views exceeds the screen bounds. This is specially the case when using the `OverlayStyle.expandableHeight`: when the overlay exceeds the bottom screen limit, its safe area will not be updated.
458
459
459
-
The simpliest way to handle the safe area correctly is to compute your notch heights using the `safeAreaInsets`provided by the container and avoid the `safeAreaLayoutGuide`bottom anchor in your overlay:
460
+
The simpliest way to handle the safe area correctly is to compute your notch heights using the `safeAreaInsets`of the container and avoid the `safeAreaLayoutGuide`use in your overlay view:
This method does not reload the notch heights immediately. It only clears the current container's state. Because the number of notches may change, the container will use its target notch policy to determine where to go.
529
532
Call `moveOverlay(toNotchAt:animated:)` to override this behavior.
530
533
534
+
## SwiftUI
535
+
536
+
See [DynamicOverlay](https://github.com/faberNovel/DynamicOverlay)
0 commit comments