search

cforlando / orlando-walking-tours-ios

Orlando Walking Tours - iOS Application
MIT License
8 stars 14 forks source link

Fixed a memory issue due to improper view controller management #104

Closed WERUreo closed 7 years ago

WERUreo commented 7 years ago

It was brought to my attention that transitioning from the CurrentTour view controller back to the Dashboard view controller was causing the memory used by the app to continually increase. It turns out, when the Home button on the CurrentTour view controller was tapped, we were pushing a new instance of the Dashboard view controller onto the stack.

I added an unwind segue to allow us to go from the CurrentTour view controller back to the Dashboard view controller properly.

NOTE: this pull request also contains some other changes, such as updating Pods (yeah, sorry).