CODEWITHSUNDEEP
android
med
med

Reputation: 1600

savedInstanceState is always null

This is my savedInstaceState code:

@Override
public void onSaveInstanceState(Bundle savedInstanceState) 
{
    savedInstanceState.putStringArrayList("todo_arraylist", Altodo);
    Log.v("bundle", "Saved");
    super.onSaveInstanceState(savedInstanceState);
}


public void onCreate(Bundle savedInstanceState) 
{
    super.onCreate(savedInstanceState);

    if (savedInstanceState != null) 
    {
        Altodo = savedInstanceState.getStringArrayList("todo_arraylist");
        Log.v("bundle", "Restored");
    }
    else
    {
        Log.v("bundle", "null");
    }

    setContentView(R.layout.main);
}

The logs always show the "bundle save" tag.

But in onCreate method, SavedInstanceState is always null.

Upvotes: 82

Views: 68461

Answers (13)

Chuck
Chuck

Reputation: 349

I was able to solve it with:

@Override public boolean onSupportNavigateUp()
{
    onBackPressed();
    return true;
}

still had parent set in the manifest. So when you press the up navigation button, now it acts like the back button.

Upvotes: 0

In New Oat
In New Oat

Reputation: 1

https://developer.android.com/guide/topics/manifest/activity-element#lmode

From this you can see 'Similarly, if you navigate up to an activity on the current stack, the behavior is determined by the parent activity's launch mode.' Maybe you are in the 'standard' mode.

Upvotes: 0

Horácio Comé
Horácio Comé

Reputation: 11

Ive managed same way arround. Instead of handling savedInstanceState Bundle on the onCreateView method, ive handled it on onCreate method and setting the passed value to a globar variable then acessing this variable on the onCreateView method. Hope it helps.

Upvotes: 0

Aron Lorincz
Aron Lorincz

Reputation: 1707

I found that when I override onSaveInstanceState() and actually save some data in the Bundle, instance state is restored. Otherwise it's not.

Upvotes: 0

AmirHossein Manian
AmirHossein Manian

Reputation: 617

Check your activity in AndroidManifest.xml and remove android:noHistory property if is true.

<activity
    // ....
    android:noHistory="false" />

Upvotes: 1

mibollma
mibollma

Reputation: 15108

How do you test it?

Imo the best way to test it is using the "Don't keep activities"-flag in Settings > Developer Options. If you don't have Developer Options in Settings, see Enabling On-device Developer Options.

  1. Open your activity
  2. Long-press home
  3. Go to another application
  4. Long-press home
  5. Go back to your application

Upvotes: 3

Jonathan Allard
Jonathan Allard

Reputation: 19249

Shouldn't super.onSaveInstanceState(savedInstanceState); be the first line in your override?

Edit: War_Hero points out in the comments that the documentation on that topic indicates that no, it shouldn't be the first line.

Upvotes: 2

Al Khorazmiy
Al Khorazmiy

Reputation: 106

in Manifest add this line for activities

android:launchMode="singleTop"

for example:

<activity
        android:name=".ActivityUniversity"
        android:label="@string/university"
        android:launchMode="singleTop"
        android:parentActivityName="com.alkhorazmiy.dtm.ActivityChart">
        <meta-data
            android:name="android.support.PARENT_ACTIVITY"
            android:value="com.alkhorazmiy.dtm.ActivityChart" />
    </activity>

Upvotes: 8

s.bandara
s.bandara

Reputation: 5664

I observed the exact same symptoms (reported as issue 133394) in a project with two Activities A and B that extend ActionBarActivity. Activity A is the main activity, and I always receive null for savedInstanceState in onCreate of its list fragment when returning from a detail view activity B. After many hours, this problem exposed itself to me as a navigation issue in disguise.

The following may be relevant to my setup and come from other answers on this page:

  • Given this answer, I made sure that fragment and activity each have unique IDs set.
  • There is no override of onSaveInstanceState without super call.
  • Activity A is specified as acitivy B's parent in AndroidManifest.xml, using both the android:parentActivityName attribute and the corresponding meta-data tag for earlier versions of Android (see "Providing Up Navigation").

Already without any corresponding creation code such as getActionBar() .setHomeButtonEnabled(true), activity B has a functioning back button (<) in its action bar. When this button is tapped, activity A reappears but with (a) all previous instance state lost, (b) onCreate always called, and (c) savedInstanceState always null.

Interestingly, when I tap the back button provided at the bottom edge of the emulator display (an open triangle that points to the left), activity A reappears just as it was left (i.e. its instance state fully retained) without invoking onCreate. So maybe something is wrong with navigation?

After more reading, I implemented my own navigation instructions to run in response to a tap on the back-button in activity B:

@Override
public boolean onOptionsItemSelected(MenuItem item) {
    if (item.getItemId() == android.R.id.home)
        NavUtils.navigateUpFromSameTask(this);
        return true;
    }
    return super.onOptionsItemSelected(item);
}

Nothing related to restoring instance state of activity A changed. NavUtils also provide a method getParentActivityIntent(Activity) and navigateUpTo(Activity, Intent) that allow us to modify the navigation intent to explicitly instruct that activity A is not started fresh (and thus without saved instance state provided) by setting the FLAG_ACTIVITY_CLEAR_TOP flag:

If set, and the activity being launched is already running in the current task, then instead of launching a new instance of that activity, all of the other activities on top of it will be closed and this Intent will be delivered to the (now on top) old activity as a new Intent.

In my hands, this solves problem of lost instance state and could look like:

public boolean onOptionsItemSelected(MenuItem item) {
    if (item.getItemId()== android.R.id.home) {
        Intent intent = NavUtils.getParentActivityIntent(this);
        intent.setFlags(Intent.FLAG_ACTIVITY_CLEAR_TOP);
        NavUtils.navigateUpTo(this, intent);
        return true;
    }
    return super.onOptionsItemSelected(item);
}

Note that this may not be the complete solution in other cases where a user can switch directly to activity B from within a different task (see here). Also, a possibly identical solution in behavior that does not make use of NavUtils is to simply call finish():

public boolean onOptionsItemSelected(MenuItem item) {
    if (item.getItemId()== android.R.id.home) {
        finish();
        return true;
    }
    return super.onOptionsItemSelected(item);
}

Both solutions work in my hands. I am only speculating that the original issue is a slightly incorrect default implementation of the back-button, and it may be related to that implementation invoking some kind of navigateUp that misses FLAG_ACTIVITY_CLEAR_TOP.

Upvotes: 57

mxcl
mxcl

Reputation: 26883

The state saved in this manner is not persisted. If the whole application is killed as you are doing during debugging, the bundle will always be null in onCreate.

This IMO is yet another example of awful Android documentation. It's also why most apps in the marketplace don't implement saving state properly (at all).

Upvotes: 15

PHF
PHF

Reputation: 1893

Did you check if you have an Id set for that view ( if a view it is/has...). onSaveInstanceState() is not called otherwise.

Check this link.

Upvotes: 14

Dharmendra
Dharmendra

Reputation: 33996

Implement a method of onRestoreInstanceState and put below code there

Altodo = savedInstanceState.getStringArrayList("todo_arraylist");

Upvotes: 0

JAL
JAL

Reputation: 3319

To debug, consider implementing onRestoreInstanceState and placing a call to Log.d in this method. Then, in the emulator, hit ctrl-F11 or whatever to rotate the phone. Your call to Log.d should be hit.

Upvotes: 0

Related Questions