xxv / android-lifecycle Goto Github PK

I'd swap Activity and Fragment, as the Activity runs first.

(Reported by Kurt Huwig via personal email)

Are you planning to add methods such as onCreateDialog which are specific to the DialogFragment class?

是我代码的问题还是？

Lifecycle documentation lacks this. I'm not sure if fits the "lifecycle" but this method is somehow related to lifecycle.

onSaveInstanceState() will be called anytime before onStop() .
onRestoreInstanceState() only will be called when the activity is actually been rescycled.

Have you tried at all to connect the two graphs? The real excitement is when you try to understand how a Fragment's lifecycle interweaves with its Activity's.

When device is rotated, onCreateOptionsMenu and onPrepareOptionsMenu methods are called before onResume.

Fragments can and do receive onActivityResult(), but it doesn't show up in the chart.

http://developer.android.com/reference/android/app/Fragment.html#onActivityResult(int, int, android.content.Intent)

onCreateOptionsMenu() and onResume() have their order swapped on Samsung devices, we've encountered it in Galaxy S4 and Galaxy Ace.

Can't confirm because it happened 6 months ago.

onNewIntent is not mentioned in the diagram at all

missing in Fragment lifecycle: onActivityResult. Maybe it's same as in Activity? Called after onStart()?

    @Override
    public void onActivityResult(int requestCode, int resultCode, Intent data) {

You've documented a 'wierdness' with v4 compat for onResume/onPostResume. It's worth saying that onResume() should be used for normal Activity's and onResumeFragments() when using the v4 compat library. This is only required when the application is waiting for the initial FragmentTransaction's to be completed by the FragmentManager. For instance the application wants to access a Fragment that was inflated during onCreate(). The best place for this is onResumeFragments().

See: http://developer.android.com/reference/android/support/v4/app/FragmentActivity.html#onResumeFragments%28%29

Update the diagram with the quarks introduced with multi-window mode to the lifecycle. Such as the recommendation to have video apps handle playback play/pause in onStart/onStop instead of onResume/onPause

The Activity diagram indicates that onPostCreate() is called regularly after onStart(). However, I am seeing that onPostCreate() seems to be called only once per onCreate(). It is not called again if the Activity calls onStart() again later.

The lifecycle of fragment seems wrong .The fragment will both re-attach and re-create if we re-enter the activity after the system kill the process.
PS: I hate some guy below with bad manner.

First of all, this is awesome. Spotted it in Android Weekly, and it is much more comprehensive than the lifecycle diagram in the Android docs.

It would be awesome to include the order of lifecycle events when another Activity is started. According to the docs, the order of events in a single application is well defined:

1. Activity A's onPause() method executes.
2. Activity B's onCreate(), onStart(), and onResume() methods execute in sequence. (Activity B now has user focus.)
3. Then, if Activity A is no longer visible on screen, its onStop() method executes.

However, I haven't verified this myself (or seen the info reproduced anywhere else).

http://developer.android.com/reference/android/app/Activity.html#onSaveInstanceState%28android.os.Bundle%29

in a nutshell, it won't always get called, for fragment pop it in and out from the backstack won't call it.

it will only get called if the activity is going to be destroyed and it knows about it in advance... (so orientation change - yes, opening another app then closing it - no)

after Activity.onDestroy a call is made to Activity.onDetachedFromWindow

(Reported by Kurt Huwig via personal email)

any chance? onFinishInflate onDraw onSaveInstanceState etc

Can you explain what is fragment restart and why onActivityCreated is not called in it?
I've tried with latest v4 support version 23.3.0 and I can't reproduce the case where onActivityCreated isn't called.

Here is some discussion about that:
http://stackoverflow.com/questions/36858835/onactivitycreated-is-always-called/36858971?noredirect=1#comment61291313_36858971

assuming a Fragment is part of a layout, what is called when?
and when the Fragment is created dynamically?

Fragment.onPause is called before Activity.onPause; ditto for onStop

(Reported by Kurt Huwig via personal email)

Available here: https://plus.google.com/u/0/+ArpitMathur/posts/cT1EuBbxEgN

Can you please at tags via git tag -a "v.0.9.0" -m "Added this and that" and a CHANGELOG.md to the repository such as this.

Fact:
onCreateOptionMenu() called ones but onPrepareOptionMenu() every time.

Proof:
onCreateOptionMenu() is only called once, the first time the options menu is displayed. To update the menu every time it is displayed, see onPrepareOptionsMenu(Menu).

onPrepareOptionMenu() Prepare the Screen's standard options menu to be displayed. This is called right before the menu is shown, every time it is shown

Problem:
Block diagram shows that every time onResume() called both onCreateOptionMenu() and onPrepareOptionMenu() are called. Which is not true.

Solutions:
"Called once, the first time the options menu is displayed or if menu invalidated" comment need to be added there or condition (diamond-like) block with text "first menu display or invalidated" and "yes" and "no" branches

I believe the note about onPostResume() is cut. should read "compatibility" instead of "compat"

Service is simple, i know, but consider putting it.
We could have all android lifecycles in one place.

http://www.klebermota.eti.br/wp-content/service_lifecycle1.png

Based on my experience and this discuss. I supposed that onActivityResult() should invoke after onRestoreInstanceStatus()
https://stackoverflow.com/questions/5059028/state-of-activity-while-in-onactivityresult-question

ActivityThread

According to Android doc: (https://developer.android.com/reference/android/app/Activity.html#onSaveInstanceState(android.os.Bundle))
In Fragment, this method may be called at any time before onDestroy();
But in Activity, this method will be called before onStop() without guarantees against onPause()