I wrote an app known as SwiftUI View Lifecycle. The app permits you to observe how totally different SwiftUI constructs and containers have an effect on a view’s lifecycle, together with the lifetime of its state and when
onAppear will get known as. The code for the app is on GitHub. It may be constructed for iOS and macOS.
After we write SwiftUI code, we assemble a view tree that consists of nested view values. Situations of the view tree are ephemeral: SwiftUI always destroys and recreates (components of) the view tree because it processes state modifications.
The view tree serves as a blueprint from which SwiftUI creates a second tree, which represents the precise view “objects” which might be “on display screen” at any given time (the “objects” may very well be precise
NSView objects, but additionally different representations; the precise that means of “on display screen” can differ relying on context). Chris Eidhof likes to name this second tree the render tree (the hyperlink factors to a 3 minute video the place Chris demonstrates this duality, extremely beneficial).
The render tree persists throughout state modifications and is utilized by SwiftUI to determine view id. When a state change causes a change in a view’s worth, SwiftUI will discover the corresponding view object within the render tree and replace it in place, fairly than recreating a brand new view object from scratch. That is after all key to creating SwiftUI environment friendly, however the render tree has one other necessary operate: it controls the lifetimes of views and their state.
We will outline a view’s lifetime because the timespan it exists within the render tree. The lifetime begins with the insertion into the render tree and ends with the elimination. Importantly, the lifetime extends to view state outlined with
@StateObject: when a view will get faraway from the render tree, its state is misplaced; when the view will get inserted once more later, the state will probably be recreated with its preliminary worth.
The SwiftUI View Lifecycle app tracks three lifecycle occasions for a view and shows them as timestamps:
- @State = when the view’s state was created (equal to the beginning of the view’s lifetime)
- onAppear = when
onAppearwas final known as
- onDisappear = when
onDisappearwas final known as
The app permits you to observe these occasions in numerous contexts. As you click on your means via the examples, you’ll discover that the timing of those occasions modifications relying on the context a view is embedded in. For instance:
elseassertion creates and destroys its youngster views each time the situation modifications; state shouldn’t be preserved.
ScrollVieweagerly inserts all of its kids into the render tree, no matter whether or not they’re contained in the viewport or not. All kids seem immediately and by no means disappear.
Checklistwith dynamic content material (utilizing
ForEach) lazily inserts solely the kid views which might be at present seen. However as soon as a baby view’s lifetime has began, the record will hold its state alive even when it will get scrolled offscreen once more.
onDisappearget known as repeatedly as views are scrolled into and out of the viewport.
onDisappearas views are pushed and popped. State for father or mother ranges within the stack is preserved when a baby view is pushed.
TabViewbegins the lifetime of all youngster views immediately, even the non-visible tabs.
onDisappearget known as repeatedly because the consumer switches tabs, however the tab view retains the state alive for all tabs.
Listed below are a number of classes to remove from this:
- Completely different container views could have totally different efficiency and reminiscence utilization behaviors, relying on how lengthy they hold youngster views alive.
onAppearisn’t essentially known as when the state is created. It may well occur later (however by no means earlier).
onAppearcould be known as a number of instances in some container views. Should you want a aspect impact to occur precisely as soon as in a view’s lifetime, contemplate writing your self an
onFirstAppearhelper, as proven by Ian Eager and Jordan Morgan in Operating Code Solely As soon as in SwiftUI (2022-11-01).
I’m certain you’ll discover extra fascinating tidbits while you play with the app. Suggestions is welcome!