分享

[Android]腾讯Tinker热修复框架简单使用

 quasiceo 2018-08-14

前言

目前我们所知的热修复方案有阿里的AndFix、美团的Robust以及QZone的超级补丁方案,还有本篇的Tinker,如何在我们的自开发的软件上选用合适的方案呢?

先看看各家的框架效能对比,在作参考。


总体来说:

  1. AndFix作为native解决方案,首先面临的是稳定性与兼容性问题,更重要的是它无法实现类替换,它是需要大量额外的开发成本的;
  2. Robust兼容性与成功率较高,但是它与AndFix一样,无法新增变量与类只能用做的bugFix方案;
  3. Qzone方案可以做到发布产品功能,但是它主要问题是插桩带来Dalvik的性能问题,以及为了解决Art下内存地址问题而导致补丁包急速增大的。

可以看出,Tinker热补丁方案既支持类、So和资源的替换,还支持了2.x-7.x平台。我们不仅可以用做bugfix,甚至可以替代功能的发布,况且Tinker已经在数亿Android端的微信上运行使用,这个噱头你还不用?

使用说明

Tinker提供了两种接入方式,gradle接入和命令行接入,这里先说明gradle的方式,这也是比较推荐的方式。

1.在项目的build.gradle中,添加tinker-patch-gradle-plugin的依赖:

  1. buildscript {
  2. dependencies {
  3. classpath ('com.tencent.tinker:tinker-patch-gradle-plugin:1.7.10')
  4. }
  5. }
2.然后在app的gradle文件app/build.gradle,我们需要添加tinker的库依赖以及apply tinker的gradle插件.
  1. dependencies {
  2. //可选,用于生成application类
  3. provided('com.tencent.tinker:tinker-android-anno:1.7.10')
  4. //tinker的核心库
  5. compile('com.tencent.tinker:tinker-android-lib:1.7.10')
  6. }
  1. //apply tinker插件
  2. apply plugin: 'com.tencent.tinker.patch'

