Android中Lifecycle的原理詳解
Lifecycle是Android Architecture Components的成員,是一個(gè)生命周期感知組件,能夠感知Activity、Fragment等組件的生命周期變化,并將變化通知到已注冊(cè)的觀察者。正確的使用有助于更好地組織代碼,減少內(nèi)存泄漏,增強(qiáng)穩(wěn)定。下面分析他的實(shí)現(xiàn)原理,看看到底只怎么感知生命周期的。
一、基本使用
1、引入依賴庫(kù)
dependencies {
def lifecycle_version = "2.5.0-alpha01"
def arch_version = "2.1.0"
implementation "androidx.lifecycle:lifecycle-viewmodel:$lifecycle_version"
implementation "androidx.lifecycle:lifecycle-livedata:$lifecycle_version"
implementation "androidx.lifecycle:lifecycle-runtime:$lifecycle_version"
//非java8使用
annotationProcessor "androidx.lifecycle:lifecycle-compiler:$lifecycle_version"
//java8使用
implementation "androidx.lifecycle:lifecycle-common-java8:$lifecycle_version"
}2、自定義一個(gè)類實(shí)現(xiàn)LifecycleObserver,在類中監(jiān)聽生命周期回調(diào)
public class BaseJsApi implements LifecycleObserver {
@OnLifecycleEvent(Lifecycle.Event.ON_CREATE)
void create() {
onCreate();
}
@OnLifecycleEvent(Lifecycle.Event.ON_DESTROY)
void destroy() {
onDestroy();
}
@OnLifecycleEvent(Lifecycle.Event.ON_RESUME)
void resume() {
onResume();
}
@OnLifecycleEvent(Lifecycle.Event.ON_PAUSE)
void pause() {
onPause();
}
……………………………………
}3、在Activity或者fragment中注冊(cè)。
getLifecycle().addObserver(getJsBridge());
通過(guò)以上兩步就可以感知當(dāng)前Activity的生命周期了,非常的簡(jiǎn)便實(shí)用。
二、LifecycleObserver接口和LifecycleOwner接口
public interface LifecycleObserver {
}
public interface LifecycleOwner {
@NonNull
Lifecycle getLifecycle();
}LifecycleObserver是一個(gè)空接口,LifecycleOwner提供getLifecycle返回Lifecycle,該接口由ComponentActivity實(shí)現(xiàn),提供了getLifecycle的實(shí)現(xiàn)。
三、getLifecycle()
getLifecycle方法實(shí)際上是調(diào)用的ComponentActivity的getLifecycle方法,通過(guò)查看,Activity確實(shí)也是繼承的ComponentActivity,該方法返回mLifecycleRegistry對(duì)象,該對(duì)象繼承自Lifecycle,具體實(shí)現(xiàn)了添加觀察者,移出觀察者的方法,還定義了一個(gè)生命周期的枚舉。
public class LifecycleRegistry extends Lifecycle {
}
public abstract class Lifecycle {
@MainThread
public abstract void addObserver(@NonNull LifecycleObserver observer);
@MainThread
public abstract void removeObserver(@NonNull LifecycleObserver observer);
@MainThread
@NonNull
public abstract State getCurrentState();
public enum Event {
ON_CREATE,
ON_START,
ON_RESUME,
ON_PAUSE,
ON_STOP,
ON_DESTROY,
ON_ANY;
…………………………………………
}
………………………………
}也就可以看出getLifecycle().addObserver實(shí)際上就是執(zhí)行LifecycleRegistry的addObserver的方法添加觀察者,做一個(gè)小總結(jié)如下:
觀察者實(shí)現(xiàn)LifecycleObserver,實(shí)現(xiàn)需要的生命周期。在Activity、Fragment中添通過(guò)getLifecycle().addObserver加觀察者。實(shí)際上調(diào)用的是ComponentActivity的getLifecycle方法返回mLifecycleRegistry。調(diào)用LifecycleRegistry的addObserver加觀察者。三、添加觀察者的流程
詳情看注釋:
@Override
public void addObserver(@NonNull LifecycleObserver observer) {
//檢查是否在主線程
enforceMainThreadIfNeeded("addObserver");
//設(shè)置狀態(tài)值
State initialState = mState == DESTROYED ? DESTROYED : INITIALIZED;
//將觀察者和初始化的值封裝到ObserverWithState中
ObserverWithState statefulObserver = new ObserverWithState(observer, initialState);
//以觀察者為key,statefulObserver為value放到hashMap集合中
ObserverWithState previous = mObserverMap.putIfAbsent(observer, statefulObserver);
//不為null表示之前已經(jīng)放進(jìn)去了,否則沒(méi)放進(jìn)去,放進(jìn)去了就添加結(jié)束
if (previous != null) {
return;
}
//獲取被觀察者對(duì)象,即Activity,如果被銷毀了,則結(jié)束
LifecycleOwner lifecycleOwner = mLifecycleOwner.get();
if (lifecycleOwner == null) {
// it is null we should be destroyed. Fallback quickly
return;
}
//mAddingObserverCounter 表示正在添加的觀察者的數(shù)量,
//開始添加新的observe之前,對(duì)該變量進(jìn)行++操作,添加完成后,進(jìn)行--操作。
//mHandlingEvent表示是否正在處理
boolean isReentrance = mAddingObserverCounter != 0 || mHandlingEvent;
//計(jì)算狀態(tài),進(jìn)行while循環(huán)
State targetState = calculateTargetState(observer);
mAddingObserverCounter++;
//新添加的LifecycleObserver ,會(huì)不斷更新自己的生命周期到指定的targetState
while ((statefulObserver.mState.compareTo(targetState) < 0
&& mObserverMap.contains(observer))) {
//添加狀態(tài)到list,計(jì)算當(dāng)前狀態(tài),用于計(jì)算狀態(tài)calculateTargetState
pushParentState(statefulObserver.mState);
//
final Event event = Event.upFrom(statefulObserver.mState);
if (event == null) {
throw new IllegalStateException("no event up from " + statefulObserver.mState);
}
//生命周期分發(fā):分發(fā)到mLifecycleObserver里面
statefulObserver.dispatchEvent(lifecycleOwner, event);
//移除狀態(tài)到list
popParentState();
// mState / subling may have been changed recalculate
//重新計(jì)算狀態(tài)
targetState = calculateTargetState(observer);
}
//沒(méi)有事件正在處理,或者是添加了observe,就需要重新同步一次狀態(tài),下面詳細(xì)介紹
if (!isReentrance) {
// we do sync only on the top level.
sync();
}
mAddingObserverCounter--;
}//計(jì)算狀態(tài)規(guī)則
private State calculateTargetState(LifecycleObserver observer) {
//在map中獲取到當(dāng)前observer的前一個(gè)observer
Map.Entry<LifecycleObserver, ObserverWithState> previous = mObserverMap.ceil(observer);
//前一個(gè)observer的state
State siblingState = previous != null ? previous.getValue().mState : null;
//如果是嵌套添加observer,獲取父級(jí)observer的狀態(tài)
State parentState = !mParentStates.isEmpty() ? mParentStates.get(mParentStates.size() - 1)
: null;
//獲取最小狀態(tài),DESTROYED < INITIALIZED < CREATED < STARTED < RESUMED
return min(min(mState, siblingState), parentState);
}四、綁定生命周期
上面介紹了addObserver的流程,在ComponentActivity的onCreate方法中:
ReportFragment.injectIfNeededIn(this);
ReportFragment是一個(gè)Fragment,它負(fù)責(zé)分派生命周期的事件,injectIfNeededIn()就是在當(dāng)前的Activity里添加一個(gè)ReportFragment,和glide的綁定生命周期比較類似。
public static void injectIfNeededIn(Activity activity) {
//當(dāng)API>=29注冊(cè)registerIn綁定生命周期
if (Build.VERSION.SDK_INT >= 29) {
// On API 29+, we can register for the correct Lifecycle callbacks directly
LifecycleCallbacks.registerIn(activity);
}
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();
}
}當(dāng)API>=29是通過(guò)Application.ActivityLifecycleCallbacks的方式注冊(cè)生命周期, 以onStart為例,其他onResume、onPause等類似:
@Override
public void onStart() {
super.onStart();
dispatchStart(mProcessListener);
dispatch(Lifecycle.Event.ON_START);
}重點(diǎn)看看dispatch:
private void dispatch(@NonNull Lifecycle.Event event) {
//當(dāng)API<29分發(fā)dispatch綁定生命周期
if (Build.VERSION.SDK_INT < 29) {
// Only dispatch events from ReportFragment on API levels prior
// to API 29. On API 29+, this is handled by the ActivityLifecycleCallbacks
// added in ReportFragment.injectIfNeededIn
dispatch(getActivity(), event);
}
}不管是pplication.ActivityLifecycleCallbacks還是當(dāng)前fragment的生命周期方式都會(huì)執(zhí)行如下dispatch:
static void dispatch(@NonNull Activity activity, @NonNull Lifecycle.Event event) {
if (activity instanceof LifecycleRegistryOwner) {
((LifecycleRegistryOwner) activity).getLifecycle().handleLifecycleEvent(event);
return;
}
if (activity instanceof LifecycleOwner) {
Lifecycle lifecycle = ((LifecycleOwner) activity).getLifecycle();
if (lifecycle instanceof LifecycleRegistry) {
((LifecycleRegistry) lifecycle).handleLifecycleEvent(event);
}
}
}調(diào)用LifecycleRegistry的handleLifecycleEvent將生命周期分發(fā)出去,LifecycleRegistry上面已經(jīng)介紹過(guò)了addObserve邏輯了,代碼比較長(zhǎng),只顯示關(guān)鍵代碼:
handleLifecycleEvent -> moveToState -> 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.");
}
//沒(méi)有同步過(guò),則同步
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) {
//如果ObserverWithState的state小于當(dāng)前state,那么就調(diào)用forwardPass方法,
backwardPass(lifecycleOwner);
}
Map.Entry<LifecycleObserver, ObserverWithState> newest = mObserverMap.newest();
if (!mNewEventOccurred && newest != null
&& mState.compareTo(newest.getValue().mState) > 0) {
//如果大于當(dāng)前state,那么就調(diào)用backwardPass方法。
forwardPass(lifecycleOwner);
}
}
mNewEventOccurred = false;
}backwardPass和forwardPass的代碼都會(huì)調(diào)用:
observer.dispatchEvent(lifecycleOwner, event)
static class ObserverWithState {
State mState;
LifecycleEventObserver mLifecycleObserver;
ObserverWithState(LifecycleObserver observer, State initialState) {
mLifecycleObserver = Lifecycling.lifecycleEventObserver(observer);
mState = initialState;
}
void dispatchEvent(LifecycleOwner owner, Event event) {
State newState = event.getTargetState();
mState = min(mState, newState);
mLifecycleObserver.onStateChanged(owner, event);
mState = newState;
}
}調(diào)用了Lifecycling.getCallback方法來(lái)獲得mLifecycleObserver的實(shí)例,通過(guò)這個(gè)實(shí)例調(diào)用onStateChanged:
static LifecycleEventObserver lifecycleEventObserver(Object object) {
boolean isLifecycleEventObserver = object instanceof LifecycleEventObserver;
boolean isFullLifecycleObserver = object instanceof FullLifecycleObserver;
if (isLifecycleEventObserver && isFullLifecycleObserver) {
return new FullLifecycleObserverAdapter((FullLifecycleObserver) object,
(LifecycleEventObserver) object);
}
if (isFullLifecycleObserver) {
return new FullLifecycleObserverAdapter((FullLifecycleObserver) object, null);
}
if (isLifecycleEventObserver) {
return (LifecycleEventObserver) object;
}
//通過(guò)反射,找到Lifecycle 自動(dòng)生成的類
final Class<?> klass = object.getClass();
int type = getObserverConstructorType(klass);
if (type == GENERATED_CALLBACK) {
List<Constructor<? extends GeneratedAdapter>> constructors =
sClassToAdapters.get(klass);
if (constructors.size() == 1) {
GeneratedAdapter generatedAdapter = createGeneratedAdapter(
constructors.get(0), object);
最終使用生成的Adapter,創(chuàng)建SingleGeneratedAdapterObserver
return new SingleGeneratedAdapterObserver(generatedAdapter);
}
GeneratedAdapter[] adapters = new GeneratedAdapter[constructors.size()];
for (int i = 0; i < constructors.size(); i++) {
adapters[i] = createGeneratedAdapter(constructors.get(i), object);
}
return new CompositeGeneratedAdaptersObserver(adapters);
}
return new ReflectiveGenericLifecycleObserver(object);
}class SingleGeneratedAdapterObserver implements LifecycleEventObserver {
private final GeneratedAdapter mGeneratedAdapter;
SingleGeneratedAdapterObserver(GeneratedAdapter generatedAdapter) {
mGeneratedAdapter = generatedAdapter;
}
@Override
public void onStateChanged(@NonNull LifecycleOwner source, @NonNull Lifecycle.Event event) {
mGeneratedAdapter.callMethods(source, event, false, null);
mGeneratedAdapter.callMethods(source, event, true, null);
}
}到這里會(huì)根據(jù)依賴中添加的annotationProcessor "androidx.lifecycle:lifecycle-compiler:2.2.0"根據(jù)不同生命周期注解生成不同的類,整個(gè)過(guò)程還是比較復(fù)雜的。整體過(guò)程如下圖:

