android--------微信 Tinker 热修复（二）

前面简单介绍了一下Tinker热修复，今天就来分享一下如何在Android中使用，希望对各位有帮助。

1：Tinker 接入指南

在项目的build.gradle中，添加tinker-patch-gradle-plugin的依赖

  dependencies {
        classpath 'com.android.tools.build:gradle:2.2.3'
        classpath ('com.tencent.tinker:tinker-patch-gradle-plugin:1.9.1')
        // NOTE: Do not place your application dependencies here; they belong
        // in the individual module build.gradle files
    }

然后在app的gradle文件app/build.gradle，我们需要添加tinker的库依赖以及apply tinker的gradle插件.

dependencies {
    //可选，用于生成application类 
    provided('com.tencent.tinker:tinker-android-anno:1.9.1')
    //tinker的核心库
    compile('com.tencent.tinker:tinker-android-lib:1.9.1') 
}
...

//apply tinker插件
apply plugin: 'com.tencent.tinker.patch'

 <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>
 <uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE"/>

可以参考官方配置或者我的Demo中两个gradle文件的配置

Tinker 接入指南

2：API主要就是初始化和loadPacth

初始化Application

@SuppressWarnings("unused")
@DefaultLifeCycle(application = "tinker.sample.android.app.SampleApplication",
                  flags = ShareConstants.TINKER_ENABLE_ALL,
                  loadVerifyFlag = false)
public class SampleApplicationLike extends DefaultApplicationLike {
    private static final String TAG = "Tinker.SampleApplicationLike";

    public SampleApplicationLike(Application application, int tinkerFlags, boolean tinkerLoadVerifyFlag,
                                 long applicationStartElapsedTime, long applicationStartMillisTime, Intent tinkerResultIntent,
                                 Resources[] resources, ClassLoader[] classLoader, AssetManager[] assetManager) {
        super(application, tinkerFlags, tinkerLoadVerifyFlag, applicationStartElapsedTime, applicationStartMillisTime, tinkerResultIntent, resources, classLoader, assetManager);
    }

    /**
     * install multiDex before install tinker
     * so we don't need to put the tinker lib classes in the main dex
     *
     * @param base
     */
    @TargetApi(Build.VERSION_CODES.ICE_CREAM_SANDWICH)
    @Override
    public void onBaseContextAttached(Context base) {
        super.onBaseContextAttached(base);
        //you must install multiDex whatever tinker is installed!
        MultiDex.install(base);

        SampleApplicationContext.application = getApplication();
        SampleApplicationContext.context = getApplication();
        TinkerManager.setTinkerApplicationLike(this);
        TinkerManager.initFastCrashProtect();
        //should set before tinker is installed
        TinkerManager.setUpgradeRetryEnable(true);

        //optional set logIml, or you can use default debug log
        TinkerInstaller.setLogIml(new MyLogImp());

        //installTinker after load multiDex
        //or you can put com.tencent.tinker.** to main dex
        TinkerManager.installTinker(this);
    }

    @TargetApi(Build.VERSION_CODES.ICE_CREAM_SANDWICH)
    public void registerActivityLifecycleCallbacks(Application.ActivityLifecycleCallbacks callback) {
        getApplication().registerActivityLifecycleCallbacks(callback);
    }

}

  <application
        android:name=".app.SampleApplication"
        android:icon="@mipmap/ic_launcher"
        android:label="@string/app_name"
        android:theme="@style/AppTheme">

第一个是验证补丁是否修复成功，第二个按钮是补丁修复操作

  textView.setOnClickListener(new View.OnClickListener() {
            @Override
            public void onClick(View v) {
                //以此来验证是否修复
                Toast.makeText(MainActivity.this,"未修复",Toast.LENGTH_SHORT).show();
            }
        });
  loadPatchButton.setOnClickListener(new View.OnClickListener() {
            @Override
            public void onClick(View v) {
                TinkerInstaller.onReceiveUpgradePatch(getApplicationContext(), 
                        Environment.getExternalStorageDirectory().getAbsolutePath() + "/patch_signed_7zip.apk");
            }

3：编译运行apk

as工具右边点击 Gradle --->点击展开目录,如图：

点击assembleDebug生成apk ，如下图：（如果出错则需要关闭Instant Run ）

4：效果图

点击文字测试显示未修复消息

点击按钮Load Patch 出现文件不存在，那是因为补丁文件还没有打包生成，

5：热修复补丁文件生成

先修改我们程序上面要修改的错误，我的只是测试很简单

 textView.setOnClickListener(new View.OnClickListener() {
            @Override
            public void onClick(View v) {
                //以此来验证是否修复
                Toast.makeText(MainActivity.this,"已修复",Toast.LENGTH_SHORT).show();
            }
        });

在app下面的bulid.gradle文件中改成对应日期需要修复的apk名称

    tinkerOldApkPath = "${bakPath}/app-debug-0302-17-14-53.apk"
    //proguard mapping file to build patch apk
    tinkerApplyMappingPath = "${bakPath}/app-debug-0302-17-14-53-mapping.txt"
    //resource R.txt to build patch apk, must input if there is resource changed
    tinkerApplyResourcePath = "${bakPath}/app-debug-0302-17-14-53-R.txt"

    //only use for build all flavor, if not, just ignore this field
    tinkerBuildFlavorDirectory = "${bakPath}/app-debug-0302-17-14-53-R.txt"

 oldApk = "${bakPath}/app-debug-0302-17-14-53.apk"

改好之后我们就可以生成修复补丁包了，点击tinkerPatchDebug 生成，如图：

生成补丁包，如图：

补丁包生成成功

6：为什么要使用热修复，补丁文件apk的使用

原因：比如你们公司上线一个app，用户反应有重大bug,需要紧急修复。如果按照通
常做法,那就是程序猿加班搞定bug,然后测试,重新打包并发布。这样带来的问题就是成本高,效率低。于是,热
修复就应运而生.一般通过事先设定的接口从网上下载无Bug的代码来替换有Bug的代码。这样就省事多了,用
户体验也好。

这里我们通过adb命令来上传到手机本地内存目录下，然后修复错误，

adb命令相关请看博客： http://www.cnblogs.com/zhangqie/p/8505252.html