android LifeCycle-简单使用和详细原理解析

2401_86372512

于 2024-09-05 03:00:15 发布

阅读量979

点赞数 21

文章标签： android

本文链接：https://blog.csdn.net/2401_86372512/article/details/141908841

版权

logEE(“resume”)
}
@OnLifecycleEvent(Lifecycle.Event.ON_PAUSE)
fun pause(){
logEE(“pause”)
}
@OnLifecycleEvent(Lifecycle.Event.ON_STOP)
fun stop(){
logEE(“stop”)
}
@OnLifecycleEvent(Lifecycle.Event.ON_DESTROY)
fun destroy(){
logEE(“destroy”)
}
@OnLifecycleEvent(Lifecycle.Event.ON_ANY)
fun any(){
logEE(“any”)
}
}

运行后我们执行如下流程：启动app-点击回退键退出app，查看生命周期日志打印：

效果展示

我们发现所有的生命周期回调都被调用了，并且每个生命周期调用后都会马上同步调用ON_ANY注解的方法

使用LifeCycle处理异常状态

异常状态说明

我所说的异常状态需要举一个例子：

比如我们现在启动了一个耗时任务去请求网络，然后当网络请求完成后要回来更新ui，我们的异常状态就是指网络请求完成前我们主动关闭了activity。正常情况下这个时候就会造成内存泄露，再次更新ui明显是一个异常状态。本例中我们就需要使用LifeCycle解决此类异常状态。

用到的方法

lifecycle.currentState.isAtLeast(Lifecycle.State.STARTED)

测试案例说明和实现

案例说明：

在注册观察者的onCreate方法监听中使用Thread.sleep模拟一个4s耗时任务，然后在Activity中监听任务的回调并打印日志。我们需要模拟两种操作：

不关闭页面等待耗时任务完成，耗时任务结束后查看日志
在耗时任务结束前关闭页面，耗时任务结束后查看日志

代码展示

注册监听的观察者代码：

lifecycle.addObserver(MainObserver {
runOnUiThread {
if(lifecycle.currentState.isAtLeast(Lifecycle.State.CREATED)){
tv.text=“耗时任务完成”
logEE(“耗时任务完成，并成功更新ui”)
}else{
logEE(“生命周期状态不匹配，不能更新ui”)
}
}
})

处理耗时任务的代码：

@OnLifecycleEvent(Lifecycle.Event.ON_CREATE)
fun create(){
thread {
Thread.sleep(4000)
fun0()
}
}

两种情况对应的日志

不关闭页面等待耗时任务完成，耗时任务结束后查看日志：

在耗时任务结束前关闭页面，耗时任务结束后查看日志

结论

是使用LifeCycle的lifecycle.currentState.isAtLeast(Lifecycle.State.CREATED)方法可以判断Activity当前的状态，从而灵活的处理异常状态

LifeCycle实现原理

基本原理

先大概的说一下基本的原理：

我们的AppComponentActivity和FragmentActivity都是继承了ComponentActivity。

ComponentActivity实现了LifecycleOwner接口。

在ComponentActivity的onCreate生命周期回调中会添加一个Fragment

所以我们就是借助Fragment来实现生命周期的观察的

这种实现原理机制并不少见，例如Glide、RxPremission都是用的这种方式实现

我总体上把代码讲解分为了下面四个部分

ComponentActivity中注册Fragment
addObserver添加监听者方法讲解
Fragment中生命周期方法联动回调
如何回调注解方法

看完后把这四部分相关结合起来理解，就能彻底搞懂LifeCycle源码了

对四部分代码进行讲解

ComponentActivity中注册Fragment

注入Fragment

AppComponentActivity

ReportFragment.injectIfNeededIn(this);

android.app.FragmentManager manager = activity.getFragmentManager();
if (manager.findFragmentByTag(REPORT_FRAGMENT_TAG) == null) {
manager.beginTransaction().add(new ReportFragment(), REPORT_FRAGMENT_TAG).commit();
// Hopefully, we are the first to make a transaction.
manager.executePendingTransactions();
}

这里主要负责把Fragment添加到activity中

addObserver方法讲解

方法调用

这个方法会调用到LifecycleRegistry的addObserver

