Analysis of the reason why calling getApplicationContext in the attachBaseContext method of Application returns null
Application extends ContextWapper
So when we call Application's getApplicationContext, we actually call ContextWapper's getApplicationContext method as follows
from ContextWapper.java
@Override
public Context getApplicationContext() {
return mBase.getApplicationContext();
}
mBase is the context passed in when attachBaseContext see the following code
form ContextWapper.java
protected void attachBaseContext(Context base) {
if (mBase != null) {
throw new IllegalStateException("Base context already set");
}
mBase = base;
}
continue to investigateattachBaseContext is a protected method, which is actually called in the attach of Application.java
from Application.java
final void attach(Context context) {
attachBaseContext(context);
mLoadedApk = ContextImpl.getImpl(context).mPackageInfo;
}
Find where attach is calledfrom Instrumentation.java
public Application newApplication(ClassLoader cl, String className, Context context)
throws InstantiationException, IllegalAccessException,
ClassNotFoundException {
Application app = getFactory(context.getPackageName())
.instantiateApplication(cl, className);
app.attach(context);
return app;
}
where newApplication is calledfrom LoadedApk.java
public Application makeApplication(boolean forceDefaultAppClass,
Instrumentation instrumentation) {
if (mApplication != null) {
return mApplication;
}
......................................
try {
java.lang.ClassLoader cl = getClassLoader();
.....................................
ContextImpl appContext = ContextImpl.createAppContext(mActivityThread, this);
app = mActivityThread.mInstrumentation.newApplication(
cl, appClass, appContext);
appContext.setOuterContext(app);
} catch (Exception e) {
}
mActivityThread.mAllApplications.add(app);
mApplication = app;
.................................
return app;
}
OK, look at the code aboveAfter generating an app instance and calling attachBaseContext, the app instance is finally pointed to mApplication
Now we know that the context passed in attachBaseContext is actually a ContextImpl instance
We look at the getApplicationContext method of ContextImpl
from ContextImpl.java
@Override
public Context getApplicationContext() {
return (mPackageInfo != null) ?
mPackageInfo.getApplication() : mMainThread.getApplication();
}
mPackageInfo is actually LoadedApk look downfrom LoadedApk.java
Application getApplication() {
return mApplication;
}
Now I know, in fact, what getApplicaitonContext returns is mApplicationAccording to the makeApplication method of LoadedApk, you can see it
mApplication is assigned after attachBaseContext, so what you get in attachBaseContext is of course NULL
이 내용에 흥미가 있습니까?
현재 기사가 여러분의 문제를 해결하지 못하는 경우 AI 엔진은 머신러닝 분석(스마트 모델이 방금 만들어져 부정확한 경우가 있을 수 있음)을 통해 가장 유사한 기사를 추천합니다:
다양한 언어의 JSONJSON은 Javascript 표기법을 사용하여 데이터 구조를 레이아웃하는 데이터 형식입니다. 그러나 Javascript가 코드에서 이러한 구조를 나타낼 수 있는 유일한 언어는 아닙니다. 저는 일반적으로 '객체'{}...
텍스트를 자유롭게 공유하거나 복사할 수 있습니다.하지만 이 문서의 URL은 참조 URL로 남겨 두십시오.
CC BY-SA 2.5, CC BY-SA 3.0 및 CC BY-SA 4.0에 따라 라이센스가 부여됩니다.