[Solved] “Can not perform this action after onSaveInstanceState” – why am I getting this exception from my activity’s onResume method?

My activity invokes the camera with the ACTION_IMAGE_CAPTURE intent. If the camera activity returns succesfully, I set a flag in the onActivityResult callback, and based on the value of the flag I start a fragment in my onResume to add a caption to the image that was captured. This seems to work ok.

I just got a stack trace from the “wild” complaining that I was trying to commit a fragment transaction after onSaveInstanceState has been called. But I’m doing the commit in my onResume method! Why would android complain about this? I do have android:configChanges=”orientation|keyboardHidden|keyboard|screenSize” set in my AndroidManifest.xml, so an orientation change should not trigger this….

This occurred on a Samsung Galaxy S3 (SGH-i747) running 4.0.4

Here is the stack:

java.lang.IllegalStateException: Can not perform this action after onSaveInstanceState
    at com.Familiar.Android.FamiliarAppV1.AddPhotosActivity2.performFragmentTransition(
    at com.Familiar.Android.FamiliarAppV1.AddPhotosActivity2.switchToCaptionsFragment(
    at com.Familiar.Android.FamiliarAppV1.AddPhotosActivity2.onResume(
    at android.os.Handler.dispatchMessage(
    at android.os.Looper.loop(
    at java.lang.reflect.Method.invokeNative(Native Method)
    at java.lang.reflect.Method.invoke(
    at dalvik.system.NativeStart.main(Native Method)

Any help or wisdom is appreciated.

Solution #1:

I think I know the answer – I’m using the FragmentActivity from v4 compatibility library, and so I need to perform my fragment transactions in onResumeFragments instead of in onResume. Can someone confirm?

Respondent: PacificSky

Solution #2:

you can use the method commitAllowingStateLoss()

but be aware you can lose the state of your activity
as you can see in google’s android reference
which explain the different between the two in the following way

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.

from my experience it may cause the addToBackStack method not to work sometimes so you will need to add it manually on the fragment
and of course the state won’t be saved (textbox text ext.)

Respondent: Asaf Manassen

Solution #3:

this worked for me… found this out on my own… hope it helps you!

1) do NOT have a global “static” FragmentManager / FragmentTransaction.

2) onCreate, ALWAYS initialize the FragmentManager again!

sample below :-

public abstract class FragmentController extends AnotherActivity{
protected FragmentManager fragmentManager;
protected FragmentTransaction fragmentTransaction;
protected Bundle mSavedInstanceState;

protected void onCreate(Bundle savedInstanceState) {
    mSavedInstanceState = savedInstanceState;

protected void setDefaultFragments() {
    fragmentManager = getSupportFragmentManager();
    //check if on orientation change.. do not re-add fragments!
    if(mSavedInstanceState == null) {
        //instantiate the fragment manager

        fragmentTransaction = fragmentManager.beginTransaction();

        //the navigation fragments
        NavigationFragment navFrag = new NavigationFragment();
        ToolbarFragment toolFrag = new ToolbarFragment();

        fragmentTransaction.add(, navFrag, "NavFrag");
        fragmentTransaction.add(, toolFrag, "ToolFrag");

        //add own fragment to the nav (abstract method)
Respondent: kurayami88

Solution #4:

Update I think I have found an explanation and a solution here:
I implemented the Empty Fragment Workaround posted there and got no more IllegalStateException so far.

I add the invisible state fragment in my activity like this;

protected void onCreate(final Bundle args) {
    if (args == null) {
        final FragmentManager fm = this.getSupportFragmentManager();
        final FragmentTransaction ft = fm.beginTransaction();
        final Fragment emptyFragmentWithCallback = new EmptyFragmentWithCallbackOnResume();
        ft.add(emptyFragmentWithCallback, EmptyFragmentWithCallbackOnResume.TAG);

The following code is taken from above link:

public class EmptyFragmentWithCallbackOnResume extends Fragment {
OnFragmentAttachedListener mListener = null;

public void onAttach(SupportActivity activity) {
    try {
        mListener = (OnFragmentAttachedListener) activity;
    } catch (ClassCastException e) {
        throw new ClassCastException(activity.toString() + " must implement OnFragmentAttachedListener");

public void onResume() {
    if (mListener != null) {

public interface OnFragmentAttachedListener {
    public void OnFragmentAttached();

and invoke fragment transactions that would intuitively go into onResume or onResumeFragments into my custom onFragmentAttached method that is invoked by the invisible state fragment. I do not use onResumeFragments at all and do not issue any fragment transactions in onResume.

So, to sum it up. If you are using the support lib and fragments, pretty much forget about onResume, forget about onResumeFragments and implement your own “onResume” based on the above workaround.
This is somewhat ridiculous.

I cannot confirm. I have the exact same problem. even though I am issuing fragment transaction in onResumeFragments.
This used to work as I posted here: IllegalStateException – Fragment support library .

It seems the error only occurs on 4.0.3 and 4.0.4. However it does neither occur always nor in my Emulator.

I am using support lib rev. 10 and API 16.
I call in onResumeFragments and continously get this ridiculous exception from some random users. I cannot reproduce it locally.

Respondent: phlebas

Solution #5:

I was always getting this when I tried to show fragment in onActivityForResult() method, so the problem was next:

  1. My Activity is paused and stopped, which means, that onSaveInstanceState() was called already (for both pre-Honeycomb and post-Honeycomb devices).
  2. In case of any result I made transaction to show/hide fragment, which causes this IllegalStateException.

What I made is next:

  1. Added value for determining if action I want was done (e.g. taking photo from camere – isPhotoTaken) – it can be boolean or integer value depending how much different transactions you need.
  2. In overriden onResumeFragments() method I checked for my value and after made fragment transactions I needed. In this case commit() was not done after onSaveInstanceState, as state was returned in onResumeFragments() method.
Respondent: Array

Solution #6:

I first develop my app targeting android 2.2 (SDK 8), using the support v4 library, and when I start using it with 4.2 (SDK 17), I had the same troubles with my fragments. But changing my Manifest to android:minSdkVersion=”8″ android:targetSdkVersion=”17″, solved my problems. Maybe this hepls you too.

Respondent: Andre Rocha

Solution #7:

Add this to your Activity:

    protected void onSaveInstanceState(Bundle outState) {
        //No call for super(). Bug on API Level > 11.
Respondent: Alok Singh

The answers/resolutions are collected from stackoverflow, are licensed under cc by-sa 2.5 , cc by-sa 3.0 and cc by-sa 4.0 .

Most Popular

To Top
India and Pakistan’s steroid-soaked rhetoric over Kashmir will come back to haunt them both clenbuterol australia bossier man pleads guilty for leadership role in anabolic steriod distribution conspiracy