Bugly1.3.6版本熱更新基本配置

Bugly主頁:https://bugly.qq.com/v2/index

熱更新文檔:https://bugly.qq.com/docs/user-guide/instruction-manual-android-hotfix/?v=20180709165613

在app module的“build.gradle”文件中添加

// 依賴插件腳本
apply from: 'tinker-support.gradle'

compile "com.android.support:multidex:1.0.1" // 多dex配置

// 集成Bugly熱更新aar(本地集成使用方式)
// compile(name: 'bugly_crashreport_upgrade-1.3.2', ext: 'aar')
// 遠程倉庫集成方式(推薦)
compile 'com.tencent.bugly:crashreport_upgrade:1.3.6'
// 指定tinker依賴版本(注:應用升級1.3.5版本起,不再內置tinker)
compile 'com.tencent.tinker:tinker-android-lib:1.9.9'
//使用NDK庫,需要配置
compile 'com.tencent.bugly:nativecrashreport:latest.release'

工程根目錄下“build.gradle”文件中添加

// tinkersupport插件(1.0.3以上無須再配置tinker插件)
classpath "com.tencent.bugly:tinker-support:1.1.5"

tinker-support.gradle文件

 apply plugin: 'com.tencent.bugly.tinker-support'

def bakPath = file("${buildDir}/bakApk/")

/**
* 此處填寫每次構建生成的基準包目錄
*/
def baseApkDir = "app-1108-11-35-14"
/**
* 對於插件各參數的詳細解析請參考
*/
tinkerSupport {
// 開啓tinker-support插件,默認值true
enable = true
// 指定歸檔目錄,默認值當前module的子目錄tinker
autoBackupApkDir = "${bakPath}"
autoGenerateTinkerId = true
// 是否啓用覆蓋tinkerPatch配置功能,默認值false
// 開啓後tinkerPatch配置不生效,即無需添加tinkerPatch
overrideTinkerPatchConfiguration = true

// 編譯補丁包時,必需指定基線版本的apk,默認值爲空
// 如果爲空,則表示不是進行補丁包的編譯
// @{link tinkerPatch.oldApk }
//baseApk = "${bakPath}/${baseApkDir}/app-release.apk"
baseApk = "${bakPath}/${baseApkDir}/app-debug.apk"
//baseApk = "${bakPath}/app-1217-14-17-24/app-1.0.0-2018-12-17.apk"

// 對應tinker插件applyMapping
//baseApkProguardMapping = "${bakPath}/${baseApkDir}/app-release-mapping.txt"
baseApkProguardMapping = "${bakPath}/${baseApkDir}/app-debug-mapping.txt"
//baseApkProguardMapping = "${bakPath}/app-1217-14-17-24/app-debug-mapping.txt"

// 對應tinker插件applyResourceMapping
//baseApkResourceMapping = "${bakPath}/${baseApkDir}/app-release-R.txt"
baseApkResourceMapping = "${bakPath}/${baseApkDir}/app-debug-R.txt"
//baseApkResourceMapping = "${bakPath}/app-1217-14-17-24/app-debug-R.txt"

tinkerId = "base-1.0.0"
//tinkerId = "patch-1.0.1"

// buildAllFlavorsDir = "${bakPath}/${baseApkDir}"

// 是否開啓加固模式,默認爲false
// isProtectedApp = true

enableProxyApplication = false
supportHotplugComponent = true
}
/**
* 一般來說,我們無需對下面的參數做任何的修改
* 對於各參數的詳細介紹請參考:
* [https://github.com/Tencent/tinker/wiki/Tinker-%E6%8E%A5%E5%85%A5%E6%8C%87%E5%8D%97](https://github.com/Tencent/tinker/wiki/Tinker-%E6%8E%A5%E5%85%A5%E6%8C%87%E5%8D%97)
*/

