当我试图在onActivityForResult()方法中显示片段时，我总是得到这个，所以接下来的问题是:

我的活动暂停和停止，这意味着，onSaveInstanceState()已经被调用(对于pre-Honeycomb和post-Honeycomb设备)。 在任何结果的情况下，我使事务显示/隐藏片段，这导致这个IllegalStateException。

接下来我做的是:

增加了确定我想要的动作是否完成的值(例如，从camere - isPhotoTaken中拍摄照片)-它可以是布尔值或整数值，这取决于你需要多少不同的事务。 在重写onResumeFragments()方法中，我检查了我的值，并在我需要的片段事务之后。在这种情况下，commit()没有在onSaveInstanceState之后执行，因为状态是在onResumeFragments()方法中返回的。

谢谢@gunar，但我认为有更好的方法。

医生说:

*如果您提交的单个事务没有修改 *碎片回栈，强烈考虑使用 * {@link FragmentTransaction#commitNow()}代替。这有助于避免 *当应用程序中的其他代码未提交时，会产生不必要的副作用 *需要不同时间的事务。 ＊ * @return如果有任何待处理事务则返回true *执行。 * / executePendingTransactions();

所以使用commitNow替换:

fragmentTransaction.commit();
FragmentManager.executePendingTransactions()

I solved the issue with onconfigurationchanged. The trick is that according to android activity life cycle, when you explicitly called an intent(camera intent, or any other one); the activity is paused and onsavedInstance is called in that case. When rotating the device to a different position other than the one during which the activity was active; doing fragment operations such as fragment commit causes Illegal state exception. There are lots of complains about it. It's something about android activity lifecycle management and proper method calls. To solve it I did this: 1-Override the onsavedInstance method of your activity, and determine the current screen orientation(portrait or landscape) then set your screen orientation to it before your activity is paused. that way the activity you lock the screen rotation for your activity in case it has been rotated by another one. 2-then , override onresume method of activity, and set your orientation mode now to sensor so that after onsaved method is called it will call one more time onconfiguration to deal with the rotation properly.

你可以复制/粘贴这段代码到你的活动来处理它:

@Override
protected void onSaveInstanceState(Bundle outState) {       
    super.onSaveInstanceState(outState);

    Toast.makeText(this, "Activity OnResume(): Lock Screen Orientation ", Toast.LENGTH_LONG).show();
    int orientation =this.getDisplayOrientation();
    //Lock the screen orientation to the current display orientation : Landscape or Potrait
    this.setRequestedOrientation(orientation);
}

//A method found in stackOverflow, don't remember the author, to determine the right screen orientation independently of the phone or tablet device 
public int getDisplayOrientation() {
    Display getOrient = getWindowManager().getDefaultDisplay();

    int orientation = getOrient.getOrientation();

    // Sometimes you may get undefined orientation Value is 0
    // simple logic solves the problem compare the screen
    // X,Y Co-ordinates and determine the Orientation in such cases
    if (orientation == Configuration.ORIENTATION_UNDEFINED) {
        Configuration config = getResources().getConfiguration();
        orientation = config.orientation;

        if (orientation == Configuration.ORIENTATION_UNDEFINED) {
        // if height and widht of screen are equal then
        // it is square orientation
            if (getOrient.getWidth() == getOrient.getHeight()) {
                orientation = Configuration.ORIENTATION_SQUARE;
            } else { //if widht is less than height than it is portrait
                if (getOrient.getWidth() < getOrient.getHeight()) {
                    orientation = Configuration.ORIENTATION_PORTRAIT;
                } else { // if it is not any of the above it will defineitly be landscape
                    orientation = Configuration.ORIENTATION_LANDSCAPE;
                }
            }
        }
    }
    return orientation; // return value 1 is portrait and 2 is Landscape Mode
}

@Override
public void onResume() {
    super.onResume();
    Toast.makeText(this, "Activity OnResume(): Unlock Screen Orientation ", Toast.LENGTH_LONG).show();
    setRequestedOrientation(ActivityInfo.SCREEN_ORIENTATION_SENSOR);
} 

如果你试图在你的片段活动的onSaveInstanceState()被调用后执行片段转换，就会发生这样的异常。

发生这种情况的一个原因是，当一个活动停止时，如果你让一个AsyncTask(或线程)运行。

调用onSaveInstanceState()后的任何转换都可能丢失，如果系统回收活动的资源并稍后重新创建它。

Android 4.2和支持库的源代码中修正了这个问题。[*]

有关原因(和解决方案)的详细信息，请参阅谷歌错误报告: http://code.google.com/p/android/issues/detail?id=19917

如果你正在使用支持库，那么你不应该担心这个错误(很长时间)[*]。然而，如果你直接使用API(即不使用支持库的FragmentManager)，并针对Android 4.2以下的API，那么你将需要尝试一种变通方法。

[*]在撰写本文时，Android SDK管理器仍在分发显示此错误的旧版本。

编辑，我要在这里补充一些澄清，因为我显然把投票反对这个答案的人弄糊涂了。

There are several different (but related) circumstances that can cause this exception to be thrown. My answer above is referring to the specific instance discussed in the question i.e. a bug in Android which has subsequently been fixed. If you're getting this exception for another reason it's because you're adding/removing fragments when you shouldn't be (after fragment states have been saved). If you're in such a situation then perhaps "Nested Fragments - IllegalStateException “Can not perform this action after onSaveInstanceState”" can be of use to you.

读 http://chris-alexander.co.uk/on-engineering/dev/android-fragments-within-fragments/

篇文章。 fragment. isresume()检查帮助我在onDestroyView w/o使用onSaveInstanceState方法。