Because of deep links or state restoration you have to push dozens of view controllers onto a UINavigationController in a row. What goes wrong if you just do that?
Pushing in a loop makes the animations overlap and break the UI, every VC on the stack stays in memory until it's popped, and the moment anything touches a view, even offscreen screens get loaded.
iOS system designShort answerIntro
A travel booking app goes list → detail → booking. For each screen, how do you decide…
#memory #navigation
Performance and debuggingShort answerAdvanced
Users say "the app just closes," but Crashlytics has nothing. If you suspect…
#memory
Performance and debuggingShort answerAdvanced
A photo editing app gets frequent memory warnings and sometimes gets killed. In what…
#memory
Performance and debuggingShort answerAdvanced
Besides retain cycle leaks, what other kinds of memory bugs do you run into on iOS? And…
#memory