Skip to main content

onSaveInstanceState() not called: why?


Problem:



I add a fragment to a LinearLayout, programmatically. It shows up in my activity, great. I turn the device —> configuration changes: everything is destroyed to be recreated. But, before onDestroy() is called, onSaveInstanceState() should be called. It is the case for the parent activity, but not for the fragment I've added. Why ?



Code:



The XML:




<?xml version="1.0" encoding="utf-8"?>
<LinearLayout
xmlns:android="http://schemas.android.com/apk/res/android"
android:id="@id/parent_LL"
android:stuff="myStuff"
>

<LinearLayout
android:id="@id/categories_activity_LL1"
android:stuff="myStuff" />

<LinearLayout
android:id="@id/categories_activity_LL2"
android:stuff="myStuff" />
</LinearLayout>



I add the fragment to the UI in the parent activity:




ft.add(container1, categories, CatFragIds.CATEGORIES.toString()).commit();



I override the onSaveInstanceState() of my fragment:




@Override
public void onSaveInstanceState(Bundle outState) {

// Récupère extensible
boolean extensible = ((CategoryAppsListView) this.getListView())
.isExtensible();

mState.setExtensible(extensible);

// Transmet l'état de CategoriesListElems
FragmentManager fm = getFragmentManager();

@SuppressWarnings("unchecked")
FragRetainObject<CategoriesListElemsState> retainedState =
(FragRetainObject<CategoriesListElemsState>)
fm.findFragmentByTag(CATEGORIESLISTELEMS_STATE+"_"+this.getTag());

if( retainedState == null) {
retainedState =
FragRetainObject.<CategoriesListElemsState>newInstance(mState);

fm.beginTransaction()
.add(retainedState, CATEGORIESLISTELEMS_STATE+"_"+this.getTag()).commit();
}
else retainedState.setRetainObj(mState);

super.onSaveInstanceState(outState);
}



Thank you for your time!! :-)


Source: Tips4allCCNA FINAL EXAM

Comments

  1. I had the same problem. There are two answers:


    Add fragment in xml file, like "fragment android:name="faragmentClass" etc."
    Call onSaveInstanceState method of fragment manualy. And in onCreate method restore fragment's state manualy, when you add it.

    ReplyDelete
  2. You need to put the config change as orientation and keyboard in the AndroidManifest.xml

    ReplyDelete

Post a Comment

Popular posts from this blog

Slow Android emulator

I have a 2.67 GHz Celeron processor, 1.21 GB of RAM on a x86 Windows XP Professional machine. My understanding is that the Android emulator should start fairly quickly on such a machine, but for me it does not. I have followed all instructions in setting up the IDE, SDKs, JDKs and such and have had some success in staring the emulator quickly but is very particulary. How can I, if possible, fix this problem?