Closed marczych closed 11 years ago
Good catch, but I haven't been able to reproduce this. I'll start the app up, start a new guide, tap the home button or open up a couple new apps, then navigate back to the app, and it's fine. Is there another guaranteed way to get the app out of memory?
Never mind - setting "Immediatly destroy activies" setting in Dev settings causes activities to be immediatly be destroyed, and thus causes the crash. http://developer.android.com/tools/debugging/debugging-devtools.html
Fixed with ac35192
1) Open up guide intro edit 2) Open another app or two to push the iFixit app out of memory. 3) Resuming the app results in a crash and a nasty stack trace: