iFixit / iFixitAndroid

Official iFixit Android App
https://play.google.com/store/apps/details?id=com.dozuki.ifixit
GNU General Public License v3.0
162 stars 88 forks source link

Guide intro edit resuming crashes #77

Closed marczych closed 11 years ago

marczych commented 11 years ago

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:

07-06 00:32:40.463    3916-3916/com.dozuki.ifixit              E/AndroidRuntime: FATAL EXCEPTION: main
        java.lang.RuntimeException: Unable to start activity ComponentInfo{com.dozuki.ifixit/com.dozuki.ifixit.ui.guide.create.GuideIntroActivity}: java.lang.NullPointerException
        at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2180)
        at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2230)
        at android.app.ActivityThread.access$600(ActivityThread.java:141)
        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1234)
        at android.os.Handler.dispatchMessage(Handler.java:99)
        at android.os.Looper.loop(Looper.java:137)
        at android.app.ActivityThread.main(ActivityThread.java:5041)
        at java.lang.reflect.Method.invokeNative(Native Method)
        at java.lang.reflect.Method.invoke(Method.java:511)
        at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:793)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:560)
        at dalvik.system.NativeStart.main(Native Method)
        Caused by: java.lang.NullPointerException
        at com.dozuki.ifixit.ui.guide.create.GuideIntroActivity.onGetPage(GuideIntroActivity.java:249)
        at com.dozuki.ifixit.ui.guide.create.wizard.TopicNameFragment.onCreate(TopicNameFragment.java:73)
        at android.support.v4.app.Fragment.performCreate(Fragment.java:1437)
        at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:877)
        at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1088)
        at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1070)
        at android.support.v4.app.FragmentManagerImpl.dispatchCreate(FragmentManager.java:1856)
        at android.support.v4.app.FragmentActivity.onCreate(FragmentActivity.java:210)
        at com.dozuki.ifixit.ui.BaseActivity.onCreate(BaseActivity.java:216)
        at com.dozuki.ifixit.ui.guide.create.GuideIntroActivity.onCreate(GuideIntroActivity.java:123)
        at android.app.Activity.performCreate(Activity.java:5104)
        at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1080)
        at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2144)
        ... 11 more
timothyasp commented 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?

timothyasp commented 11 years ago

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

timothyasp commented 11 years ago

Fixed with ac35192