總結(jié)
到此這篇關(guān)于Android中Lifecycle的原理詳解的文章就介紹到這了,更多相關(guān)Android Lifecycle原理內(nèi)容請(qǐng)搜索腳本之家以前的文章或繼續(xù)瀏覽下面的相關(guān)文章希望大家以后多多支持腳本之家!
相關(guān)文章
Android sqlite cursor的遍歷實(shí)例詳解
在本篇內(nèi)容里小編給大家整理的是一篇關(guān)于Android sqlite cursor的遍歷的相關(guān)實(shí)例及知識(shí)點(diǎn),需要的朋友們可以學(xué)習(xí)下。2021-06-06
Android中將Bitmap對(duì)象以PNG格式保存在內(nèi)部存儲(chǔ)中的方法
在Android中進(jìn)行圖像處理的任務(wù)時(shí),有時(shí)我們希望將處理后的結(jié)果以圖像文件的格式保存在內(nèi)部存儲(chǔ)空間中,本文以此為目的,介紹將Bitmap對(duì)象的數(shù)據(jù)以PNG格式保存下來(lái)的方法2017-08-08
3種Android隱藏頂部狀態(tài)欄及標(biāo)題欄的方法
這篇文章主要為大家詳細(xì)介紹了3種Android隱藏頂部狀態(tài)欄及標(biāo)題欄的方法,還涉及一種隱藏Android 4.0平板底部狀態(tài)欄的方法,感興趣的小伙伴們可以參考一下2016-02-02
Android開發(fā)中的數(shù)據(jù)庫(kù)事務(wù)用法分析
這篇文章主要介紹了Android開發(fā)中的數(shù)據(jù)庫(kù)事務(wù)用法,分析了Android數(shù)據(jù)庫(kù)事務(wù)的功能、使用方法與相關(guān)注意事項(xiàng),需要的朋友可以參考下2016-06-06
總結(jié)Android中多線程更新應(yīng)用的頁(yè)面信息的方式
這篇文章主要介紹了總結(jié)Android中多線程更新應(yīng)用的頁(yè)面信息的方式,文中共總結(jié)了runOnUiThread、Handler、AsyncTask異步以及View直接在UI線程中更新的方法,需要的朋友可以參考下2016-02-02
Android自定義View實(shí)現(xiàn)廣告信息上下滾動(dòng)效果
這篇文章主要為大家詳細(xì)介紹了Android自定義View實(shí)現(xiàn)廣告信息上下滾動(dòng)的具體代碼,感興趣的小伙伴們可以參考一下2016-05-05
安卓(android)仿電商app商品詳情頁(yè)按鈕浮動(dòng)效果
很多電商類app的商品詳情頁(yè)(其他app也有類似效果,比如qq音樂(lè))都有這么一個(gè)效果:當(dāng)用戶向上滑動(dòng)頁(yè)面內(nèi)容超過(guò)一定距離后,中間的標(biāo)題欄會(huì)卡在頂部,往下拉回到固定高度后又會(huì)消失。那么如何實(shí)現(xiàn)這個(gè)效果呢?跟著小編一起來(lái)學(xué)習(xí)學(xué)習(xí)。2016-08-08

