Android的ShowDialog的：IllegalStateException异常：不能的onSaveInstanceState后执行此操作 [英] Android ShowDialog : IllegalStateException: Can not perform this action after onSaveInstanceState

问题描述

在 runOnUiThread（）的活动，我想表现出ProgressDialog。

  FragmentTransaction fragmentTransaction = getSupportFragmentManager（）调用BeginTransaction（）;
 ProgressDialogFragment mProgressDialogFragment =新ProgressDialogFragment（）;
 mProgressDialogFragment.show（fragmentTransaction，TAG）;
 

下面 ProgressDialogFragment 扩展 DialogFragment 。我曾经在很多设备测试这一点，并没有得到任何崩溃。但是，而在华硕的，我经常收到下面的崩溃每当我显示对话框。华硕OS版本是4.4.2。

  java.lang.IllegalStateException：的onSaveInstanceState后无法执行此操作
       在android.support.v4.app.FragmentManagerImpl.checkStateLoss（FragmentManager.java:1360）
       在android.support.v4.app.FragmentManagerImpl.enqueueAction（FragmentManager.java:1378）
       在android.support.v4.app.BackStackRecord.commitInternal（BackStackRecord.java:595）
       在android.support.v4.app.BackStackRecord.commit（BackStackRecord.java:574）
       在android.support.v4.app.DialogFragment.show（DialogFragment.java:155）
       在com.trimble.android.trimbleone.activity.ProgressDialogHandlerActivity.showProgressDialog(ProgressDialogHandlerActivity.java:72)
       在com.trimble.android.trimbleone.activity.UICallbackHandlerActivity$processThread$7.run(UICallbackHandlerActivity.java:222)
       在android.os.Handler.handleCallback（Handler.java:733）
       在android.os.Handler.dispatchMessage（Handler.java:95）
       在android.os.Looper.loop（Looper.java:149）
       在android.app.ActivityThread.main（ActivityThread.java:5061）
       在java.lang.reflect.Method.invokeNative（Method.java）
       在java.lang.reflect.Method.invoke（Method.java:515）
       在com.android.internal.os.ZygoteInit $ MethodAndArgsCaller.run（ZygoteInit.java:788）
       在com.android.internal.os.ZygoteInit.main（ZygoteInit.java:604）
       在dalvik.system.NativeStart.main（NativeStart.java）
 

解决方案

  @覆盖
保护无效的onSaveInstanceState（捆绑outState）{
    //没有要求超（）。臭虫在API级别＆GT; 11。
}
 

不要使调用超（）在 saveInstanceState 方法。这是搞乱事情了...

一些调查研究后，这是在支持包一个知道是不是BUG。

如果您需要保存的实例，并添加了一些你的 outState 捆绑您可以使用以下命令：

  @覆盖
保护无效的onSaveInstanceState（捆绑outState）{
    outState.putString（WORKAROUND_FOR_BUG_19917_KEY，WORKAROUND_FOR_BUG_19917_VALUE）;
    super.onSaveInstanceState（outState）;
}
 

在结束时的适当的溶液（如在注释所示）使用

  transaction.commitAllowingStateLoss（）;
 

添加或执行时， FragmentTransaction 这是造成了例外。

将上述溶液从我记得固定在早期support.v4库的问题。但是，如果你仍然有这个问题，你也必须阅读 @AlexLockwood 的博客：的片段交易和放大器;活动状态损耗

从博客文章摘要（但我强烈建议你读它）：

绝不会提交（）在的onPause交易（）上pre-蜂窝和的onStop（）上后蜂窝
承诺活动生命周期方法内交易时要小心。使用的onCreate（）， onResumeFragments（）和 onPostResume（）
避免内部异步回调方法执行交易
使用 commitAllowingStateLoss（）只能作为最后的手段结果
更新：用于显示 DialogFragment 使用stateLoss使用以下行

  DialogFragment loadingDialog = createDialog（）;
FragmentTransaction交易= getSupportFragmentManager（）调用BeginTransaction（）。
                    transaction.add（loadingDialog，装）;
                    transaction.commitAllowingStateLoss（）;
 

In runOnUiThread() of an Activity, I'm trying to show a ProgressDialog.

 FragmentTransaction fragmentTransaction = getSupportFragmentManager().beginTransaction();
 ProgressDialogFragment mProgressDialogFragment = new ProgressDialogFragment();
 mProgressDialogFragment.show(fragmentTransaction, TAG);

Here ProgressDialogFragment extends DialogFragment. I have tested this in many devices and didn't get any crash. But whereas in Asus, I'm constantly getting the below crash whenever I show the dialog. OS version on Asus is 4.4.2 .

java.lang.IllegalStateException: Can not perform this action after onSaveInstanceState
       at android.support.v4.app.FragmentManagerImpl.checkStateLoss(FragmentManager.java:1360)
       at android.support.v4.app.FragmentManagerImpl.enqueueAction(FragmentManager.java:1378)
       at android.support.v4.app.BackStackRecord.commitInternal(BackStackRecord.java:595)
       at android.support.v4.app.BackStackRecord.commit(BackStackRecord.java:574)
       at android.support.v4.app.DialogFragment.show(DialogFragment.java:155)
       at com.trimble.android.trimbleone.activity.ProgressDialogHandlerActivity.showProgressDialog(ProgressDialogHandlerActivity.java:72)
       at com.trimble.android.trimbleone.activity.UICallbackHandlerActivity$processThread$7.run(UICallbackHandlerActivity.java:222)
       at android.os.Handler.handleCallback(Handler.java:733)
       at android.os.Handler.dispatchMessage(Handler.java:95)
       at android.os.Looper.loop(Looper.java:149)
       at android.app.ActivityThread.main(ActivityThread.java:5061)
       at java.lang.reflect.Method.invokeNative(Method.java)
       at java.lang.reflect.Method.invoke(Method.java:515)
       at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:788)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:604)
       at dalvik.system.NativeStart.main(NativeStart.java)

解决方案

@Override
protected void onSaveInstanceState(Bundle outState) {
    //No call for super(). Bug on API Level > 11.
}

don't make the call to super() on the saveInstanceState method. This was messing things up...

After some more research, this is a know bug in the support package.

If you need to save the instance, and add something to your outState Bundle you can use the following :

@Override
protected void onSaveInstanceState(Bundle outState) {
    outState.putString("WORKAROUND_FOR_BUG_19917_KEY", "WORKAROUND_FOR_BUG_19917_VALUE");
    super.onSaveInstanceState(outState);
}

In the end the proper solution was (as seen in the comments) to use :

transaction.commitAllowingStateLoss();

when adding or performing the FragmentTransaction that was causing the Exception.

The above solutions were fixing issues in the early support.v4 libraries from what I can remember. But if you still have issues with this you MUST also read @AlexLockwood 's blog : Fragment Transactions & Activity State Loss

Summary from the blog post (but I strongly recommend you to read it) :

NEVER commit() transactions after onPause() on pre-Honeycomb, and onStop() on post-Honeycomb Be careful when committing transactions inside Activity lifecycle methods. Use onCreate(), onResumeFragments() and onPostResume() Avoid performing transactions inside asynchronous callback methods Use commitAllowingStateLoss() only as a last resort
Updated : For showing the DialogFragment using stateLoss use the following lines.

DialogFragment loadingDialog = createDialog();
FragmentTransaction transaction = getSupportFragmentManager().beginTransaction();
                    transaction.add(loadingDialog, "loading");
                    transaction.commitAllowingStateLoss();

这篇关于Android的ShowDialog的：IllegalStateException异常：不能的onSaveInstanceState后执行此操作的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！