memory leak with addChild() about xcoordinator-example HOT 3 OPEN

I'm not sure I understand what you mean - can you elaborate on how adding another protocol will solve memory issues? A method would need to be called at some point - that cannot easily be done. An alternative would be to enable overriding of canBeRemovedAsChild. Feel free to open a MR once you have a working version, so we can start a discussion on how to solve this best.

from xcoordinator-example.

The leak in AboutCoordinator can easily be fixed by overriding the viewController property with:

override var viewController: UIViewController! {
    rootViewController.viewControllers.first { $0 is AboutViewController }
}

I will open a MR today for that.

from xcoordinator-example.

Me too. Even build with XCoordinator v2.2.0, the child coordinator can't be removed when clicked the navigation bar back button. I have tried the way from @pauljohanneskraft , it works.

from xcoordinator-example.