zoukankan      html  css  js  c++  java
  • 解决IllegalStateException: Can not perform this action after onSaveInstanceState

    extends:http://blog.csdn.net/ranxiedao/article/details/8214936 , http://blog.csdn.net/top_code/article/details/12614571

    今天使用Fragment的时候,出现了这个错误 IllegalStateException: Can not perform this action after onSaveInstanceState:

     
    
    E/AndroidRuntime(12747): Caused by: java.lang.IllegalStateException: Can not perform this action after onSaveInstanceState  
        at android.support.v4.app.FragmentManagerImpl.checkStateLoss(FragmentManager.java:1314)  
        at android.support.v4.app.FragmentManagerImpl.enqueueAction(FragmentManager.java:1325)  

    java.lang.IllegalStateException: Can not perform this action after onSaveInstanceState
    at android.support.v4.app.FragmentManagerImpl.checkStateLoss(Unknown Source)
    at android.support.v4.app.FragmentManagerImpl.enqueueAction(Unknown Source)
    at android.support.v4.app.BackStackRecord.commitInternal(Unknown Source)
    at android.support.v4.app.BackStackRecord.commit(Unknown Source)
    at com.yulore.yellowpage.DialLogActivity.a(Unknown Source)
    at com.yulore.yellowpage.fragment.x.handleMessage(Unknown Source)
    at android.os.Handler.dispatchMessage(Handler.java:99)
    at android.os.Looper.loop(Looper.java:137)
    at android.app.ActivityThread.main(ActivityThread.java:4797)
    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:789)
    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:556)
    at dalvik.system.NativeStart.main(Native Method)

    是在使用FragmentTransition的 commit方法添加一个Fragment的时候出现的,后来在官网找到了相关的

    说明:http://developer.android.com/reference/android/app/FragmentTransaction.html#commitAllowingStateLoss()

    public abstract int commitAllowingStateLoss ()                                    Added in API level 11

    Like commit() but allows the commit to be executed after an activity's state is saved. This is dangerous 

    because the commit can be lost if the activity needs to later be restored from its state, so this should 

    only be used for cases where it is okay for the UI state to change unexpectedly on the user.

    大致意思是说我使用的 commit方法是在Activity的onSaveInstanceState()之后调用的,这样会出错,因为onSaveInstanceState

    方法是在该Activity即将被销毁前调用,来保存Activity数据的,如果在保存玩状态后再给它添加Fragment就会出错。解决办法就

    是把commit()方法替换成 commitAllowingStateLoss()就行了,其效果是一样的。

    解决办法

    把commit()方法替换成 commitAllowingStateLoss() 

     
    ft.setTransition(FragmentTransaction.TRANSIT_FRAGMENT_FADE);  
            if (this.isFinishing()) {   //判断Activity是否还存在  
                return;  
            }  
            ft.commitAllowingStateLoss();  
    //      ft.commit();  
     
  • 相关阅读:
    [转]VS2010几款超赞的扩展辅助工具总结
    从客户端中检测到有潜在危险的Request.Form 值
    面试系列28 分布式服务接口的幂等性如何设计
    面试系列26 如何基于dubbo进行服务治理、服务降级、失败重试以及超时重试
    面试系列25 dubbo的spi思想是什么
    面试系列24 dubbo负载均衡策略和集群容错策略
    面试系列23
    面试系列22 dubbo的工作原理
    面试系列21 为什么要进行系统拆分
    面试系列20 生产环境中的redis是怎么部署的
  • 原文地址:https://www.cnblogs.com/niray/p/4282236.html
Copyright © 2011-2022 走看看