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
{{ message }}
This repository has been archived by the owner on Sep 2, 2020. It is now read-only.
UIKit doesn't guarantee specific order or paring for viewDidAppear and viewDidDisappear (as well as for most other appearance methods combinations). So they can't be used for proper management of the notification lifecycle and can cause over- or under-subscription problems in practice.
Why the safe area update shouldn't happen when view is 'disappeared' in the first place?
The text was updated successfully, but these errors were encountered:
This is great feedback! Thanks so much, @odnoletkov, for pointing it out. I'd gladly accept a PR that fixes this issue. Is that something you could provide? I might be able to do it myself but no guarantees on timeframe since I'm working this week :)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
viewDidAppear
andviewDidDisappear
(as well as for most other appearance methods combinations). So they can't be used for proper management of the notification lifecycle and can cause over- or under-subscription problems in practice.The text was updated successfully, but these errors were encountered: