没有查看发现ID时，与QUOT;不保留活动＆QUOT;已开启 [英] No View Found for ID when "Don't Keep Activities" Is Turned On

问题描述

我的应用程序被闲置的一些间歇之后崩溃。所以我想我没有正确存放东西。我打开不保留活动来解决，现在我的应用程序崩溃无处不在。

My app was crashing intermittently after some inactivity. So i figured I wasn't storing things correctly. I turned on "Don't Keep Activities" to troubleshoot and now my app is crashing everywhere.

堆栈跟踪： https://gist.github.com/hanleyhansen/6d41fee54b1e129b7922
这是去失踪的布局： https://gist.github.com/hanleyhansen/73ace0c99ae675023e0f

推荐答案

我觉得你正在经历的问题19917 。这个bug存在于3.2和更高版本和最近（4.2）只是固定的。同样的修复还没有到支持库的方式作出，但。

I think you are experiencing a likely symptom of Issue 19917. This bug exists in 3.2 and higher and was only fixed recently (4.2). This same fix hasn't made its way in to the support library, yet.

查看评论28 为一个真正的修复：你要编辑您的支持库，并重新编译。编辑V4 / JAVA /安卓/支持/ V4 /应用/ FragmentManager.java

Check out comment 28 for a real fix: you'll want to edit your support library and recompile. edit v4/java/android/support/v4/app/FragmentManager.java

Bundle saveFragmentBasicState(Fragment f) {
    Bundle result = null;

    if (mStateBundle == null) {
        mStateBundle = new Bundle();
    }
    f.onSaveInstanceState(mStateBundle);
    if (!mStateBundle.isEmpty()) {
        result = mStateBundle;
        mStateBundle = null;
    }

    if (f.mView != null) {
        saveFragmentViewState(f);
    }
    if (f.mSavedViewState != null) {
        if (result == null) {
            result = new Bundle();
        }
        result.putSparseParcelableArray(
                FragmentManagerImpl.VIEW_STATE_TAG, f.mSavedViewState);
    }
    if (!f.mUserVisibleHint) {
        // Only add this if it's not the default value
        // @@@ BUG, result may not have been created, can be null!
        if (result == null) {
            result = new Bundle();
        }
        result.putBoolean(FragmentManagerImpl.USER_VISIBLE_HINT_TAG, f.mUserVisibleHint);
    }

    return result;
}

如果您不觉得能够胜任工作，并希望等待谷歌修复支持库
这里是另一个解决办法
评论8 以修复您可以应用到所有的片段

If you dont feel up to the task and want to wait for Google to fix the support library here is another workaround Comment 8 for fix you can apply to all your fragments

    @Override
    public void onSaveInstanceState(Bundle outState) {
        //first saving my state, so the bundle wont be empty.
        //http://code.google.com/p/android/issues/detail?id=19917
        outState.putString("WORKAROUND_FOR_BUG_19917_KEY", "WORKAROUND_FOR_BUG_19917_VALUE");
        super.onSaveInstanceState(outState);
    }

我也遇到 transaction.commitAllowingStateLoss（）; 作为修复这不是器transaction.commit（）;

其他的一些背景信息和解决方法我发现是相关的，与片段的问题（特别是其中嵌套时）

Some other background info and workaround I've found that are related that helped me with fragment issues (esp. when nesting them)

• TNR的回答 java.lang.IllegalStateException：无法执行后的onSaveInstanceState这个行动DialogFragment （体面的解决方法）


• 如何解决无法执行后的onSaveInstanceState此操作在Android片段] 4 （非常丰富）


• 克里斯·詹金斯回答做片段真的需要一个空的构造？

• TNR's answer to java.lang.IllegalStateException: Can not perform this action after onSaveInstanceState with DialogFragment (decent workaround)
• How to fix "Can not perform this action after onSaveInstanceState" on Android Fragments ]4 (very informative)
• Chris Jenkins answer to Do fragments really need an empty constructor?

这篇关于没有查看发现ID时，与QUOT;不保留活动＆QUOT;已开启的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！