I managed to free the memory…
The reason why only making the
unowned didn’t work was because it was only half of the solution. The
navigation was being retained elsewhere… To solve it, simply make the
navigation unowned but inside the
Hello again Dama,
Hope you are doing well and votes of success for 2019!
After a little more research, I found that the retaining cycle is related to the completion within each Wireframe. Sorry for taking so long to answer but I was only able to look at this again today.
Great article! I think this is actually a really good way of not losing the screens context. We really get an overview of the paths the users may take during the application usage as we do of the data that is passed between them.