Hi Lance, Thanks for your reply. You are right, I've missed the onCreate documentation which mentions the onCreate-->finish()->onDestroy path. I guess the android behavior is logical, however the the documentation is not consistent/complete:
* the onStart-->finish()-->onStop is not documented (I don;t remember what I've tested: either onStart->finish() or onResume-->finish, anyway both of them are claimed to be "non killable") * the onCreate -->finish()->on Destroy is inconsistent with the "not killable" declarations of the Life Cycle Table and the Paths of the Activity life cycle diagram. Best Alex On Dec 24, 11:01 am, Lance Nanek <[email protected]> wrote: > It does seem to be mentioned in the documentation for the onCreate > method at > least:http://developer.android.com/intl/zh-CN/reference/android/app/Activit... > > On Dec 23, 9:22 am, alexk-il <[email protected]> wrote: > > > > > Hi, > > > I am confused with the SDK documentation which describes that Activity > > states "onCreate" through "onResume" are "not killable" by the > > system. > > > However, calling finish() in onCreate() (for example, as a response > > to SW error) seems to be working - the Activity goes directly from > > onCreate to onDestroy skipping all the intermediate states. This seems > > to be different from the documentationj - see the Activity states > > diagramm which doesn't show onCreate-->onDestroy > > path:http://developer.android.com/reference/android/app/Activity.html. > > > Am I missing something? > > > Thanks > > Alex -- You received this message because you are subscribed to the Google Groups "Android Beginners" group. NEW! Try asking and tagging your question on Stack Overflow at http://stackoverflow.com/questions/tagged/android To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en