3.在/app/build.gradle中加入tinkerPatch task 脚本,
  1. def bakPath = file("${buildDir}/bakApk/")

  2. ext {
  3. //for some reason, you may want to ignore tinkerBuild, such as instant run debug build?
  4. tinkerEnabled = true

  5. //for normal build
  6. //old apk file to build patch apk
  7. tinkerOldApkPath = "${bakPath}/app-release-0601-14-29-28.apk"
  8. //proguard mapping file to build patch apk
  9. tinkerApplyMappingPath = "${bakPath}/app-release-0601-14-29-28-mapping.txt"
  10. //resource R.txt to build patch apk, must input if there is resource changed
  11. tinkerApplyResourcePath = "${bakPath}/app-release-0601-14-29-28-R.txt"

  12. //only use for build all flavor, if not, just ignore this field
  13. // tinkerBuildFlavorDirectory = "${bakPath}/app-0526-17-40-51"
  14. }

  15. //这个方法其实就是定义了一个tink_id
  16. def getSha() {
  17. try {
  18. String tinkId = "tink_id_000000000"
  19. if (tinkId == null) {
  20. throw new RuntimeException("you should add tinkeId to system path or just input test value, such as 'testTinkerId'")
  21. }
  22. return tinkId
  23. } catch (Exception e) {
  24. throw new RuntimeException("you should add tinkeId to system path or just input test value, such as 'testTinkerId'")
  25. }
  26. }


  27. def getOldApkPath() {
  28. return hasProperty("OLD_APK") ? OLD_APK : ext.tinkerOldApkPath
  29. }

  30. def getApplyMappingPath() {
  31. return hasProperty("APPLY_MAPPING") ? APPLY_MAPPING : ext.tinkerApplyMappingPath
  32. }

  33. def getApplyResourceMappingPath() {
  34. return hasProperty("APPLY_RESOURCE") ? APPLY_RESOURCE : ext.tinkerApplyResourcePath
  35. }

  36. def getTinkerIdValue() {
  37. return hasProperty("TINKER_ID") ? TINKER_ID : getSha()
  38. }

  39. def buildWithTinker() {
  40. return hasProperty("TINKER_ENABLE") ? TINKER_ENABLE : ext.tinkerEnabled
  41. }

  42. def getTinkerBuildFlavorDirectory() {
  43. return ext.tinkerBuildFlavorDirectory
  44. }

  45. if (buildWithTinker()) {
  46. apply plugin: 'com.tencent.tinker.patch'

  47. tinkerPatch {
  48. /**
  49. * necessary,default 'null'
  50. * the old apk path, use to diff with the new apk to build
  51. * add apk from the build/bakApk
  52. */
  53. oldApk = getOldApkPath()
  54. /**
  55. * optional,default 'false'
  56. * there are some cases we may get some warnings
  57. * if ignoreWarning is true, we would just assert the patch process
  58. * case 1: minSdkVersion is below 14, but you are using dexMode with raw.
  59. * it must be crash when load.
  60. * case 2: newly added Android Component in AndroidManifest.xml,
  61. * it must be crash when load.
  62. * case 3: loader classes in dex.loader{} are not keep in the main dex,
  63. * it must be let tinker not work.
  64. * case 4: loader classes in dex.loader{} changes,
  65. * loader classes is ues to load patch dex. it is useless to change them.
  66. * it won't crash, but these changes can't effect. you may ignore it
  67. * case 5: resources.arsc has changed, but we don't use applyResourceMapping to build
  68. */
  69. ignoreWarning = false

  70. /**
  71. * optional,default 'true'
  72. * whether sign the patch file
  73. * if not, you must do yourself. otherwise it can't check success during the patch loading
  74. * we will use the sign config with your build type
  75. */
  76. useSign = true

  77. /**
  78. * optional,default 'true'
  79. * whether use tinker to build
  80. */
  81. tinkerEnable = buildWithTinker()

  82. /**
  83. * Warning, applyMapping will affect the normal android build!
  84. */
  85. buildConfig {
  86. /**
  87. * optional,default 'null'
  88. * if we use tinkerPatch to build the patch apk, you'd better to apply the old
  89. * apk mapping file if minifyEnabled is enable!
  90. * Warning:
  91. * you must be careful that it will affect the normal assemble build!
  92. */
  93. applyMapping = getApplyMappingPath()
  94. /**
  95. * optional,default 'null'
  96. * It is nice to keep the resource id from R.txt file to reduce java changes
  97. */
  98. applyResourceMapping = getApplyResourceMappingPath()

  99. /**
  100. * necessary,default 'null'
  101. * because we don't want to check the base apk with md5 in the runtime(it is slow)
  102. * tinkerId is use to identify the unique base apk when the patch is tried to apply.
  103. * we can use git rev, svn rev or simply versionCode.
  104. * we will gen the tinkerId in your manifest automatic
  105. */
  106. tinkerId = getTinkerIdValue()

  107. /**
  108. * if keepDexApply is true, class in which dex refer to the old apk.
  109. * open this can reduce the dex diff file size.
  110. */
  111. keepDexApply = false

  112. /**
  113. * optional, default 'false'
  114. * Whether tinker should treat the base apk as the one being protected by app
  115. * protection tools.
  116. * If this attribute is true, the generated patch package will contain a
  117. * dex including all changed classes instead of any dexdiff patch-info files.
  118. */
  119. isProtectedApp = false
  120. }

  121. dex {
  122. /**
  123. * optional,default 'jar'
  124. * only can be 'raw' or 'jar'. for raw, we would keep its original format
  125. * for jar, we would repack dexes with zip format.
  126. * if you want to support below 14, you must use jar
  127. * or you want to save rom or check quicker, you can use raw mode also
  128. */
  129. dexMode = "jar"

  130. /**
  131. * necessary,default '[]'
  132. * what dexes in apk are expected to deal with tinkerPatch
  133. * it support * or ? pattern.
  134. */
  135. pattern = ["classes*.dex",
  136. "assets/secondary-dex-?.jar"]
  137. /**
  138. * necessary,default '[]'
  139. * Warning, it is very very important, loader classes can't change with patch.
  140. * thus, they will be removed from patch dexes.
  141. * you must put the following class into main dex.
  142. * Simply, you should add your own application {@code tinker.sample.android.SampleApplication}
  143. * own tinkerLoader, and the classes you use in them
  144. *
  145. */
  146. loader = [
  147. //use sample, let BaseBuildInfo unchangeable with tinker
  148. "com.tencent.tinker.loader.*",
  149. "com.tencent.tinker.*",
  150. "com.example.myapp.MyApplication"
  151. ]
  152. }

  153. lib {
  154. /**
  155. * optional,default '[]'
  156. * what library in apk are expected to deal with tinkerPatch
  157. * it support * or ? pattern.
  158. * for library in assets, we would just recover them in the patch directory
  159. * you can get them in TinkerLoadResult with Tinker
  160. */
  161. pattern = ["lib/*/*.so"]
  162. }

  163. res {
  164. /**
  165. * optional,default '[]'
  166. * what resource in apk are expected to deal with tinkerPatch
  167. * it support * or ? pattern.
  168. * you must include all your resources in apk here,
  169. * otherwise, they won't repack in the new apk resources.
  170. */
  171. pattern = ["res/*", "assets/*", "resources.arsc", "AndroidManifest.xml"]

  172. /**
  173. * optional,default '[]'
  174. * the resource file exclude patterns, ignore add, delete or modify resource change
  175. * it support * or ? pattern.
  176. * Warning, we can only use for files no relative with resources.arsc
  177. */
  178. ignoreChange = ["assets/sample_meta.txt"]

  179. /**
  180. * default 100kb
  181. * for modify resource, if it is larger than 'largeModSize'
  182. * we would like to use bsdiff algorithm to reduce patch file size
  183. */
  184. largeModSize = 100
  185. }

  186. packageConfig {
  187. /**
  188. * optional,default 'TINKER_ID, TINKER_ID_VALUE' 'NEW_TINKER_ID, NEW_TINKER_ID_VALUE'
  189. * package meta file gen. path is assets/package_meta.txt in patch file
  190. * you can use securityCheck.getPackageProperties() in your ownPackageCheck method
  191. * or TinkerLoadResult.getPackageConfigByName
  192. * we will get the TINKER_ID from the old apk manifest for you automatic,
  193. * other config files (such as patchMessage below)is not necessary
  194. */
  195. configField("TINKER_ID", getSha())
  196. configField("app_name", "MyApp")
  197. configField("patchMessage", "这是一个测试");
  198. /**
  199. * just a sample case, you can use such as sdkVersion, brand, channel...
  200. * you can parse it in the SamplePatchListener.
  201. * Then you can use patch conditional!
  202. */
  203. configField("platform", "all")
  204. /**
  205. * patch version via packageConfig
  206. */
  207. configField("patchVersion", "1.0")
  208. }
  209. //or you can add config filed outside, or get meta value from old apk
  210. //project.tinkerPatch.packageConfig.configField("test1", project.tinkerPatch.packageConfig.getMetaDataFromOldApk("Test"))
  211. //project.tinkerPatch.packageConfig.configField("test2", "sample")

  212. /**
  213. * if you don't use zipArtifact or path, we just use 7za to try
  214. */
  215. sevenZip {
  216. /**
  217. * optional,default '7za'
  218. * the 7zip artifact path, it will use the right 7za with your platform
  219. */
  220. zipArtifact = "com.tencent.mm:SevenZip:1.1.10"
  221. /**
  222. * optional,default '7za'
  223. * you can specify the 7za path yourself, it will overwrite the zipArtifact value
  224. */
  225. // path = "/usr/local/bin/7za"
  226. }
  227. }

  228. List<String> flavors = new ArrayList<>();
  229. project.android.productFlavors.each {flavor ->
  230. flavors.add(flavor.name)
  231. }
  232. boolean hasFlavors = flavors.size() > 0
  233. def date = new Date().format("MMdd-HH-mm-ss")

  234. /**
  235. * bak apk and mapping
  236. */
  237. android.applicationVariants.all { variant ->
  238. /**
  239. * task type, you want to bak
  240. */
  241. def taskName = variant.name

  242. tasks.all {
  243. if ("assemble${taskName.capitalize()}".equalsIgnoreCase(it.name)) {

  244. it.doLast {
  245. copy {
  246. def fileNamePrefix = "${project.name}-${variant.baseName}"
  247. def newFileNamePrefix = hasFlavors ? "${fileNamePrefix}" : "${fileNamePrefix}-${date}"

  248. def destPath = hasFlavors ? file("${bakPath}/${project.name}-${date}/${variant.flavorName}") : bakPath
  249. from variant.outputs.outputFile
  250. into destPath
  251. rename { String fileName ->
  252. fileName.replace("${fileNamePrefix}.apk", "${newFileNamePrefix}.apk")
  253. }

  254. from "${buildDir}/outputs/mapping/${variant.dirName}/mapping.txt"
  255. into destPath
  256. rename { String fileName ->
  257. fileName.replace("mapping.txt", "${newFileNamePrefix}-mapping.txt")
  258. }

  259. from "${buildDir}/intermediates/symbols/${variant.dirName}/R.txt"
  260. into destPath
  261. rename { String fileName ->
  262. fileName.replace("R.txt", "${newFileNamePrefix}-R.txt")
  263. }
  264. }
  265. }
  266. }
  267. }
  268. }
  269. project.afterEvaluate {
  270. //sample use for build all flavor for one time
  271. if (hasFlavors) {
  272. task(tinkerPatchAllFlavorRelease) {
  273. group = 'tinker'
  274. def originOldPath = getTinkerBuildFlavorDirectory()
  275. for (String flavor : flavors) {
  276. def tinkerTask = tasks.getByName("tinkerPatch${flavor.capitalize()}Release")
  277. dependsOn tinkerTask
  278. def preAssembleTask = tasks.getByName("process${flavor.capitalize()}ReleaseManifest")
  279. preAssembleTask.doFirst {
  280. String flavorName = preAssembleTask.name.substring(7, 8).toLowerCase() + preAssembleTask.name.substring(8, preAssembleTask.name.length() - 15)
  281. project.tinkerPatch.oldApk = "${originOldPath}/${flavorName}/${project.name}-${flavorName}-release.apk"
  282. project.tinkerPatch.buildConfig.applyMapping = "${originOldPath}/${flavorName}/${project.name}-${flavorName}-release-mapping.txt"
  283. project.tinkerPatch.buildConfig.applyResourceMapping = "${originOldPath}/${flavorName}/${project.name}-${flavorName}-release-R.txt"
  284. }
  285. }
  286. }

  287. task(tinkerPatchAllFlavorDebug) {
  288. group = 'tinker'
  289. def originOldPath = getTinkerBuildFlavorDirectory()
  290. for (String flavor : flavors) {
  291. def tinkerTask = tasks.getByName("tinkerPatch${flavor.capitalize()}Debug")
  292. dependsOn tinkerTask
  293. def preAssembleTask = tasks.getByName("process${flavor.capitalize()}DebugManifest")
  294. preAssembleTask.doFirst {
  295. String flavorName = preAssembleTask.name.substring(7, 8).toLowerCase() + preAssembleTask.name.substring(8, preAssembleTask.name.length() - 13)
  296. project.tinkerPatch.oldApk = "${originOldPath}/${flavorName}/${project.name}-${flavorName}-debug.apk"
  297. project.tinkerPatch.buildConfig.applyMapping = "${originOldPath}/${flavorName}/${project.name}-${flavorName}-debug-mapping.txt"
  298. project.tinkerPatch.buildConfig.applyResourceMapping = "${originOldPath}/${flavorName}/${project.name}-${flavorName}-debug-R.txt"
  299. }
  300. }
  301. }
  302. }
  303. }
  304. }

