Unity工程插件化加载方案
- 宿主工程依赖 VirtualApk implementation com.didi.virtualapk:core:0.9.8.0.1
- 在Application中初始化VirtualApk
@Override
protected void attachBaseContext(Context base) {
super.attachBaseContext(base);
PluginManager.getInstance(base).init();
}
在启动插件前加载插件apk
com.didi.virtualapk.PluginManager.getInstance(context).loadPlugin(apkFile);
启动插件的activity
public static void runPlugin(Context context, Intent intent) {
if (com.didi.virtualapk.PluginManager.getInstance(context).getLoadedPlugin(PLUGIN_PACKAGE_NAME) == null) {
return;
}
if (intent == null) {
intent = new Intent();
}
//PLUGIN_PACKAGE_NAME 插件APK的包名
//PLUGIN_ATY_NAME 要启动的插件APK中的activity的全路径, ex:com.demo.activity.PluginActivity
intent.setComponent(new ComponentName(PLUGIN_PACKAGE_NAME, PLUGIN_ATY_NAME));
context.startActivity(intent);
}
- Unity导出Android 工程文件,在目标activity中添加以下修改
@Override protected void onCreate(Bundle savedInstanceState)
{
//在实例化mUnityPlayer 前修改so文件加载路径
getApplicationInfo().nativeLibraryDir = "/data/data/com.****.****/app_valibs";
requestWindowFeature(Window.FEATURE_NO_TITLE);
super.onCreate(savedInstanceState);
mUnityPlayer = new UnityPlayer(this);
setContentView(mUnityPlayer);
mUnityPlayer.requestFocus();
}
@Override
public String getPackageCodePath() {
File file = new File("/sdcard/unitytest/test.apk");
return file.getAbsolutePath();
}
//指定插件工程的的资源索引
aaptOptions {
//additionalParameters --allow-reserved-package-id,--package-id,0x70
//避免加载插件时,资源id的索引重合
additionalParameters --allow-reserved-package-id,--package-id,0x80
noCompress .unity3d, .ress, .resource, .obb,config.json
}
- 遇到的问题:经过插件话加载的unity工程在执行mUnityPlayer.quit()会崩溃,且没有日常日志,无法定位。
@Override protected void onDestroy ()
{
mUnityPlayer.quit();