tinkerPatch {
//oldApk ="${bakPath}/${appName}/app-release.apk"
ignoreWarning = false
useSign = true
dex {
dexMode = "jar"
pattern = ["classes*.dex"]
loader = []
}
lib {
pattern = ["lib/*/*.so"]
}
res {
pattern = ["res/*", "r/*", "assets/*", "resources.arsc", "AndroidManifest.xml"]
ignoreChange = []
largeModSize = 100
}
packageConfig {
}
sevenZip {
zipArtifact = "com.tencent.mm:SevenZip:1.1.10"
// path = "/usr/local/bin/7za"
}
buildConfig {
keepDexApply = false
//tinkerId = "1.0.1-patch"
//applyMapping = "${bakPath}/${appName}/app-release-mapping.txt" // 可選,設置mapping文件,建議保持舊apk的proguard混淆方式
//applyResourceMapping = "${bakPath}/${appName}/app-release-R.txt" // 可選,設置R.txt文件,通過舊apk文件保持ResId的分配
}
}

編譯基準包

修改tinker-support.gradle文件中以下參數

//baseApk = "${bakPath}/${baseApkDir}/app-release.apk"
baseApk = "${bakPath}/${baseApkDir}/app-debug.apk"
//baseApk = "${bakPath}/app-1217-14-17-24/app-1.0.0-2018-12-17.apk"

// 對應tinker插件applyMapping
//baseApkProguardMapping = "${bakPath}/${baseApkDir}/app-release-mapping.txt"
baseApkProguardMapping = "${bakPath}/${baseApkDir}/app-debug-mapping.txt"
//baseApkProguardMapping = "${bakPath}/app-1217-14-17-24/app-debug-mapping.txt"

// 對應tinker插件applyResourceMapping
//baseApkResourceMapping = "${bakPath}/${baseApkDir}/app-release-R.txt"
baseApkResourceMapping = "${bakPath}/${baseApkDir}/app-debug-R.txt"
//baseApkResourceMapping = "${bakPath}/app-1217-14-17-24/app-debug-R.txt"

tinkerId = "base-1.0.0"
//tinkerId = "patch-1.0.1"

雙擊assembleRelease編譯生成基準包
(assembleRelease在右側gradle下的Tasks/bulid/assembleRelease)

這個會在build/outputs/bakApk路徑下生成每次編譯的基準包、混淆配置文件、資源Id文件


根據基線版本生成補丁包(重點)

修改tinker-support.gradle文件中以下參數
注意(baseApk,baseApkProguardMapping,baseApkResourceMapping要修改爲基準包存放的路徑,且tinkerId一定要修改)

//baseApk = "${bakPath}/${baseApkDir}/app-release.apk"
baseApk = "${bakPath}/${baseApkDir}/app-debug.apk"
//baseApk = "${bakPath}/app-1217-14-17-24/app-1.0.0-2018-12-17.apk"

// 對應tinker插件applyMapping
//baseApkProguardMapping = "${bakPath}/${baseApkDir}/app-release-mapping.txt"
baseApkProguardMapping = "${bakPath}/${baseApkDir}/app-debug-mapping.txt"
//baseApkProguardMapping = "${bakPath}/app-1217-14-17-24/app-debug-mapping.txt"

// 對應tinker插件applyResourceMapping
//baseApkResourceMapping = "${bakPath}/${baseApkDir}/app-release-R.txt"
baseApkResourceMapping = "${bakPath}/${baseApkDir}/app-debug-R.txt"
//baseApkResourceMapping = "${bakPath}/app-1217-14-17-24/app-debug-R.txt"

tinkerId = "base-1.0.0"
//tinkerId = "patch-1.0.1"

雙擊 buildTinkerPatchRelease編譯生成補丁包
( buildTinkerPatchRelease在右側gradle下的Tasks/tinker-support/buildTinkerPatchRelease)

生成的補丁包在build/outputs/patch目錄下


注意:下發補丁以後,APP必須殺死重新啓動纔會自動下載補丁包

發表評論
所有評論
還沒有人評論,想成為第一個評論的人麼? 請在上方評論欄輸入並且點擊發布.
相關文章