Safe area insets are not respected when setting overrideUserInterfaceStyle on a MessageView in iOS 17 about swiftmessages HOT 3 OPEN

@jmarr I appreciate the detailed writeup. I'm unlikely to look at this anytime soon given that it is an obscure problem and you have a workaround. Hopefully it will resolve itself in a future version of iOS.

from swiftmessages.

@wtmoose Thanks and yeah, that's totally understandable. I mostly wanted to post it here in case anyone else runs into the issue, since it took a while to discover thatoverrideUserInterfaceStyle was triggering it.

In our app the issue was much more noticeable because we have a container view with a bottom bar that sets additionalSafeAreaInsets on its children, so the message was appearing entirely behind the bar.

And yes, hopefully the underlying issue will be resolved in an iOS update, though I did verify it's still happening on the latest iOS 17.1 beta.

from swiftmessages.

I just discovered that this issue also occurs when showing a message from a view controller that's being presented.

1. Build and run this project on a device with safe areas.
2. Tap Show Message and note that the message respects the safe area.
3. Tap Present View Controller.
4. Tap Show Message and note that the message overlaps the safe area.

The issue doesn't occur if I change the presentationContext from .viewController(self) to .window(windowLevel: .normal)

In stepping through the code, after calling container.layoutIfNeeded() on line 100 of TopBottomAnimation.swift, the frame of container is changed and no longer overlapping the safe area, so the safe area isn't taken into account by the call to adjustMargins, just like when overrideUserInterfaceStyle was used.

from swiftmessages.