tinker热修复gradle接入，1-3年的Android开发工程师看过来

//废弃，因为我们吧tinker_id写死了，这里的作用是把git的提交记录用作tinker_id的版本

def gitSha() {

try {

String gitRev = ‘git rev-parse --short HEAD’.execute(null, project.rootDir).text.trim()

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’”)

}

}

//配置java版本

def javaVersion = JavaVersion.VERSION_1_7

android {

compileSdkVersion 23

buildToolsVersion “23.0.2”

compileOptions {

sourceCompatibility javaVersion

targetCompatibility javaVersion

}

//recommend

dexOptions {

jumboMode = true

}

//配置自己的签名文件，签名文件的生成和导入可以去百度，本篇不讲解

signingConfigs {

release {

try {

keyAlias ‘china’

keyPassword ‘123456’

storeFile file(‘D:/work/release.jks’)

storePassword ‘123456’

} catch (ex) {

throw new InvalidUserDataException(ex.toString())

}

}

debug {

storeFile file(‘D:/work/debug.jks’)

keyAlias ‘china’

keyPassword ‘123456’

storePassword ‘123456’

}

}

defaultConfig {

applicationId “tinker.sample.android”

minSdkVersion 10

targetSdkVersion 22

versionCode 1

versionName “1.0.0”

/**

• 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”, "“1.0"”

buildConfigField “String”, “PLATFORM”, ““all””

}

// aaptOptions{

// cruncherEnabled false

// }

// //use to test flavors support

// productFlavors {

// flavor1 {

// applicationId ‘tinker.sample.android.flavor1’

// }

//

// flavor2 {

// applicationId ‘tinker.sample.android.flavor2’

// }

// }

buildTypes {

release {

minifyEnabled true

signingConfig signingConfigs.release

proguardFiles getDefaultProguardFile(‘proguard-android.txt’), ‘proguard-rules.pro’

}

debug {

debuggable true

minifyEnabled false

signingConfig signingConfigs.debug

proguardFiles getDefaultProguardFile(‘proguard-android.txt’), ‘proguard-rules.pro’

}

}

sourceSets {

main {

jniLibs.srcDirs = [‘libs’]

}

}

}

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 {

//for some reason, you may want to ignore tinkerBuild, such as instant run debug build?

tinkerEnabled = true

//for normal build

//old apk file to build patch apk

tinkerOldApkPath = “${bakPath}/app-release-0313-16-16-16.apk”

//proguard mapping file to build patch apk

tinkerApplyMappingPath = “${bakPath}/app-release-0313-16-16-mapping.txt”

//resource R.txt to build patch apk, must input if there is resource changed

tinkerApplyResourcePath = “${bakPath}/app-release-0313-16-16-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 = true

/**

• 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 = “1.0”/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

}

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 flavors = new ArrayList<>();

project.android.productFlavors.each {flavor ->

flavors.add(flavor.name)

}

boolean hasFlavors = flavors.size() > 0

/**

• bak apk and mapping

*/

android.applicationVariants.all { variant ->

/**

• task type, you want to bak

*/

def taskName = variant.name

def date = new Date().format(“MMdd-HH-mm-ss”)

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”)

自我介绍一下，小编13年上海交大毕业，曾经在小公司待过，也去过华为、OPPO等大厂，18年进入阿里一直到现在。

深知大多数初中级安卓工程师，想要提升技能，往往是自己摸索成长，但自己不成体系的自学效果低效又漫长，而且极易碰到天花板技术停滞不前！

因此收集整理了一份《2024年最新Android移动开发全套学习资料》送给大家，初衷也很简单，就是希望能够帮助到想自学提升又不知道该从何学起的朋友，同时减轻大家的负担。

由于文件比较大，这里只是将部分目录截图出来，每个节点里面都包含大厂面经、学习笔记、源码讲义、实战项目、讲解视频
如果你觉得这些内容对你有帮助，可以添加下面V无偿领取！（备注Android）

最后

考虑到文章的篇幅问题，我把这些问题和答案以及我多年面试所遇到的问题和一些面试资料做成了PDF文档，如果有需要的朋友可以私信我【面试】免费领取

点击这里领取Android面试资料汇总

lize()}ReleaseManifest")

自我介绍一下，小编13年上海交大毕业，曾经在小公司待过，也去过华为、OPPO等大厂，18年进入阿里一直到现在。

深知大多数初中级安卓工程师，想要提升技能，往往是自己摸索成长，但自己不成体系的自学效果低效又漫长，而且极易碰到天花板技术停滞不前！

因此收集整理了一份《2024年最新Android移动开发全套学习资料》送给大家，初衷也很简单，就是希望能够帮助到想自学提升又不知道该从何学起的朋友，同时减轻大家的负担。
[外链图片转存中…(img-06NbIPmj-1711203696516)]
[外链图片转存中…(img-yfk6CC2w-1711203696517)]
[外链图片转存中…(img-yfqf2STD-1711203696517)]
[外链图片转存中…(img-fSnK6bHQ-1711203696517)]

由于文件比较大，这里只是将部分目录截图出来，每个节点里面都包含大厂面经、学习笔记、源码讲义、实战项目、讲解视频
如果你觉得这些内容对你有帮助，可以添加下面V无偿领取！（备注Android）
[外链图片转存中…(img-sqS8y4zn-1711203696517)]

最后

考虑到文章的篇幅问题，我把这些问题和答案以及我多年面试所遇到的问题和一些面试资料做成了PDF文档，如果有需要的朋友可以私信我【面试】免费领取

点击这里领取Android面试资料汇总

[外链图片转存中…(img-Uoo89Qx9-1711203696518)]

[外链图片转存中…(img-0npCIUNI-1711203696518)]

喜欢的朋友可以关注、转发、点赞 感谢！