Menu
I am trying Android N multi window feature and I have found myself confused when starting a new activity. The problem is that when I start a new Activity, the onStop() callback is not being fired and when I press the back button from this new activity to return to the previous one, the previous one's onStart() callback is not being fired either.
Does anyone know what is happening?
--- Edited
It seems like that ActivityOptionsCompat.makeSceneTransitionAnimation has something to do with it.
282
The onStop() method is used to save application data. These methods are guaranteed to be called before the activity is terminated. If the user switches back to application which has been terminated by the system, it is restarted.
onStop() Called when the activity is no longer visible to the user. Either because another Activity has resumed, and is covering this one, an existing activity is coming to the foreground, or the activity is about to be destroyed.
Once your activity is stopped, the system might destroy the instance if it needs to recover system memory. In extreme cases, the system might simply kill your app process without calling the activity's final onDestroy() callback, so it's important you use onStop() to release resources that might leak memory.
onPause() and onStop() will not be invoked if finish() is called from within the onCreate() method. This might occur, for example, if you detect an error during onCreate() and call finish() as a result. In such a case, though, any cleanup you expected to be done in onPause() and onStop() will not be executed.
Here is the android-lifecycle:
If you call another app in multi window mode, your application is still "partially visible", so onPause() is being called, but onStop() not.
At restart it's the same: onResume() is being called, but onStart() isn't.
50
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