@Override
public void addObserver(@NonNull LifecycleObserver observer) {
State initialState = mState == DESTROYED ? DESTROYED : INITIALIZED;
ObserverWithState statefulObserver = new ObserverWithState(observer, initialState);
ObserverWithState previous = mObserverMap.putIfAbsent(observer, statefulObserver);
LifecycleOwner lifecycleOwner = mLifecycleOwner.get();
boolean isReentrance = mAddingObserverCounter != 0 || mHandlingEvent;
State targetState = calculateTargetState(observer);
mAddingObserverCounter++;
while ((statefulObserver.mState.compareTo(targetState) < 0
&& mObserverMap.contains(observer))) {
pushParentState(statefulObserver.mState);
statefulObserver.dispatchEvent(lifecycleOwner, upEvent(statefulObserver.mState));
popParentState();
// mState / subling may have been changed recalculate
targetState = calculateTargetState(observer);
}

if (!isReentrance) {
// we do sync only on the top level.
sync();
}
mAddingObserverCounter–;
}

首先会创建ObserverWithState对象，用来记录生命周期状态，

State targetState = calculateTargetState(observer);

方法会计算出此时的生命周期状态，

后面是一个while循环，while循环会分发生命周期状态

比如你在onResume中进行注册其实也是可以收到onCreate和onStart的注册回调的，这种注册方式实际上就是粘性注册，安卓系统中电量信息的广播接受者就是一种很好的粘性广播注册案例，与这个粘性注册原理相同

后面代码中的方法调用如下

if (!isReentrance) {
// we do sync only on the top level.
sync();
}

isReentrance为false的条件是，当前没有在moveToState方法中分发消息，或者注册者的数量不等于0。如果满足这个条件就会调用sync()方法分发消息

Fragment中生命周期方法联动回调

ReportFragment中生命周期方法回调

例如：

dispatch(Lifecycle.Event.ON_DESTROY);

private void dispatch(Lifecycle.Event event) {
Activity activity = getActivity();

if (activity instanceof LifecycleOwner) {
Lifecycle lifecycle = ((LifecycleOwner) activity).getLifecycle();
if (lifecycle instanceof LifecycleRegistry) {
((LifecycleRegistry) lifecycle).handleLifecycleEvent(event);
}
}
}

代码中会把Fragment中的所有生命周期回调都调用dispatch方法进行分发，dispatch方法中会调用lifecycle的handleLifecycleEvent方法继续分发

跳到LifecycleRegistry类中，找到handleLifecycleEvent方法

public void handleLifecycleEvent(@NonNull Lifecycle.Event event) {
State next = getStateAfter(event);
moveToState(next);
}

getStateAfter方法主要用来确认事件触发时下一个生命周期的状态，有下面三种：

CREATED、STARTED、DESTROYED

moveToState方法更改生命周期状态并分发，代码如下：

private void moveToState(State next) {
if (mState == next) {
return;
}
mState = next;
if (mHandlingEvent || mAddingObserverCounter != 0) {
mNewEventOccurred = true;
// we will figure out what to do on upper level.
return;
}
mHandlingEvent = true;
sync();
mHandlingEvent = false;
}

moveToState中的sync()方法用来分发生命周期事件到Observer，

sync() 方法

private void sync() {
LifecycleOwner lifecycleOwner = mLifecycleOwner.get();
if (lifecycleOwner == null) {
throw new IllegalStateException(“LifecycleOwner of this LifecycleRegistry is already”

“garbage collected. It is too late to change lifecycle state.”);
}
while (!isSynced()) {
mNewEventOccurred = false;
// no need to check eldest for nullability, because isSynced does it for us.
if (mState.compareTo(mObserverMap.eldest().getValue().mState) < 0) {
backwardPass(lifecycleOwner);
}
Entry<LifecycleObserver, ObserverWithState> newest = mObserverMap.newest();
if (!mNewEventOccurred && newest != null
&& mState.compareTo(newest.getValue().mState) > 0) {
forwardPass(lifecycleOwner);
}
}
mNewEventOccurred = false;
}

下面代码是State的几种状态

public enum State {

DESTROYED,

INITIALIZED,

CREATED,

STARTED,

RESUMED;
}

sync方法的while循环中有如下代码：

if (mState.compareTo(mObserverMap.eldest().getValue().mState) < 0) {
backwardPass(lifecycleOwner);
}

上面这行代码会比较当前生命周期状态和最早被加入到SafeIterableMap中的状态，如果小于零（比如一般第一个被加入的是INITIALIZED状态，当前状态比ONCREATE还小只能是DESTROYED状态了），说明当前生命周期需要被backwardPass处理

Entry<LifecycleObserver, ObserverWithState> newest = mObserverMap.newest();
if (!mNewEventOccurred && newest != null
&& mState.compareTo(newest.getValue().mState) > 0) {
forwardPass(lifecycleOwner);
}

上面代码中newest是最新被添加到mObserverMap中的状态，如果当前生命周期状态大于newest状态，说明状态在前进（比如onCreate到onStart）

继续看backwardPass和forwardPass方法

private void forwardPass(LifecycleOwner lifecycleOwner) {
Iterator<Entry<LifecycleObserver, ObserverWithState>> ascendingIterator =
mObserverMap.iteratorWithAdditions();//获取正序的迭代器
while (ascendingIterator.hasNext() && !mNewEventOccurred) {
Entry<LifecycleObserver, ObserverWithState> entry = ascendingIterator.next();
ObserverWithState observer = entry.getValue();
while ((observer.mState.compareTo(mState) < 0 && !mNewEventOccurred
&& mObserverMap.contains(entry.getKey()))) {
pushParentState(observer.mState);
observer.dispatchEvent(lifecycleOwner, upEvent(observer.mState));
popParentState();
}
}
}

private void backwardPass(LifecycleOwner lifecycleOwner) {
Iterator<Entry<LifecycleObserver, ObserverWithState>> descendingIterator =
mObserverMap.descendingIterator();//获取逆向迭代器
while (descendingIterator.hasNext() && !mNewEventOccurred) {
Entry<LifecycleObserver, ObserverWithState> entry = descendingIterator.next();
ObserverWithState observer = entry.getValue();
while ((observer.mState.compareTo(mState) > 0 && !mNewEventOccurred
&& mObserverMap.contains(entry.getKey()))) {
Event event = downEvent(observer.mState);
pushParentState(getStateAfter(event));
observer.dispatchEvent(lifecycleOwner, event);
popParentState();
}
}
}

forwardPass和backwardPass都有三句重要代码：

pushParentState(getStateAfter(event));
observer.dispatchEvent(lifecycleOwner, event);
popParentState();

pushParentState(getStateAfter(event));

向列表中存入状态

observer.dispatchEvent(lifecycleOwner, event);

向Observer分发状态

popParentState();

弹出上一步代码中存入的状态

查看dispathchEvent方法

void dispatchEvent(LifecycleOwner owner, Event event) {
State newState = getStateAfter(event);
mState = min(mState, newState);
mLifecycleObserver.onStateChanged(owner, event);
mState = newState;
}

这里的mLifecycleObserver.onStateChanged(owner, event);最终会回调到我们声明的注解方法，mLifecycleObserver的实例是ReflectiveGenericLifecycleObserver，ReflectiveGenericLifecycleObserver最终通过反射的方式回调注解方法，这一部分下一节会详细讲

如何回调注解方法

说到注解方法回调就不得不提addObserver方法了，在LifecycleRegistry类的addObserver方法中，我们创建了一个ObserverWithState对象，并放到Map中

实际上在ObserverWithState方法的构造中就会对注解方法进行包装处理，从而最终用反射回调方法，下面开始代码解析：

ObserverWithState方法的构造如下

ObserverWithState(LifecycleObserver observer, State initialState) {
mLifecycleObserver = Lifecycling.lifecycleEventObserver(observer);
mState = initialState;
}

mLifecycleObserver = Lifecycling.lifecycleEventObserver(observer);

这一行代码最终获得的mLifecycleObserver实例的真实类型是ReflectiveGenericLifecycleObserver

ObserverWithState的dispatchEvent方法如下

void dispatchEvent(LifecycleOwner owner, Event event) {
State newState = getStateAfter(event);
mState = min(mState, newState);
mLifecycleObserver.onStateChanged(owner, event);
mState = newState;
}

在dispatchEvent方法中，会调用

mLifecycleObserver.onStateChanged(owner, event);

代码进行消息分发，实际上就是调用ReflectiveGenericLifecycleObserver.onStateChanged方法。

那么我就看看ReflectiveGenericLifecycleObserver类中的代码吧

class ReflectiveGenericLifecycleObserver implements LifecycleEventObserver {
private final Object mWrapped;
private final CallbackInfo mInfo;

ReflectiveGenericLifecycleObserver(Object wrapped) {
mWrapped = wrapped;
mInfo = ClassesInfoCache.sInstance.getInfo(mWrapped.getClass());
}
anged(owner, event);

代码进行消息分发，实际上就是调用ReflectiveGenericLifecycleObserver.onStateChanged方法。

那么我就看看ReflectiveGenericLifecycleObserver类中的代码吧

class ReflectiveGenericLifecycleObserver implements LifecycleEventObserver {
private final Object mWrapped;
private final CallbackInfo mInfo;

ReflectiveGenericLifecycleObserver(Object wrapped) {
mWrapped = wrapped;
mInfo = ClassesInfoCache.sInstance.getInfo(mWrapped.getClass());
}