注意,minifyEnabled一定要设置为true,别忘了设置tinkerId,在getSha方法里可以先写死。

代码里我们要做点什么呢?我需要先自定义Application类,因为引入了Tinker,所以原来的MyApplication必须改造。

程序启动时会加载默认的Application类,这导致我们补丁包是无法对它做修改了。如何规避?在这里我们并没有使用类似InstantRun hook Application的方式,而是通过代码框架的方式来避免,这也是为了尽量少的去反射,提升框架的兼容性。这里我们要实现的是完全将原来的Application类隔离起来,即其他任何类都不能再引用我们自己的Application。我们需要做的其实是以下几个工作:

  1. 将我们自己Application类以及它的继承类的所有代码拷贝到自己的ApplicationLike继承类中,例如MyApplicationLike。你也可以直接将自己的Application改为继承ApplicationLike;
  2. Application的attachBaseContext方法实现要单独移动到onBaseContextAttached中;
  3. 对ApplicationLike中,引用application的地方改成getApplication();
  4. 对其他引用Application或者它的静态对象与方法的地方,改成引用ApplicationLike的静态对象与方法;

我的demo中原来是自定义的MyApplication,现在必须把之前的Application中定义的变量转移到自定义的ApplicationLike中去,然后自动生成MyApplication,这里使用Annotation生成Application类(推荐)。

