你可能会调用fragmentManager.popBackStackImmediate();当活动暂停时。活动未完成，但处于暂停状态，且不在前台。你需要在popBackStackImmediate()之前检查activity是否被暂停。

在屏幕被锁定\blank并且Activity +对话框的实例状态被保存之后，在对话框片段上调用dismiss()也会发生这种情况。要绕过这个调用:

dismissAllowingStateLoss()

实际上，每次我解散一个对话框时，我都不再关心它的状态了，所以这样做是可以的——实际上你并没有失去任何状态。

I noticed something very interesting. I have in my app the option to open the phone's gallery and the device asks what app to use, there I click on the gray area away from the dialog and saw this issue. I noticed how my activity goes from onPause, onSaveInstanceState back to onResume, it doesn't happen to visit onCreateView. I am doing transactions at onResume. So what I ended up doing is setting a flag being negated onPause, but being true onCreateView. if the flag is true onResume then do onCommit, otherwise commitAllowingStateLoss. I could go on and waste so much time but I wanted to check the lifecycle. I have a device which is sdkversion 23, and I don't get this issue, but I have another one which is 21, and there I see it.

我认为生命周期状态可以帮助防止这种崩溃从Android支持库v26.1.0开始，你可以有以下检查:

if (getLifecycle().getCurrentState().isAtLeast(Lifecycle.State.STARTED)){
  // Do fragment's transaction commit
}

或者你可以试试:

Fragment.isStateSaved()

更多信息请点击这里 https://developer.android.com/reference/android/support/v4/app/Fragment.html isStateSaved ()

我对这个问题的解决方案是

在片段中添加方法:

@Override
public View onCreateView(LayoutInflater inflater, ViewGroup container, Bundle savedInstanceState) {
    ...
    guideMapFragment = (SupportMapFragment)a.getSupportFragmentManager().findFragmentById(R.id.guideMap);
    guideMap = guideMapFragment.getMap();
    ...
}

@Override
public void onDestroyView() {
    SherlockFragmentActivity a = getSherlockActivity();
    if (a != null && guideMapFragment != null) {
        try {
            Log.i(LOGTAG, "Removing map fragment");
            a.getSupportFragmentManager().beginTransaction().remove(guideMapFragment).commit();
            guideMapFragment = null;
        } catch(IllegalStateException e) {
            Log.i(LOGTAG, "IllegalStateException on exit");
        }
    }
    super.onDestroyView();
}

可能很糟糕，但找不到更好的了。

好吧，在尝试了以上所有的解决方案都没有成功(因为基本上我没有事务)。

在我的情况下，我使用alertdialog和ProgressDialog作为片段，有时，在旋转时，当请求FragmentManager时，错误会上升。

我找到了一个混合了许多类似帖子的变通方法:

这是一个3步解决方案，所有在你的FragmentActivity(在这种情况下，它被称为GenericActivity):

private static WeakReference<GenericActivity> activity = null; //To avoid bug for fragments: Step 1 of 3

@Override
protected void onCreate(Bundle savedInstanceState){
    super.onCreate(savedInstanceState);
    //To avoid bug for fragments: Step 2 of 3
    activity = new WeakReference<GenericActivity>(this);
}

@Override
public FragmentManager getSupportFragmentManager(){
    //To avoid bug for fragments: Step 3 of 3
    if (this == activity.get()) {
        return super.getSupportFragmentManager();
    }
    return activity.get().getSupportFragmentManager();
}