febs
11/13/2018, 9:10 PMMrNiamh
11/13/2018, 9:11 PMfebs
11/13/2018, 9:12 PMAlan Evans
11/13/2018, 9:12 PMfebs
11/13/2018, 9:22 PMEgor Trutenko
11/14/2018, 10:33 AMonCreate
, onResume
or onDestroy
, you'll anyway end up in Activity source code, because callbacks that you write are called by the Android System through its own codefebs
11/14/2018, 11:47 AMEgor Trutenko
11/14/2018, 11:55 AMSystem Events Looper
-> Activity.*callback name*
-> *your callback*
So when the execution of your callback is over, it returns to what's on top of execution stack, that is, methods in Activity.java
febs
11/14/2018, 11:59 AMEgor Trutenko
11/14/2018, 12:08 PMonCreate
, onResume
, onDestroy
etc., basically everything that you don't call yourself.
I assume you're trying to debug through lifecycle functions in order they are called? onCreate
-> onStart
-> onResume
etc., right? Think of it like they are not executed one right after another - it's system that handles device's resources, so all of these methods are called asynchronously, at any time that you can't predict. That's why you have to place breakpoints in all of them and let execution go as a function finishes and returns execution back to the systemfebs
11/15/2018, 9:51 AM