MyApplicationLike.java

  1. package com.example.myapp;

  2. import android.app.Application;
  3. import android.content.Context;
  4. import android.content.Intent;

  5. import com.example.myapp.db.dao.DaoMaster;
  6. import com.example.myapp.db.dao.DaoSession;
  7. import com.example.myapp.event.MyEventBusIndex;
  8. import com.jan.lib.BusPoster;
  9. import com.tencent.tinker.anno.DefaultLifeCycle;
  10. import com.tencent.tinker.lib.tinker.TinkerInstaller;
  11. import com.tencent.tinker.loader.app.DefaultApplicationLike;
  12. import com.tencent.tinker.loader.shareutil.ShareConstants;

  13. import org.greenrobot.greendao.database.Database;

  14. /**
  15. * Created by Jan on 2017/5/25.
  16. */
  17. @DefaultLifeCycle(
  18. application = ".MyApplication",
  19. flags = ShareConstants.TINKER_ENABLE_ALL, ////tinkerFlags, tinker支持的类型,dex,library,还是全部都支持!
  20. loaderClass = "com.tencent.tinker.loader.TinkerLoader",//loaderClassName, 我们这里使用默认即可!
  21. loadVerifyFlag = false) //tinkerLoadVerifyFlag
  22. public class MyApplicationLike extends DefaultApplicationLike {

  23. public static final boolean ENCRYPTED = false;
  24. private DaoSession mDaoSession;
  25. public static Context mContext;

  26. public MyApplicationLike(Application application, int tinkerFlags, boolean tinkerLoadVerifyFlag, long applicationStartElapsedTime, long applicationStartMillisTime, Intent tinkerResultIntent) {
  27. super(application, tinkerFlags, tinkerLoadVerifyFlag, applicationStartElapsedTime, applicationStartMillisTime, tinkerResultIntent);
  28. }

  29. @Override
  30. public void onBaseContextAttached(Context base) {
  31. super.onBaseContextAttached(base);
  32. }

  33. @Override
  34. public void onCreate() {
  35. super.onCreate();
  36. TinkerInstaller.install(this);
  37. MyApplication application = (MyApplication) getApplication();
  38. BusPoster.registerSubIndex(new MyEventBusIndex());
  39. mContext =application.getApplicationContext();
  40. registerDaoComp();
  41. }

  42. private void registerDaoComp(){
  43. DaoMaster.DevOpenHelper helper = new DaoMaster.DevOpenHelper(mContext,ENCRYPTED ? "app-db-encrypted" : "app-db");
  44. Database db = ENCRYPTED ? helper.getEncryptedWritableDb("super-secret") : helper.getWritableDb();
  45. mDaoSession = new DaoMaster(db).newSession();
  46. }

  47. public DaoSession getDaoSession(){
  48. return mDaoSession;
  49. }

  50. }

