理解Android Context
一. 概述
接触过Android的小伙伴, 一定不会对Context感到陌生, 有大量的场景使用都离不开Context, 下面列举部分常见场景:
- 启动Activity (startActivity)
- 启动服务 (startService)
- 发送广播 (sendBroadcast), 注册广播接收者 (registerReceiver)
- 获取ContentResolver (getContentResolver)
- 获取类加载器 (getClassLoader)
- 打开或创建数据库 (openOrCreateDatabase)
- 获取资源 (getResources)
- …
四大组件,各种资源操作以及其他很多场景都离不开Context, 那么Context到底是何方神圣呢? 中文意思为上下文, 顾名思义就是在某一个场景中本身所包含的一些潜在信息. 举个例子来说明, 比如当下你正在看Gityuan博客 作为一个Context, 那么这个上下文就会隐藏 博客作者, 博客网址, 博客目录等信息, 其中通过Contet.getAuthor()就能返回”Gityuan”. 这就是上下文, 某一个场景背后所隐藏的信息.
1.1 类关系图
回到主题, Android Context本身是一个抽象类. ContextImpl, Activity, Service, Application这些都是Context的直接或间接子类, 下面通过看看这些类的关系,如下:
点击查看大图
图解:
- ContextImpl:
- Application/Activity/Service通过attach() 调用父类ContextWrapper的attachBaseContext(), 从而设置父类成员变量mBase为ContextImpl对象;
- ContextWrapper的核心工作都是交给mBase(即ContextImpl)来完成;
- Application: 四大组件属于某一Application, 获取所在Application:
- Activity/Service: 是通过调用其方法getApplication(),可主动获取当前所在mApplication;
- mApplication是由LoadedApk.makeApplication()过程所初始化的;
- Receiver: 是通过其方法onReceive()的第一个参数指向通当前所在Application,也就是只有接收到广播的时候才能拿到当前的Application对象;
- provider: 目前没有提供直接获取当前所在Application的方法, 但可通过getContext()可以获取当前的ContextImpl.
- Activity/Service: 是通过调用其方法getApplication(),可主动获取当前所在mApplication;
二. 组件初始化
要理解Context, 需要依次来看看四大组件的初始化过程.
2.1 performLaunchActivity
[-> ActivityThread.java]
private Activity performLaunchActivity(ActivityClientRecord r, Intent customIntent) {
...
ActivityInfo aInfo = r.activityInfo;
if (r.packageInfo == null) {
//step 1: 创建LoadedApk对象
r.packageInfo = getPackageInfo(aInfo.applicationInfo, r.compatInfo,
Context.CONTEXT_INCLUDE_CODE);
}
... //component初始化过程
java.lang.ClassLoader cl = r.packageInfo.getClassLoader();
//step 2: 创建Activity对象
Activity activity = mInstrumentation.newActivity(cl, component.getClassName(), r.intent);
...
//step 3: 创建Application对象
Application app = r.packageInfo.makeApplication(false, mInstrumentation);
if (activity != null) {
//step 4: 创建ContextImpl对象
Context appContext = createBaseContextForActivity(r, activity);
CharSequence title = r.activityInfo.loadLabel(appContext.getPackageManager());
Configuration config = new Configuration(mCompatConfiguration);
//step5: 将Application/ContextImpl都attach到Activity对象 [见小节4.1]
activity.attach(appContext, this, getInstrumentation(), r.token,
r.ident, app, r.intent, r.activityInfo, title, r.parent,
r.embeddedID, r.lastNonConfigurationInstances, config,
r.referrer, r.voiceInteractor);
...
int theme = r.activityInfo.getThemeResource();
if (theme != 0) {
activity.setTheme(theme);
}
activity.mCalled = false;
if (r.isPersistable()) {
//step 6: 执行回调onCreate
mInstrumentation.callActivityOnCreate(activity, r.state, r.persistentState);
} else {
mInstrumentation.callActivityOnCreate(activity, r.state);
}
r.activity = activity;
r.stopped = true;
if (!r.activity.mFinished) {
activity.performStart(); //执行回调onStart
r.stopped = false;
}
if (!r.activity.mFinished) {
//执行回调onRestoreInstanceState
if (r.isPersistable()) {
if (r.state != null || r.persistentState != null) {
mInstrumentation.callActivityOnRestoreInstanceState(activity, r.state,
r.persistentState);
}
} else if (r.state != null) {
mInstrumentation.callActivityOnRestoreInstanceState(activity, r.state);
}
}
...
r.paused = true;
mActivities.put(r.token, r);
}
return activity;
}
startActivity的过程最终会在目标进程执行performLaunchActivity()方法, 该方法主要功能:
- 创建对象LoadedApk;
- 创建对象Activity;
- 创建对象Application;
- 创建对象ContextImpl;
- Application/ContextImpl都attach到Activity对象;
- 执行onCreate()等回调;
2.2 handleCreateService
[-> ActivityThread.java]
private void handleCreateService(CreateServiceData data) {
...
//step 1: 创建LoadedApk
LoadedApk packageInfo = getPackageInfoNoCheck(
data.info.applicationInfo, data.compatInfo);
java.lang.ClassLoader cl = packageInfo.getClassLoader();
//step 2: 创建Service对象
service = (Service) cl.loadClass(data.info.name).newInstance();
//step 3: 创建ContextImpl对象
ContextImpl context = ContextImpl.createAppContext(this, packageInfo);
context.setOuterContext(service);
//step 4: 创建Application对象
Application app = packageInfo.makeApplication(false, mInstrumentation);
//step 5: 将Application/ContextImpl都attach到Activity对象 [见小节4.2]
service.attach(context, this, data.info.name, data.token, app,
ActivityManagerNative.getDefault());
//step 6: 执行onCreate回调
service.onCreate();
mServices.put(data.token, service);
ActivityManagerNative.getDefault().serviceDoneExecuting(
data.token, SERVICE_DONE_EXECUTING_ANON, 0, 0);
...
}
整个过程:
- 创建对象LoadedApk;
- 创建对象Service;
- 创建对象ContextImpl;
- 创建对象Application;
- Application/ContextImpl分别attach到Service对象;
- 执行onCreate()回调;
2.3 handleReceiver
[-> ActivityThread.java]
private void handleReceiver(ReceiverData data) {
...
String component = data.intent.getComponent().getClassName();
//step 1: 创建LoadedApk对象
LoadedApk packageInfo = getPackageInfoNoCheck(
data.info.applicationInfo, data.compatInfo);
IActivityManager mgr = ActivityManagerNative.getDefault();
java.lang.ClassLoader cl = packageInfo.getClassLoader();
data.intent.setExtrasClassLoader(cl);
data.intent.prepareToEnterProcess();
data.setExtrasClassLoader(cl);
//step 2: 创建BroadcastReceiver对象
BroadcastReceiver receiver = (BroadcastReceiver)cl.loadClass(component).newInstance();
//step 3: 创建Application对象
Application app = packageInfo.makeApplication(false, mInstrumentation);
//step 4: 创建ContextImpl对象
ContextImpl context = (ContextImpl)app.getBaseContext();
sCurrentBroadcastIntent.set(data.intent);
receiver.setPendingResult(data);
//step 5: 执行onReceive回调 [见小节4.3]
receiver.onReceive(context.getReceiverRestrictedContext(), data.intent);
...
}
整个过程:
- 创建对象LoadedApk;
- 创建对象BroadcastReceiver;
- 创建对象Application;
- 创建对象ContextImpl;
- 执行onReceive()回调;
说明:
- 以上过程是静态广播接收者, 即通过AndroidManifest.xml的标签来申明的BroadcastReceiver;
- 如果是动态广播接收者,则不需要再创建那么多对象, 因为动态广播的注册时进程已创建, 基本对象已创建完成. 那么只需要回调BroadcastReceiver的onReceive()方法即可.
2.4 installProvider
[-> ActivityThread.java]
private IActivityManager.ContentProviderHolder installProvider(Context context,
IActivityManager.ContentProviderHolder holder, ProviderInfo info,
boolean noisy, boolean noReleaseNeeded, boolean stable) {
ContentProvider localProvider = null;
IContentProvider provider;
if (holder == null || holder.provider == null) {
Context c = null;
ApplicationInfo ai = info.applicationInfo;
if (context.getPackageName().equals(ai.packageName)) {
c = context;
} else if (mInitialApplication != null &&
mInitialApplication.getPackageName().equals(ai.packageName)) {
c = mInitialApplication;
} else {
//step 1 && 2: 创建LoadedApk和ContextImpl对象
c = context.createPackageContext(ai.packageName,Context.CONTEXT_INCLUDE_CODE);
}
final java.lang.ClassLoader cl = c.getClassLoader();
//step 3: 创建ContentProvider对象
localProvider = (ContentProvider)cl.loadClass(info.name).newInstance();
provider = localProvider.getIContentProvider();
//step 4: ContextImpl都attach到ContentProvider对象 [见小节4.4]
//step 5: 并执行回调onCreate
localProvider.attachInfo(c, info);
} else {
...
}
...
return retHolder;
}
该方法主要功能:
- 创建对象LoadedApk;
- 创建对象ContextImpl;
- 创建对象ContentProvider;
- ContextImpl都attach到ContentProvider对象;
- 执行onCreate回调;
2.5 handleBindApplication
[-> ActivityThread.java]
private void handleBindApplication(AppBindData data) {
//step 1: 创建LoadedApk对象
data.info = getPackageInfoNoCheck(data.appInfo, data.compatInfo);
...
//step 2: 创建ContextImpl对象;
final ContextImpl appContext = ContextImpl.createAppContext(this, data.info);
//step 3: 创建Instrumentation
mInstrumentation = new Instrumentation();
//step 4: 创建Application对象; [见小节3.2.1]
Application app = data.info.makeApplication(data.restrictedBackupMode, null);
mInitialApplication = app;
//step 5: 安装providers
List providers = data.providers;
installContentProviders(app, providers);
//step 6: 执行Application.Create回调
mInstrumentation.callApplicationOnCreate(app);
该过程主要功能:
- 创建对象LoadedApk
- 创建对象ContextImpl;
- 创建对象Instrumentation;
- 创建对象Application;
- 安装providers;
- 执行Create回调;
三. 核心对象
上面介绍了4大组件以及Application的初始化过程, 接下来再进一步说明其中LoadedApk, ContextImpl, Application的初始化过程.
3.1 创建LoadedApk
3.1.1 AT.getPackageInfo
[-> ActivityThread.java]
public final LoadedApk getPackageInfo(ApplicationInfo ai, CompatibilityInfo compatInfo,
int flags) {
boolean includeCode = (flags&Context.CONTEXT_INCLUDE_CODE) != 0;
//是否违反隐私问题
boolean securityViolation = includeCode && ai.uid != 0
&& ai.uid != Process.SYSTEM_UID && (mBoundApplication != null
? !UserHandle.isSameApp(ai.uid, mBoundApplication.appInfo.uid)
: true);
boolean registerPackage = includeCode && (flags&Context.CONTEXT_REGISTER_PACKAGE) != 0;
...
return getPackageInfo(ai, compatInfo, null, securityViolation, includeCode,
registerPackage);
}
当securityViolation=true,则代表违反隐私问题, 会抛出SecurityException异常.
3.1.2 AT.getPackageInfo
[-> ActivityThread.java]
private LoadedApk getPackageInfo(ApplicationInfo aInfo, CompatibilityInfo compatInfo,
ClassLoader baseLoader, boolean securityViolation, boolean includeCode,
boolean registerPackage) {
final boolean differentUser = (UserHandle.myUserId() != UserHandle.getUserId(aInfo.uid));
synchronized (mResourcesManager) {
WeakReference ref;
if (differentUser) {
ref = null;
} else if (includeCode) {
ref = mPackages.get(aInfo.packageName); //从mPackages查询
} else {
...
}
LoadedApk packageInfo = ref != null ? ref.get() : null;
if (packageInfo == null || (packageInfo.mResources != null
&& !packageInfo.mResources.getAssets().isUpToDate())) {
//创建LoadedApk对象, 此时baseLoader为null
packageInfo = new LoadedApk(this, aInfo, compatInfo, baseLoader,
securityViolation, includeCode &&
(aInfo.flags&ApplicationInfo.FLAG_HAS_CODE) != 0, registerPackage);
...
if (differentUser) {
...
} else if (includeCode) {
//将新创建的LoadedApk加入到mPackages
mPackages.put(aInfo.packageName, new WeakReference(packageInfo));
} else {
...
}
}
return packageInfo;
}
}
该方法主要功能:
- mPackages的数据类型为ArrayMap
- 当mPackages没有找到相应的LoadedApk对象, 则创建该对象并加入到mPackages.
3.1.3 AT.getPackageInfoNoCheck
public final LoadedApk getPackageInfoNoCheck(ApplicationInfo ai,
CompatibilityInfo compatInfo) {
return getPackageInfo(ai, compatInfo, null, false, true, false);
}
除了Activity的初始化, 其他组件初始化都是采用该方法,有默认参数值, 主要功能还是一致的.
- securityViolation=false,则不进行是否违反隐私的监测;
- registerPackage=false, 则在获取类加载器(getClassLoader)时,不会将该package添加到当前所在进程的成员变量pkgDeps.
3.2 创建Application
有了LoadedApk对象, 接下来可以创建Application对象, 该对象一个Apk只会创建一次.
3.2.1 LoadedApk.makeApplication
[-> LoadedApk.java]
public Application makeApplication(boolean forceDefaultAppClass,
Instrumentation instrumentation) {
//保证一个LoadedApk对象只创建一个对应的Application对象
if (mApplication != null) {
return mApplication;
}
String appClass = mApplicationInfo.className;
if (forceDefaultAppClass || (appClass == null)) {
appClass = "android.app.Application"; //设置应用类名
}
java.lang.ClassLoader cl = getClassLoader();
if (!mPackageName.equals("android")) {
initializeJavaContextClassLoader();
}
//创建ContextImpl对象
ContextImpl appContext = ContextImpl.createAppContext(mActivityThread, this);
//创建Application对象, 并将appContext attach到新创建的Application[见3.2.2]
Application app = mActivityThread.mInstrumentation.newApplication(cl, appClass, appContext);
appContext.setOuterContext(app);
...
mActivityThread.mAllApplications.add(app);
mApplication = app; //将刚创建的app赋值给mApplication
...
return app;
}
该方法主要功能:
- 获取当前应用的ClassLoader对象,根据是否为”android”来决定调用initializeJavaContextClassLoader()的过程;
- 根据当前ActivityThread对象来创建相应的ContextImpl对象
- 创建Application对象, 初始化其成员变量:
- mBase指向新创建ContextImpl;
- mLoadedApk指向当前所在的LoadedApk对象;
- 将新创建的Application对象保存到ContextImpl的成员变量mOuterContext.
关于initializeJavaContextClassLoader()的过程, 见文章理解Application初始化的[小节2.9].
关于应用类名采用的是Apk中声明的应用类名,即Manifest.xml中定义的类名. 有两种特殊情况会强制 设置应用类名为”android.app.Application”:
- 当forceDefaultAppClass=true, 目前只有system_server进程初始化包名为”android”的apk过程会调用;
- Apk没有自定义应用类名的情况.
3.2.2 newApplication
[-> Instrumentation.java]
static public Application newApplication(Class clazz, Context context)
throws InstantiationException, IllegalAccessException, ClassNotFoundException {
Application app = (Application)clazz.newInstance(); //创建Application
app.attach(context); //执行attach操作[见小节4.3.5]
return app;
}
3.3 创建ContextImpl
创建ContextImpl的方式有多种, 不同的组件初始化调用不同的方法,如下:
- Activity: 调用createBaseContextForActivity初始化;
- Service/Application: 调用createAppContext初始化;
- Provider: 调用createPackageContext初始化;
- BroadcastReceiver: 直接从Application.getBaseContext()来获取ContextImpl对象;
3.3.1 createBaseContextForActivity
[-> ActivityThread.java]
private Context createBaseContextForActivity(ActivityClientRecord r, final Activity activity) {
int displayId = Display.DEFAULT_DISPLAY;
try {
displayId = ActivityManagerNative.getDefault().getActivityDisplayId(r.token);
} catch (RemoteException e) {
}
//创建ContextImpl对象
ContextImpl appContext = ContextImpl.createActivityContext(
this, r.packageInfo, displayId, r.overrideConfig);
appContext.setOuterContext(activity);
Context baseContext = appContext;
...
return baseContext;
}
[-> ContextImpl.java]
static ContextImpl createActivityContext(ActivityThread mainThread,
LoadedApk packageInfo, int displayId, Configuration overrideConfiguration) {
return new ContextImpl(null, mainThread, packageInfo,
null, null, false,
null, overrideConfiguration, displayId);
}
Activity采用该方法来初始化ContextImpl对象.
3.3.2 createAppContext
[-> ContextImpl.java]
static ContextImpl createAppContext(ActivityThread mainThread, LoadedApk packageInfo) {
if (packageInfo == null) throw new IllegalArgumentException("packageInfo");
return new ContextImpl(null, mainThread, packageInfo,
null, null, false,
null, null, Display.INVALID_DISPLAY);
}
Service/Application采用该方法来初始化ContextImpl对象.
3.3.3 createPackageContext
[-> ContextImpl.java]
public Context createPackageContext(String packageName, int flags)
throws NameNotFoundException {
return createPackageContextAsUser(packageName, flags,
mUser != null ? mUser : Process.myUserHandle());
}
public Context createPackageContextAsUser(String packageName, int flags, UserHandle user)
throws NameNotFoundException {
final boolean restricted = (flags & CONTEXT_RESTRICTED) == CONTEXT_RESTRICTED;
if (packageName.equals("system") || packageName.equals("android")) {
return new ContextImpl(this, mMainThread, mPackageInfo, mActivityToken,
user, restricted, mDisplay, null, Display.INVALID_DISPLAY);
}
//创建LoadedApk
LoadedApk pi = mMainThread.getPackageInfo(packageName, mResources.getCompatibilityInfo(),
flags | CONTEXT_REGISTER_PACKAGE, user.getIdentifier());
if (pi != null) {
//创建ContextImpl
ContextImpl c = new ContextImpl(this, mMainThread, pi,
mActivityToken,user, restricted,
mDisplay, null, Display.INVALID_DISPLAY);
if (c.mResources != null) {
return c;
}
}
}
provider采用该方法来初始化ContextImpl对象.
3.3.4 ContextImpl初始化
[-> ContextImpl.java]
class ContextImpl extends Context {
final ActivityThread mMainThread;
final LoadedApk mPackageInfo;
private final IBinder mActivityToken;
private final String mBasePackageName;
private Context mOuterContext;
//缓存Binder服务
final Object[] mServiceCache = SystemServiceRegistry.createServiceCache();
private ContextImpl(ContextImpl container, ActivityThread mainThread,
LoadedApk packageInfo, IBinder activityToken, UserHandle user, boolean restricted,
Display display, Configuration overrideConfiguration, int createDisplayWithId) {
mOuterContext = this; //ContextImpl对象
mMainThread = mainThread; // ActivityThread赋值
mPackageInfo = packageInfo; // LoadedApk赋值
mBasePackageName = packageInfo.mPackageName; //mBasePackageName等于“android”
...
}
}
四. Context attach过程
4.1 Activity
[-> Activity.java]
final void attach(Context context, ActivityThread aThread,
Instrumentation instr, IBinder token, int ident,
Application application, Intent intent, ActivityInfo info,
CharSequence title, Activity parent, String id,
NonConfigurationInstances lastNonConfigurationInstances,
Configuration config, String referrer, IVoiceInteractor voiceInteractor) {
attachBaseContext(context); //调用父类方法设置mBase.
mUiThread = Thread.currentThread();
mMainThread = aThread;
mApplication = application;
mIntent = intent;
mComponent = intent.getComponent();
mActivityInfo = info;
...
}
将新创建的ContextImpl赋值到父类ContextWrapper.mBase变量.
4.2 Service
[-> Service.java]
public final void attach(
Context context,
ActivityThread thread, String className, IBinder token,
Application application, Object activityManager) {
attachBaseContext(context); //调用父类方法设置mBase.
mClassName = className;
mToken = token;
mApplication = application;
...
}
将新创建的ContextImpl赋值到父类ContextWrapper.mBase变量.
4.3 BroadcastReceiver
[-> ContextImpl.java]
final Context getReceiverRestrictedContext() {
if (mReceiverRestrictedContext != null) {
return mReceiverRestrictedContext;
}
return mReceiverRestrictedContext = new ReceiverRestrictedContext(getOuterContext());
}
对于广播来说Context的传递过程, 跟其他组件完全不同. 广播是在onCreate过程通过参数将ReceiverRestrictedContext传递过去的. 此处getOuterContext()返回的是ContextImpl对象.
4.4 ContentProvider
[-> ContentProvider.java]
public void attachInfo(Context context, ProviderInfo info) {
attachInfo(context, info, false);
}
private void attachInfo(Context context, ProviderInfo info, boolean testing) {
mNoPerms = testing;
if (mContext == null) {
//将新创建ContextImpl对象保存到ContentProvider对象的成员变量mContext
mContext = context;
...
if (info != null) {
setReadPermission(info.readPermission);
setWritePermission(info.writePermission);
setPathPermissions(info.pathPermissions);
mExported = info.exported;
mSingleUser = (info.flags & ProviderInfo.FLAG_SINGLE_USER) != 0;
setAuthorities(info.authority);
}
// 执行onCreate回调;
ContentProvider.this.onCreate();
}
}
该方法主要功能:
- 将新创建ContextImpl对象保存到ContentProvider对象的成员变量mContext;
- 可通过getContext()获取该ContextImpl;
- 执行onCreate回调;
4.5 Application
[-> Application.java]
final void attach(Context context) {
attachBaseContext(context); //Application的mBase
mLoadedApk = ContextImpl.getImpl(context).mPackageInfo;
}
该方法主要功能:
- 将新创建的ContextImpl对象保存到Application的父类成员变量mBase;
- 将当前所在的LoadedApk对象保存到Application的父员变量mLoadedApk;
4.6 Context核心方法
再来说说Context相关的几个核心方法:
| 对象 | 方法 | 返回值类型 | 含义 |
|---|---|---|---|
| Activity | getApplication() | Application | 获取Activity所属的mApplication |
| Service | getApplication() | Application | 获取Service所属的mApplication |
| ContextWrapper | getBaseContext | ContextImpl | 获取mBase,即ContextImpl |
| ContextWrapper | getApplicationContext | Application | 见小节4.6.1 |
| ContextImpl | getApplicationContext | Application | 见小节4.6.1 |
| ContextImpl | getOuterContext | ContextImpl | 获取mOuterContext |
| ContextImpl | getApplicationInfo | ApplicationInfo | mPackageInfo.mApplicationInfo |
关于Application:
- Activity的mApplication是由 [小节3.2.1]makeApplication() 过程创建, 由 [小节4.1]赋值;
- Service的mApplication是由 [小节3.2.1]makeApplication() 过程创建, 由 [小节4.2]赋值;
- Receiver是通过其方法onReceive()的第一个参数指向当前所在Application;
- provider无法获取application,因为其所在application不一定初始化;
关于mOuterContext: ContextImpl的mOuterContext,默认值是由[小节3.3.4]ContextImpl初始化过程创建. 但往往通过调用setOuterContext()使其指向外部的Context;
- makeApplication过程, mOuterContext指向Application;
- handleCreateService()过程, mOuterContext指向Service;
- performLaunchActivity的createBaseContextForActivity过程, mOuterContext指向Activity;
- BroadcastReceiver/Provider则采用默认值ContextImpl;
4.6.1 CI.getApplicationContext
class ContextImpl extends Context {
public Context getApplicationContext() {
return (mPackageInfo != null) ?
mPackageInfo.getApplication() : mMainThread.getApplication();
}
}
//上述mPackageInfo的数据类型为LoadedApk
public final class LoadedApk {
Application getApplication() {
return mApplication;
}
}
//上述mMainThread为ActivityThread
public final class ActivityThread {
public Application getApplication() {
return mInitialApplication;
}
}
- mPackageInfo.getApplication(): 返回的是LoadedApk.mApplication
- Activity/Servie/BroadcastReceiver/Application初始化, 调用[小节3.2.1]makeApplication()完成; 但对于同一个apk只会执行一次;
- mMainThread.getApplication(): 返回的是ActivityThread.mInitialApplication
- ActivityThread.handleBindApplication()赋值;
- system_server进程的AT.attach()赋值;
五. 总结
5.1 组件初始化
下面用一幅图来看看核心组件的初始化过程会创建哪些对象:
| 类型 | LoadedApk | ContextImpl | Application | 创建相应对象 | 回调方法 |
|---|---|---|---|---|---|
| Activity | √ | √ | √ | Activity | onCreate |
| Service | √ | √ | √ | Service | onCreate |
| Receiver | √ | √ | √ | BroadcastReceiver | onReceive |
| Provider | √ | √ | × | ContentProvider | onCreate |
| Application | √ | √ | √ | Application | onCreate |
每个Apk都对应唯一的application对象和LoadedApk对象, 当Apk中任意组件的创建过程中, 当其所对应的的LoadedApk和Application没有初始化则会创建, 且只会创建一次.
另外大家会注意到唯有Provider在初始化过程并不会去创建所相应的Application对象.也就意味着当有多个Apk运行在同一个进程的情况下, 第二个apk通过Provider初始化过程再调用getContext().getApplicationContext()返回的并非Application对象, 而是NULL. 这里要注意会抛出空指针异常.
5.2 Context attach过程
- Application:
- 调用attachBaseContext()将新创建ContextImpl赋值到父类ContextWrapper.mBase变量;
- 可通过getBaseContext()获取该ContextImpl;
- Activity/Service:
- 调用attachBaseContext() 将新创建ContextImpl赋值到父类ContextWrapper.mBase变量;
- 可通过getBaseContext()获取该ContextImpl;
- 可通过getApplication()获取其所在的Application对象;
- ContentProvider:
- 调用attachInfo()将新创建ContextImpl保存到ContentProvider.mContext变量;
- 可通过getContext()获取该ContextImpl;
- BroadcastReceiver:
- 在onCreate过程通过参数将ReceiverRestrictedContext传递过去的.
- ContextImpl:
- 可通过getApplicationContext()获取Application;
5.3 Context使用场景
| 类型 | startActivity | startService | bindService | sendBroadcast | registerReceiver | getContentResolver |
|---|---|---|---|---|---|---|
| Activity | √ | √ | √ | √ | √ | √ |
| Service | - | √ | √ | √ | √ | √ |
| Receiver | - | √ | × | √ | - | √ |
| Provider | - | √ | √ | √ | √ | √ |
| Application | - | √ | √ | √ | √ | √ |
说明: (图中第一列代表不同的Context, √代表允许在该Context执行相应的操作; ×代表不允许; -代表分情况讨论)
- 当Context为Receiver的情况下:
- 不允许执行bindService()操作, 由于限制性上下文(ReceiverRestrictedContext)所决定的,会直接抛出异常.
- registerReceiver是否允许取决于receiver;
- 当receiver == null用于获取sticky广播, 允许使用;
- 否则不允许使用registerReceiver;
- 纵向来看startActivity操作
- 当为Activity Context则可直接使用;
- 当为其他Context, 则必须带上FLAG_ACTIVITY_NEW_TASK flags才能使用;
- 另外UI相关要Activity中使用.
- 除了以上情况, 其他的操作都是被允许执行.
5.4 getApplicationContext
绝大多数情况下, getApplication()和getApplicationContext()这两个方法完全一致, 返回值也相同; 那么两者到底有什么区别呢? 真正理解这个问题的人非常少. 接下来彻底地回答下这个问题:
getApplicationContext()这个的存在是Android历史原因. 我们都知道getApplication()只存在于Activity和Service对象; 那么对于BroadcastReceiver和ContentProvider却无法获取Application, 这时就需要一个能在Context上下文直接使用的方法, 那便是getApplicationContext().
两者对比:
- 对于Activity/Service来说, getApplication()和getApplicationContext()的返回值完全相同; 除非厂商修改过接口;
- BroadcastReceiver在onReceive的过程, 能使用getBaseContext().getApplicationContext获取所在Application, 而无法使用getApplication;
- ContentProvider能使用getContext().getApplicationContext()获取所在Application. 绝大多数情况下没有问题, 但是有可能会出现空指针的问题, 情况如下:
当同一个进程有多个apk的情况下, 对于第二个apk是由provider方式拉起的, 前面介绍过provider创建过程并不会初始化所在application, 此时执行 getContext().getApplicationContext()返回的结果便是NULL. 所以对于这种情况要做好判空.
Tips: 如果对于Application理解不够深刻, 建议getApplicationContext()方法谨慎使用, 做好是否为空的判定,防止出现空指针异常.
以上内容转自：Gityuan的博客http://gityuan.com/2017/04/09/android_context/
---------------------------------------------------------------------分割线--------------------------------------------------------------------------------
以下内容为本人的一些总结：
1.一个进程一个ActivityThread，一个ActivityThread一个调用一次IActivityManager#attach（），就是只调用一次ActivityThread#handleBindApplication。
2.LoadedApk和Application是在handleBindApplication首先创建，当然，如果在handleBindApplication中创建失败，在启动四大组件时也会创建（ContentProvider除外，ContentProvider不会创建Application）
3.在handleBindApplication（）中关键代码的顺序是创建LoadedApk->ContextImpl（绑定到Instrumentation）->创建Instrumentation->创建Application->install providers->调用Application#oncreate
4.需要注意的，Application#onCreate在install providers后面调用，所以onCreate中初始化的对象不要在ContentProvider初始化中使用。一个进程中可以运行多个apk，而第二个apk起来时不会再调用一次handleBindApplication,而LoadedApk是以包名为key保存在ActivityThread的mPackages：ArrayMap中的，而每个LoadedApk对应一个Application对象，Application统一调用LoadedAp#makeApplication（）去获取，有则直接返回，没有则创建一个后返回。
5.install provider时，会去获取LoadedApk（使用统一接口getPackageInfoxxx(),有则返回，没有则创建后返回一个），但是不会去获取Application,这样就会导致上面的文章所说的那种特殊情况“当同一个进程有多个apk的情况下, 对于第二个apk是由provider方式拉起的, 前面介绍过provider创建过程并不会初始化所在application, 此时执行 getContext().getApplicationContext()返回的结果便是NULL”