tinker(一)-集成
来源:互联网 发布:淘宝卖明星同款 编辑:程序博客网 时间:2024/05/22 14:25
官网:http://www.tinkerpatch.com/Docs/intro
一、在project的gradle中添加:
dependencies { classpath 'com.android.tools.build:gradle:2.3.3' classpath ('com.tencent.tinker:tinker-patch-gradle-plugin:1.7.11')}
二、在module中的gradle中添加:
dependencies { //可选,用于生成application类 provided 'com.tencent.tinker:tinker-android-anno:1.7.9' //tinker的核心库 compile('com.tencent.tinker:tinker-android-lib:1.7.11')}
apply plugin: 'com.tencent.tinker.patch' //在顶部
android { compileSdkVersion 26 buildToolsVersion "25.0.2" ..............中间省略 dexOptions { jumboMode = true }}
三、在gradle中配置tinker参数:
def gitSha() { return android.defaultConfig.versionName //我没有配置git,所以用本地的versionName替代// 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'")// }}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-debug.apk" //proguard mapping file to build patch apk tinkerApplyMappingPath = "${bakPath}/app-debug-mapping.txt" //resource R.txt to build patch apk, must input if there is resource changed tinkerApplyResourcePath = "${bakPath}/app-debug-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 = 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 = ["com.tencent.tinker.loader.*", "com.qiyei.funny.MyApplication" ] } 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" } }
四、配置application:
@DefaultLifeCycle( application = "com.android.**.Application", //这里更改为你自己的包名 . 要用的applacation名即可 flags = ShareConstants.TINKER_ENABLE_ALL)public class MyApplication extends DefaultApplicationLike {
@TargetApi(Build.VERSION_CODES.ICE_CREAM_SANDWICH)public void registerActivityLifecycleCallbacks(Application.ActivityLifecycleCallbacks callback) { getApplication().registerActivityLifecycleCallbacks(callback);}@Overridepublic void onBaseContextAttached(Context base) { super.onBaseContextAttached(base); MultiDex.install(getContext()); TinkerInstaller.install(this);}
至此,全部配置完毕,配置中如果不是完全这样配置的话会有一些问题,官方也有解决方法,百度一大堆,很简单,并且tinker已经支持加固。
阅读全文
0 0
- tinker(一)-集成
- Tinker集成和使用(一)Tinker简介和运行Tinker示例出现的问题
- 腾讯Tinker 热修复 Andriod studio 3.0 配置和集成(一)
- 热更新Tinker研究(一):运行tinker-sample-android
- 集成tinker热更新
- Tinker集成步骤
- tinker热修复--集成tinker patch 详解
- 微信热补丁解决方案Tinker初探(一)
- Tinker接入及源码分析(一)
- android热修复框架Tinker(一)
- Tinker接入及源码分析(一)
- Android热修复(微信tinker的集成)
- 微信热升级tinker集成项目
- 微信tinker快速集成
- 微信热补丁Tinker -- 项目集成
- tinker第1部-集成
- 热修复Tinker快速集成
- 10分钟快速集成tinker
- ListView异步创建View
- nginx-1.12.1 + openssl-1.1.0f 静态编译
- jvm关于内存管理和垃圾回收的学习总结
- 打包oracle的JDBC驱动到maven仓库
- jQuery.ajax各种参数及属性设置
- tinker(一)-集成
- 响应式童装服装展示类dedecms织梦模板
- [51nod 1287]加农炮
- 微信jssdk多图上传
- 关于Android系统开放所有App运用的权限
- iOS源码博文集锦1
- 使用命令行下载百度云盘的数据
- 在Activity类之外监听Activity的生命周期
- 扑克游戏(小根堆)