AndroidMnaifest,xml里的android:name=".MyApplication" 这个是自动生成的哦~

为了方便测试效果,我们在demo的测试Activity中写入这样的逻辑:加入一个按钮A,用于执行加载修复补丁包,以及展示一段文字,为了和加入补丁后的代码进行比较,用来判断是否有效。

因为这里加载补丁包势必要有读取文件的权限:<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>

  1. Tinker tinker = Tinker.with(getApplicationContext());
  2. //判断是否加载了补丁
  3. if(tinker.isTinkerLoaded()){
  4. Toast.makeText(this,"patch is loaded",Toast.LENGTH_SHORT).show();
  5. }else {
  6. Toast.makeText(this,"patch is not loaded",Toast.LENGTH_SHORT).show();
  7. }
  8. //用来加载补丁包的按钮
  9. btn2 = (Button) findViewById(R.id.button2);
  10. btn2.setOnClickListener(new View.OnClickListener() {
  11. @Override
  12. public void onClick(View v) {
  13. //adb push ./app/build/outputs/tinkerPatch/debug/patch_signed_7zip.apk /storage/sdcard0/
  14. TinkerInstaller.onReceiveUpgradePatch(getApplicationContext(), Environment.getExternalStorageDirectory().getAbsolutePath() + "/patch_signed_7zip.apk");

  15. }
  16. });
  17. //关闭APP的按钮
  18. btn3 = (Button) findViewById(R.id.button3);
  19. btn3.setOnClickListener(new View.OnClickListener() {
  20. @Override
  21. public void onClick(View v) {
  22. ShareTinkerInternals.killAllOtherProcess(getApplicationContext());
  23. android.os.Process.killProcess(android.os.Process.myPid());
  24. }
  25. });

