熱修復框架Tinker最完整講解（01）——整合之路
阿新 • • 發佈：2019-02-04
前言
上個月我們的產品又更新了一個版本，當一個測試把產品上傳了十幾個應用市場的時候，另外一個測試突然測出一個重要bug。專案經理就說把全部渠道上傳的先退回來，重新改好bug再發布。這時候我們就苦逼了，又要走一遍 簽名打包->加固->簽名->上傳應用市場的流程。要知道我們的渠道有接近20個，整個流程又要花上2，3小時。只能全部加班加點了。。。
為了解決有一個bug又要重新發布版本的問題，專案經理就叫我趕緊把熱修復整合到專案中去。一開始覺得3天就能搞定，就跟專案經理要了4天時間（呵呵，老司機都懂。。。）。結果是整整搞了5天！整合tinker Demo確實一天可以搞定，但是還要自定義Application類（我們專案的Application還比較複雜），整合美團Walle多渠道打包（我們以前多渠道打包是採用productFlavors實現的），與後臺溝通介面的設計（補丁包的存放），svn的分支管理，測試整個流程等等就花了很多時間了。這其中遇到了很多坑和問題。這個系列文章都會一一講解，新手看了肯定會少走很多彎路。
Tinker是什麼
Tinker是微信官方的Android熱補丁解決方案，它支援動態下發程式碼、So庫以及資源，讓應用能夠在不需要重新安裝的情況下實現更新。當然，你也可以使用Tinker來更新你的外掛。
為什麼使用Tinker
當前市面的熱補丁方案有很多，其中比較出名的有阿里的AndFix、美團的Robust以及QZone的超級補丁方案。但它們都存在無法解決的問題，這也是正是我們推出Tinker的原因。
總的來說:
1、AndFix作為native解決方案，首先面臨的是穩定性與相容性問題，更重要的是它無法實現類替換，它是需要大量額外的開發成本的；
2、Robust相容性與成功率較高，但是它與AndFix一樣，無法新增變數與類只能用做的bugFix方案；
3、Qzone方案可以做到釋出產品功能，但是它主要問題是插樁帶來Dalvik的效能問題，以及為了解決Art下記憶體地址問題而導致補丁包急速增大的。
特別是在Android N之後，由於混合編譯的inline策略修改，對於市面上的各種方案都不太容易解決。而Tinker熱補丁方案不僅支援類、So以及資源的替換，它還是2.X－7.X的全平臺支援。利用Tinker我們不僅可以用做bugfix,甚至可以替代功能的釋出。Tinker已執行在微信的數億Android裝置上，那麼為什麼你不使用Tinker呢？
Tinker的已知問題
由於原理與系統限制，Tinker有以下已知問題：
1、Tinker不支援修改AndroidManifest.xml，Tinker不支援新增四大元件；
2、由於Google Play的開發者條款限制，不建議在GP渠道動態更新程式碼；
3、在Android N上，補丁對應用啟動時間有輕微的影響；
4、不支援部分三星android-21機型，載入補丁時會主動丟擲”TinkerRuntimeException:checkDexInstall failed”；
5、對於資源替換，不支援修改remoteView。例如transition動畫，notification icon以及桌面圖示。
Tinker整合
一、配置gradle
1，在專案的gradle.properties檔案中新增Tinker的版本號
#Tinker版本號
TINKER_VERSION=1.7.112，在專案的build.gradle中，新增tinker-patch-gradle-plugin的依賴
buildscript {
repositories {
jcenter()
}
dependencies {
classpath 'com.android.tools.build:gradle:2.2.2'
//tinker
classpath "com.tencent.tinker:tinker-patch-gradle-plugin:${TINKER_VERSION}"
}
}3，在app的gradle檔案app/build.gradle，新增tinker的庫依賴(有註釋的3個)
dependencies {
compile fileTree(include: ['*.jar'], dir: 'libs')
testCompile 'junit:junit:4.12'
compile 'com.android.support:appcompat-v7:23.1.1'
// 多dex 打包的類庫
compile 'com.android.support:multidex:1.0.1'
//tinker的核心庫
compile("com.tencent.tinker:tinker-android-lib:${TINKER_VERSION}") { changing = true }
//用於生成application類
provided("com.tencent.tinker:tinker-android-anno:${TINKER_VERSION}") { changing = true }
}4，在app的gradle檔案app/build.gradle，新增tinker的相關配置
下面就把整個app/build.gradle配置貼出來，其中標有Tinker相關配置即為tinker的相關配置，其中比較重要的屬性都標有中文註釋，其餘屬性解釋可以自行參考 Tinker 接入指南
apply plugin: 'com.android.application'
android {
compileSdkVersion 23
buildToolsVersion "23.0.2"
//recommend Tinker相關配置
dexOptions {
jumboMode = true
}
//簽名信息配置
signingConfigs {
release {
storeFile file("./keystore/wildmatinker.jks")
keyAlias "wildmatinker"
storePassword "123456"
keyPassword "123456"
}
debug {
storeFile file("./keystore/debug.keystore")
}
}
defaultConfig {
applicationId "com.wildma.wildmatinker"
minSdkVersion 14
targetSdkVersion 22
versionCode 1
versionName "1.0.0"
//Tinker相關配置start======================================
testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
/**
* you can use multiDex and install it in your ApplicationLifeCycle implement
*/
multiDexEnabled true
/**
* buildConfig can change during patch!
* we can use the newly value when patch
*/
buildConfigField "String", "MESSAGE", "\"I am the base apk\""
// buildConfigField "String", "MESSAGE", "\"I am the patch apk\""
/**
* client version would update with patch
* so we can get the newly git version easily!
*/
buildConfigField "String", "TINKER_ID", "\"${getTinkerIdValue()}\""
buildConfigField "String", "PLATFORM", "\"all\""
//Tinker相關配置end======================================
}
buildTypes {
release {
minifyEnabled true
signingConfig signingConfigs.release
proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
}
debug {
debuggable true
minifyEnabled false
signingConfig signingConfigs.debug
}
}
sourceSets {
main {
jniLibs.srcDirs = ['libs']
}
}
}
dependencies {
compile fileTree(include: ['*.jar'], dir: 'libs')
testCompile 'junit:junit:4.12'
compile 'com.android.support:appcompat-v7:23.1.1'
// 多dex 打包的類庫
compile 'com.android.support:multidex:1.0.1'
//tinker的核心庫
compile("com.tencent.tinker:tinker-android-lib:${TINKER_VERSION}") { changing = true }
//用於生成application類
provided("com.tencent.tinker:tinker-android-anno:${TINKER_VERSION}") { changing = true }
}
//Tinker相關配置start======================================
def gitSha() {
try {
// String gitRev = 'git rev-parse --short HEAD'.execute(null, project.rootDir).text.trim()
String gitRev = '1.0.0' //tinkerID,每次釋出新版本都需要修改!
if (gitRev == null) {
throw new GradleException("can't get git rev, you should add git to system path or just input test value, such as 'testTinkerId'")
}
return gitRev
} catch (Exception e) {
throw new GradleException("can't get git rev, you should add git to system path or just input test value, such as 'testTinkerId'")
}
}
def javaVersion = JavaVersion.VERSION_1_7
def bakPath = file("${buildDir}/bakApk/")
/**
* you can use assembleRelease to build you base apk
* use tinkerPatchRelease -POLD_APK= -PAPPLY_MAPPING= -PAPPLY_RESOURCE= to build patch
* add apk from the build/bakApk
*/
ext {
//是否開啟tinker的功能
tinkerEnabled = true
//old apk地址
tinkerOldApkPath = "${bakPath}/app-release-0708-21-59-49.apk"
//old apk 混淆檔案地址
tinkerApplyMappingPath = "${bakPath}/app-release-0708-21-59-49-mapping.txt"
//old apk R 檔案地址
tinkerApplyResourcePath = "${bakPath}/app-release-0708-21-59-49-R.txt"
//only use for build all flavor, if not, just ignore this field
tinkerBuildFlavorDirectory = "${bakPath}/app-1018-17-32-47"
}
def getOldApkPath() {
return hasProperty("OLD_APK") ? OLD_APK : ext.tinkerOldApkPath
}
def getApplyMappingPath() {
return hasProperty("APPLY_MAPPING") ? APPLY_MAPPING : ext.tinkerApplyMappingPath
}
def getApplyResourceMappingPath() {
return hasProperty("APPLY_RESOURCE") ? APPLY_RESOURCE : ext.tinkerApplyResourcePath
}
def getTinkerIdValue() {
return hasProperty("TINKER_ID") ? TINKER_ID : gitSha()
}
def buildWithTinker() {
return hasProperty("TINKER_ENABLE") ? TINKER_ENABLE : ext.tinkerEnabled
}
def getTinkerBuildFlavorDirectory() {
return ext.tinkerBuildFlavorDirectory
}
if (buildWithTinker()) {
apply plugin: 'com.tencent.tinker.patch'
tinkerPatch {
/**
* necessary，default 'null'
* the old apk path, use to diff with the new apk to build
* add apk from the build/bakApk
*/
oldApk = getOldApkPath()
/**
* optional，default 'false'
* there are some cases we may get some warnings
* if ignoreWarning is true, we would just assert the patch process
* case 1: minSdkVersion is below 14, but you are using dexMode with raw.
* it must be crash when load.
* case 2: newly added Android Component in AndroidManifest.xml,
* it must be crash when load.
* case 3: loader classes in dex.loader{} are not keep in the main dex,
* it must be let tinker not work.
* case 4: loader classes in dex.loader{} changes,
* loader classes is ues to load patch dex. it is useless to change them.
* it won't crash, but these changes can't effect. you may ignore it
* case 5: resources.arsc has changed, but we don't use applyResourceMapping to build
*/
ignoreWarning = false
/**
* optional，default 'true'
* whether sign the patch file
* if not, you must do yourself. otherwise it can't check success during the patch loading
* we will use the sign config with your build type
*/
useSign = true
/**
* optional，default 'true'
* whether use tinker to build
*/
tinkerEnable = buildWithTinker()
/**
* Warning, applyMapping will affect the normal android build!
*/
buildConfig {
/**
* optional，default 'null'
* if we use tinkerPatch to build the patch apk, you'd better to apply the old
* apk mapping file if minifyEnabled is enable!
* Warning:
* you must be careful that it will affect the normal assemble build!
*/
applyMapping = getApplyMappingPath()
/**
* optional，default 'null'
* It is nice to keep the resource id from R.txt file to reduce java changes
*/
applyResourceMapping = getApplyResourceMappingPath()
/**
* necessary，default 'null'
* because we don't want to check the base apk with md5 in the runtime(it is slow)
* tinkerId is use to identify the unique base apk when the patch is tried to apply.
* we can use git rev, svn rev or simply versionCode.
* we will gen the tinkerId in your manifest automatic
*/
tinkerId = getTinkerIdValue()
/**
* if keepDexApply is true, class in which dex refer to the old apk.
* open this can reduce the dex diff file size.
*/
keepDexApply = false
//是否開啟加固
isProtectedApp = false
}
dex {
/**
* optional，default 'jar'
* only can be 'raw' or 'jar'. for raw, we would keep its original format
* for jar, we would repack dexes with zip format.
* if you want to support below 14, you must use jar
* or you want to save rom or check quicker, you can use raw mode also
*/
dexMode = "jar"
/**
* necessary，default '[]'
* what dexes in apk are expected to deal with tinkerPatch
* it support * or ? pattern.
*/
pattern = ["classes*.dex",
"assets/secondary-dex-?.jar"]
/**
* necessary，default '[]'
* Warning, it is very very important, loader classes can't change with patch.
* thus, they will be removed from patch dexes.
* you must put the following class into main dex.
* Simply, you should add your own application {@code tinker.sample.android.SampleApplication}
* own tinkerLoader, and the classes you use in them
*
*/
loader = [
//use sample, let BaseBuildInfo unchangeable with tinker
"tinker.sample.android.app.BaseBuildInfo"
]
}
lib {
/**
* optional，default '[]'
* what library in apk are expected to deal with tinkerPatch
* it support * or ? pattern.
* for library in assets, we would just recover them in the patch directory
* you can get them in TinkerLoadResult with Tinker
*/
pattern = ["lib/*/*.so"]
}
res {
/**
* optional，default '[]'
* what resource in apk are expected to deal with tinkerPatch
* it support * or ? pattern.
* you must include all your resources in apk here,
* otherwise, they won't repack in the new apk resources.
*/
pattern = ["res/*", "assets/*", "resources.arsc", "AndroidManifest.xml"]
/**
* optional，default '[]'
* the resource file exclude patterns, ignore add, delete or modify resource change
* it support * or ? pattern.
* Warning, we can only use for files no relative with resources.arsc
*/
ignoreChange = ["assets/sample_meta.txt"]
/**
* default 100kb
* for modify resource, if it is larger than 'largeModSize'
* we would like to use bsdiff algorithm to reduce patch file size
*/
largeModSize = 100
}
packageConfig {
/**
* optional，default 'TINKER_ID, TINKER_ID_VALUE' 'NEW_TINKER_ID, NEW_TINKER_ID_VALUE'
* package meta file gen. path is assets/package_meta.txt in patch file
* you can use securityCheck.getPackageProperties() in your ownPackageCheck method
* or TinkerLoadResult.getPackageConfigByName
* we will get the TINKER_ID from the old apk manifest for you automatic,
* other config files (such as patchMessage below)is not necessary
*/
configField("patchMessage", "tinker is sample to use")
/**
* just a sample case, you can use such as sdkVersion, brand, channel...
* you can parse it in the SamplePatchListener.
* Then you can use patch conditional!
*/
configField("platform", "all")
/**
* patch version via packageConfig
*/
configField("patchVersion", "1.0")
}
//or you can add config filed outside, or get meta value from old apk
//project.tinkerPatch.packageConfig.configField("test1", project.tinkerPatch.packageConfig.getMetaDataFromOldApk("Test"))
//project.tinkerPatch.packageConfig.configField("test2", "sample")
/**
* if you don't use zipArtifact or path, we just use 7za to try
*/
sevenZip {
/**
* optional，default '7za'
* the 7zip artifact path, it will use the right 7za with your platform
*/
zipArtifact = "com.tencent.mm:SevenZip:1.1.10"
/**
* optional，default '7za'
* you can specify the 7za path yourself, it will overwrite the zipArtifact value
*/
// path = "/usr/local/bin/7za"
}
}
List<String> flavors = new ArrayList<>();
project.android.productFlavors.each {flavor ->
flavors.add(flavor.name)
}
boolean hasFlavors = flavors.size() > 0
def date = new Date().format("MMdd-HH-mm-ss")
/**
* bak apk and mapping
*/
android.applicationVariants.all { variant ->
/**
* task type, you want to bak
*/
def taskName = variant.name
tasks.all {
if ("assemble${taskName.capitalize()}".equalsIgnoreCase(it.name)) {
it.doLast {
copy {
def fileNamePrefix = "${project.name}-${variant.baseName}"
def newFileNamePrefix = hasFlavors ? "${fileNamePrefix}" : "${fileNamePrefix}-${date}"
def destPath = hasFlavors ? file("${bakPath}/${project.name}-${date}/${variant.flavorName}") : bakPath
from variant.outputs.outputFile
into destPath
rename { String fileName ->
fileName.replace("${fileNamePrefix}.apk", "${newFileNamePrefix}.apk")
}
from "${buildDir}/outputs/mapping/${variant.dirName}/mapping.txt"
into destPath
rename { String fileName ->
fileName.replace("mapping.txt", "${newFileNamePrefix}-mapping.txt")
}
from "${buildDir}/intermediates/symbols/${variant.dirName}/R.txt"
into destPath
rename { String fileName ->
fileName.replace("R.txt", "${newFileNamePrefix}-R.txt")
}
}
}
}
}
}
project.afterEvaluate {
//sample use for build all flavor for one time
if (hasFlavors) {
task(tinkerPatchAllFlavorRelease) {
group = 'tinker'
def originOldPath = getTinkerBuildFlavorDirectory()
for (String flavor : flavors) {
def tinkerTask = tasks.getByName("tinkerPatch${flavor.capitalize()}Release")
dependsOn tinkerTask
def preAssembleTask = tasks.getByName("process${flavor.capitalize()}ReleaseManifest")
preAssembleTask.doFirst {
String flavorName = preAssembleTask.name.substring(7, 8).toLowerCase() + preAssembleTask.name.substring(8, preAssembleTask.name.length() - 15)
project.tinkerPatch.oldApk = "${originOldPath}/${flavorName}/${project.name}-${flavorName}-release.apk"
project.tinkerPatch.buildConfig.applyMapping = "${originOldPath}/${flavorName}/${project.name}-${flavorName}-release-mapping.txt"
project.tinkerPatch.buildConfig.applyResourceMapping = "${originOldPath}/${flavorName}/${project.name}-${flavorName}-release-R.txt"
}
}
}
task(tinkerPatchAllFlavorDebug) {
group = 'tinker'
def originOldPath = getTinkerBuildFlavorDirectory()
for (String flavor : flavors) {
def tinkerTask = tasks.getByName("tinkerPatch${flavor.capitalize()}Debug")
dependsOn tinkerTask
def preAssembleTask = tasks.getByName("process${flavor.capitalize()}DebugManifest")
preAssembleTask.doFirst {
String flavorName = preAssembleTask.name.substring(7, 8).toLowerCase() + preAssembleTask.name.substring(8, preAssembleTask.name.length() - 13)
project.tinkerPatch.oldApk = "${originOldPath}/${flavorName}/${project.name}-${flavorName}-debug.apk"
project.tinkerPatch.buildConfig.applyMapping = "${originOldPath}/${flavorName}/${project.name}-${flavorName}-debug-mapping.txt"
project.tinkerPatch.buildConfig.applyResourceMapping = "${originOldPath}/${flavorName}/${project.name}-${flavorName}-debug-R.txt"
}
}
}
}
}
}
//Tinker相關配置start======================================二、自定義Application類
程式啟動時會載入預設的Application類，這導致補丁包無法對它做修改。所以Tinker官方說不建議自己去實現Application，而是由Tinker自動生成。即需要建立一個SampleApplication類，繼承DefaultApplicationLike，然後將我們自己的MyApplication中所有邏輯放在SampleApplication中的onCreate中。最後需要將我們專案中之前的MyApplication類刪除。如下：
package com.wildma.wildmatinker;
import android.annotation.TargetApi;
import android.app.Application;
import android.content.Context;
import android.content.Intent;
import android.os.Build;
import android.support.multidex.MultiDex;
import com.tencent.tinker.anno.DefaultLifeCycle;
import com.tencent.tinker.lib.tinker.Tinker;
import com.tencent.tinker.lib.tinker.TinkerInstaller;
import com.tencent.tinker.loader.app.DefaultApplicationLike;
import com.tencent.tinker.loader.shareutil.ShareConstants;
import com.wildma.wildmatinker.tinker.MyLogImp;
import com.wildma.wildmatinker.tinker.TinkerManager;
@SuppressWarnings("unused")
@DefaultLifeCycle( application = "com.wildma.wildmatinker.MyApplication",// 自定義生成
flags = ShareConstants.TINKER_ENABLE_ALL,
loadVerifyFlag = false)
public class SampleApplication extends DefaultApplicationLike {
public static SampleApplication sampleApplication;
public SampleApplication(Application application, int tinkerFlags, boolean tinkerLoadVerifyFlag,
long applicationStartElapsedTime, long applicationStartMillisTime, Intent tinkerResultIntent) {
super(application, tinkerFlags, tinkerLoadVerifyFlag, applicationStartElapsedTime, applicationStartMillisTime, tinkerResultIntent);
}
@Override
public void onCreate() {
super.onCreate();
sampleApplication = this;
//將我們自己的MyApplication中的所有邏輯放在這裡，例如初始化一些第三方
}
@TargetApi(Build.VERSION_CODES.ICE_CREAM_SANDWICH)
@Override
public void onBaseContextAttached(Context base) {
super.onBaseContextAttached(base);
// 其原理是分包架構，所以在載入初要載入其餘的分包
MultiDex.install(base);
// Tinker管理類，儲存當前物件
TinkerManager.setTinkerApplicationLike(this);
// 崩潰保護
TinkerManager.initFastCrashProtect();
// 是否重試
TinkerManager.setUpgradeRetryEnable(true);
//Log 實現，列印載入補丁的資訊
TinkerInstaller.setLogIml(new MyLogImp());
// 執行Tinker ，通過Tinker新增一些基本配置
TinkerManager.installTinker(this);
Tinker tinker = Tinker.with(getApplication());
}
@TargetApi(Build.VERSION_CODES.ICE_CREAM_SANDWICH)
public void registerActivityLifecycleCallbacks(Application.ActivityLifecycleCallbacks callback) {
// 生命週期，預設配置
getApplication().registerActivityLifecycleCallbacks(callback);
}
/**
* 獲取SampleApplication例項
* @return
*/
public static SampleApplication getSampleApplication(){
return sampleApplication;
}
}
其中DefaultLifeCycle中的MyApplication為我們真正的Application，清單檔案中的Application的name改為MyApplication的全路徑。如下：
<application
android:name="com.wildma.wildmatinker.MyApplication"
android:allowBackup="true"
android:icon="@mipmap/ic_launcher"
android:label="@string/app_name"
android:supportsRtl="true"
android:theme="@style/AppTheme">
<activity android:name=".MainActivity">
<intent-filter>
<action android:name="android.intent.action.MAIN"/>
<category android:name="android.intent.category.LAUNCHER"/>
</intent-filter>
</activity>
</application>三、新增Tinker相關類
這些類主要是載入補丁包過程的回撥，列印log，崩潰保護等。具體見 Tinker 自定義擴充套件
四、在清單檔案新增讀寫sd卡的許可權
<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE"/>
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>五、載入補丁包程式碼
package com.wildma.wildmatinker;
public class MainActivity extends AppCompatActivity {
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_main);
//載入補丁包
TinkerInstaller.onReceiveUpgradePatch(getApplicationContext(), Environment.getExternalStorageDirectory().getAbsolutePath() + "/patch_signed_7zip");
}
//Tinker相關配置
protected void onResume() {
super.onResume();
Utils.setBackground(false);
}
//Tinker相關配置
@Override
protected void onPause() {
super.onPause();
Utils.setBackground(true);
}
}
其中第9行程式碼的路徑為我們放在sd卡中的補丁包路徑。
測試Tinker熱修復
這裡只講release版本。
一、按正常流程打包出帶簽名的APK，並裝到手機上
打包完成，會自動在專案的app/build資料夾下生成bakAPK資料夾並有三個檔案（基礎包的一些檔案），如圖：
二、將上面的三個檔案路徑複製到app.build中對應的位置，如圖
三、修復bug（測試的時候隨便改動一點程式碼）
四、執行補丁命令獲取補丁包
執行補丁命令，單擊AS右側頂部gradle–>雙擊tinkerPatchRelease，如圖:
執行完成會在build->outputs->tinkerPatch->release資料夾中生成一個名為patch_signed_7zip.apk的補丁包，如圖：
五、將該補丁包複製到之前載入補丁包中對應的SD卡路勁即可。
六、執行專案發現bug並沒有修復，因為tinker是不支援即時修復的，關掉APP重啟。恭喜你！bug已修復！
Tinker整合在這裡講的已經非常詳細了，有不足的地方希望指出。遇到不懂的問題都可以直接在這裡問我，只要我遇到過並且能回答出來的都會樂意回答。