If you present a UIViewController and from that screen you make a step which change flow will create a memory leak by holding the NavigationController with full stack of ViewController within it. That flow is deallocated but the navigation controller and other view controller still exists on memory.
Protocol oriented, Cocoa UI abstractions based library that helps to handle view controllers composition, navigation and deep linking tasks in the iOS application. Can be used as the universal replacement for the Coordinator pattern.
All are private (implementation detail). The setup should be called in init (for views) or in viewDidLoad (for view controllers). The update should be called in the viewModels didSet. The setupViewModelBindings should be called (if even existent) at the beginning of the setup method. Provide a full example.
If you present a UIViewController and from that screen you make a step which change flow will create a memory leak by holding the NavigationController with full stack of ViewController within it. That flow is deallocated but the navigation controller and other view controller still exists on memory.