好了,代码基本很简单。下面讲讲如何打包。

4.我们这里模拟打正式发布的包,先执行gradle上述的方法中的assembleRelease脚本


我们这里生成了基准包,在build/bakApk/下的。。。apk文件和mapping文件,R字典文件配置到如图的区域中。这一步骤可不能忘了。这个基准包apk我们是经过混淆过的,我们把这个app-release-xxx.apk,先安装到手机上。


接着修改 Activity中的文字展示的代码,然后开始生成补丁包,执行tinkerPatchRelease


这会儿在app\build\outputs\tinkerPatch\release目录下找到补丁包patch_signed_7zip.apk,然后push到手机sd卡下,准备加载动作。

执行命令adb push ./app/build/outputs/tinkerPatch/release/patch_signed_7zip.apk /storage/sdcard0/ 即可。

再打开我们刚开始装的app,点击执行加载补丁功能,如果成功,将会自动关闭下次启动后,发现展示的文字是最新修改过的。如果你失败了,那得看看日志,找找哪里出了问题。

    本站是提供个人知识管理的网络存储空间,所有内容均由用户发布,不代表本站观点。请注意甄别内容中的联系方式、诱导购买等信息,谨防诈骗。如发现有害或侵权内容,请点击一键举报。
    转藏 分享 献花(0

    0条评论

    发表

    请遵守用户 评论公约

    类似文章 更多