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
You're right: there are no weak references in the project.
Actually there many strong reference cycles, I found a few just by looking at the AppDependencies.swift file (e.g. ListPresenter and ListWireframe reference to each other, same for ListPresenter and ListInteractor, and AddWireframe and AddPresenter).
Some of these references (most of them) are optionals, but they still are strong references.
The ideal would be to have the ListViewController to strong reference the ListPresenter, and all the other references to ListPresenterweak (from ListWireFrame, ListInteractor, and AddPresenter).
Therefore when the VC is deinitialized you have a chain-reaction where every other part of the VIPER architecture for that view is deinitialized.
The problem in this project is that the ListviewControlleris initializedafter the dependencies are already set up, therefore what I suggest above is not implementable without some code changes (that are more than just adding weak here and there).
Why there are strong delegate references ??
I get my class nil when setting weak delegate . But delegate should be weak , isn't it ?
The text was updated successfully, but these errors were encountered: