The following figure (from the official doc) describes the well-known lifecycle of an Android activity:
On the other hand, when the activity is destroyed by the system (for example because memory needs to be reclaimed), the state of the activity is sometimes automatically saved and restored by means of the methods onSaveInstanceState()
and onRestoreInstanceState()
, as illustrated by the following figure (also from the official doc):
I'm aware that onSaveInstanceState()
is not always called when an activity is about to be destroyed. For example, if it is destroyed because the user has pressed the "back" button, the activity state is not preserved. But in the cases when the state is saved and restored, and onSaveInstanceState()
/ onRestoreInstanceState()
get called, when exactly are they called?
For example, according to the above figures, onRestoreInstanceState()
might be called before onStart()
, or after onStart()
but before onResume()
, or after onResume()
. Similarly, several possibilities exist for onSaveInstanceState()
. So when are they called exactly?
Ideally, what I would like is to see a combined diagram showing the activity lifecycle states and the save/restore methods, if that exists.
Note that onSaveInstanceState() is called when your activity goes into the background and NOT when the app process is about to be killed.
Choose one: onSaveInstanceState() is called before the onStop() method. onSaveInstanceState() is called before the onResume() method.
From the documentation I understand that onSaveInstanceState() should be called to store only temporary information, and onPause() should be used to store any persistent data.
The onSaveInstanceState() method allows you to add key/value pairs to the outState of the app. Then the onRestoreInstanceState() method will allow you to retrieve the value and set it back to the variable from which it was originally collected.
Per the documentation:
void onRestoreInstanceState (Bundle savedInstanceState)
This method is called between
onStart()
andonPostCreate(Bundle)
.void onSaveInstanceState (Bundle outState)
If called, this method will occur after onStop() for applications targeting platforms starting with Build.VERSION_CODES.P. For applications targeting earlier platform versions this method will occur before onStop() and there are no guarantees about whether it will occur before or after onPause().
As per doc1 and doc2
onSaveInstanceState
Prior to Honeycomb, activities were not considered killable until after they had been paused, meaning that onSaveInstanceState() was called immediately before onPause(). Beginning with Honeycomb, however, Activities are considered to be killable only after they have been stopped, meaning that onSaveInstanceState() will now be called before onStop() instead of immediately before onPause().
onRestoreInstanceState
This method is called between onStart() and onPostCreate(Bundle) when the activity is being re-initialized from a previously saved state
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With