

只要你严格按照以下步骤肯定没有问题的!!
第一步:工程的gradle下配置
Android Studio 3.0依赖:
classpath "com.tencent.bugly:tinker-support:1.1.1"
Android Studio 2.2.2 依赖:
classpath "com.tencent.bugly:tinker-support:latest.release"
第二步:App的gradle下配置
Android Studio 3.0依赖:
// 多dex配置
compile 'com.android.support:multidex:1.0.1'
// 远程仓库集成方式(推荐)
implementation 'com.tencent.bugly:crashreport_upgrade:1.3.4'
Android Studio 2.2.2 依赖:
compile 'com.tencent.bugly:crashreport_upgrade:latest.release'
第三步: 在App下创建 tinker-support.gradle
apply plugin: 'com.tencent.bugly.tinker-support'
def bakPath = file("${buildDir}/bakApk/")
/**
* 此处填写每次构建生成的基准包目录
*/
def baseApkDir = "app-0504-21-17-43"
/**
* 对于插件各参数的详细解析请参考
*/
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"
// 对应tinker插件applyMapping
baseApkProguardMapping = "${bakPath}/${baseApkDir}/app-release-mapping.txt"
// 对应tinker插件applyResourceMapping
baseApkResourceMapping = "${bakPath}/${baseApkDir}/app-release-R.txt"
tinkerId = "1.0.1-patch"
// 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
*/
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的分配
}
}
第四步:完成代码,进行签名打包
然后在App的gradle包下会自动生成:
pply plugin: 'com.android.application'
apply from: 'tinker-support.gradle'
android {
signingConfigs {
release {
keyAlias 'key0'
keyPassword '123456'
storeFile file('E:/code/AndroidProject_WorkSpace/TinkerDemo/app/res.jks')
storePassword '123456'
}
}
compileSdkVersion 26
defaultConfig {
applicationId "com.shenxuesong.tinkerdemo"
minSdkVersion 15
targetSdkVersion 26
versionCode 1
versionName "1.0"
testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
// 开启multidex
multiDexEnabled true
ndk {
//设置支持的SO库架构,模拟器需要‘x86’,‘armeabi-v7a’
abiFilters 'armeabi', 'x86', 'armeabi-v7a', 'x86_64', 'arm64-v8a'
}
}
dexOptions {
jumboMode = true
}
buildTypes {
release {
minifyEnabled false
proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
signingConfig signingConfigs.release
}
}
}
dependencies {
implementation fileTree(include: ['*.jar'], dir: 'libs')
//noinspection GradleCompatible
implementation 'com.android.support:appcompat-v7:27.1.1'
implementation 'com.android.support.constraint:constraint-layout:1.1.0'
testImplementation 'junit:junit:4.12'
androidTestImplementation 'com.android.support.test:runner:1.0.2'
androidTestImplementation 'com.android.support.test.espresso:espresso-core:3.0.2'
// 多dex配置
compile 'com.android.support:multidex:1.0.1'
// 远程仓库集成方式(推荐)
implementation 'com.tencent.bugly:crashreport_upgrade:1.3.4'
implementation files('libs/testSo.jar')
}
注意上面标红的配置!上面是有bug的打包配置生成(传说中的基准线包)如下图:
开始修改代码,进行打补丁包
最后到腾讯Bugly进行上传APK,进行基准包的上传
补丁包的上传
然后将基准包运行到模拟器,再将它强制关闭,再启动,点击下载手动下载补丁就OK了
具体的代码Github:点击打开链接
切记第一次是有Bug的包,然后补丁打的包可以修复