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
@lonsky thanks for the bug report. You’re right, it sounds like the safe area is somehow not being updated for these views that are offscreen. I’ll look into it when I get a chance.
One thing I’d be interested in seeing is whether the safeAreaInsetsDidChange() method is called on each view in the stack view, if so which views, and what the value of the safe area insets are after each call.
Depending on what the result of this is, perhaps AloeStackView could attempt to update each view when the safe area changes (specifically the ones that are offscreen that are not being updated). I’m not sure exactly what that would look like, but it could be an approach worth exploring.
Unfortunately I only have phone access at the moment, no computer access until next week, so I cannot debug this until then. Please feel free to share any details you learn in the meantime though. Thanks again!
There is a problem with safe area insets for embedded views (viewControllers).
How to reproduce (you need phone or simulator with a notch):
See, that safe area is correct for those views that were visible and incorrect for those that weren't.
Seems like it's UIKit bug, but maybe you have a workaround for this issue.
the only solution i've found was inspired by this answer on SO:
https://stackoverflow.com/questions/46505999/using-a-stack-view-in-a-scroll-view-and-respecting-safe-area-insets?rq=1
but in this case you don't have TableView-like behaviour when background takes full width and content is located inside the safe area
The text was updated successfully, but these errors were encountered: