Tencent hotfix Tinker details and use

Reprint please indicate the source: blog.csdn.net/qq_33408235… I am a github:github.com/niezhiyang

1. Overview of hot repair

To put it bluntly, hot repair means “patching”. For example, when your company launches an app, users respond that there is a major bug and urgent repair is needed. As usual, programmers work overtime to fix bugs, test them, repackage them, and release them. The problem is high cost and low efficiency. And that’s where thermal repair comes in. Replace buggy code with bug-free code downloaded from the web through a pre-defined interface. This saves much trouble, user experience is good.

2. Overview of Tinker (this introduction is taken from the official website)

2.1 Comparison between Tinker and Ali’s AndFix, Meituan’s Robust and QZone

In summary:

1. As a native solution, AndFix first faces stability and compatibility problems. More importantly, it cannot realize class replacement, which requires a lot of extra development costs.
2. Robust compatibility and success rate are high, but like AndFix, it cannot add variables and classes and can only be used as bugFix schemes.
3. Qzone solution can release product functions, but its main problems are the performance problems of Dalvik caused by piling, and the rapid increase of patch packages in order to solve the memory address problem under Art.

Especially since Android N, it has not been easy to fix the various solutions on the market due to the inline policy changes of mixed compilation. Tinker hotfix not only supports class, So, and resource replacement, it also supports 2.x to 7.x platform. Tinker can not only be used as a Bugfix, but also as a replacement for feature publishing. Tinker already runs on wechat’s hundreds of millions of Android devices, so why don’t you use it?

2.2 Known problems of Tinker

3. Tinker Access Guide

In fact, the official website has said almost, just want to practice, and the pit to everyone to fill up, there are two access methods

• Gradle access (recommended by the official website and also introduced by this article)
• Command line access (not covered here)

3.1 Adding a Dependency

 dependencies {
        classpath 'com. Android. Tools. Build: gradle: 2.3.3'
        classpath ('com. Tencent. Tinker: tinker - patch - gradle - plugin: 1.8.0 comes with')/ / pluggin tinker
        // NOTE: Do not place your application dependencies here; they belong
        // in the individual module build.gradle files
    }Copy the code

dependencies {
    // Optional, used to generate the Application class
    provided('com. Tencent. Tinker: tinker - android - anno: 1.8.0 comes with')
    // Tinker's core library
    compile('com. Tencent. Tinker: tinker - android - lib: 1.8.0 comes with') 
    // The subcontract library can be used below
      compile 'com. Android. Support: multidex: 1.0.1'
}Copy the code

/ / the apply tinker plug-in
apply plugin: 'com.tencent.tinker.patch'Copy the code

3.2 Configuration parameters and introduction of Build. gradle in APP

3.2.1 Explain the meaning of parameters

We call the original APK package the benchmark APK package. TinkerPatch directly uses the benchmark APK package to make differences with the newly compiled APK package to obtain the final patch package. Gradle configuration parameters are explained as follows:

3.2.2 According to mybuild.gradleOr the websitebuild.gradleConfigure build.gradle. In fact, mine is the same as the one on the official website

signingConfigs { release { try { storeFile file(".. /demojks.jks") // .. StorePassword '123456' keyAlias' Demojks' keyPassword '123456'} Catch (ex) {throw new InvalidUserDataException(ex.toString()) } } debug { storeFile file(".. /demojks.jks") storePassword '123456' keyAlias 'demojks' keyPassword '123456' } }Copy the code

3.3 Simulation of online APK production (that is, apK released to the market)

MyApplicationLike extends ApplicationLike, which is not an application, but rewrites the onCreate method as follows: Note that there is an annotation in this class @DefaultLifecycle that the application inside is a custom application, remember to use it in the manifest file

    @DefaultLifeCycle(application = ".MyApplication".// This class is really a custom application. Don't forget to use it in androidmanifest.xml
            flags = ShareConstants.TINKER_ENABLE_ALL,
            loadVerifyFlag =true)
    public class MyApplicationLike extends ApplicationLike {
        public MyApplicationLike(Application application, int tinkerFlags, boolean tinkerLoadVerifyFlag, long applicationStartElapsedTime, long applicationStartMillisTime, Intent tinkerResultIntent) {
            super(application, tinkerFlags, tinkerLoadVerifyFlag, applicationStartElapsedTime, applicationStartMillisTime, tinkerResultIntent);
        }
        @Override
        public void onBaseContextAttached(Context base) {
            super.onBaseContextAttached(base);
            MultiDex.install(base);
            TinkerInstaller.install(this);

        }
        @Override
            public void onCreate() {
                super.onCreate(); }}Copy the code

Deliberately miswrite code in mainactivity. Java, such as a button that will crash when clicked

@Override protected void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); setContentView(R.layout.activity_main); // loadPatch loadPatch(); } private void loadPatch() { String path = Environment.getExternalStorageDirectory().getAbsolutePath()+"/patch.apk"; File file = new File(path); If (the file. The exists ()) {/ / load the patch TinkerInstaller. OnReceiveUpgradePatch (getApplicationContext (), the path). }else {toast.maketext (this, "patch does not exist ", toast.length_short).show(); } } public void test(View view) { int i=1/0; // The button will crash when clicked.Copy the code

3,3.1 run:

Tinker does not support Instant Run. Go to File – > Settings – > Search for Instant Run and close it

3.3.2 Both Demo. apk and patch APK must be release versions. Change Build Variant to Release version, as shown below

3.3.3 Look at the position below after running, this APK is the APK that you have packaged and published online

3.4 Patch Package ApK Package

    public void test(View view) {
    // int i=1/0;
       Toast.makeText(this."I'm fixed. I'm not broken.", Toast.LENGTH_SHORT).show();
        }Copy the code

    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-1026-17-04-59.apk"
    //proguard mapping file to build patch apk
    tinkerApplyMappingPath = "${bakPath}/app-release-1026-17-04-59-mapping.txt"
    //resource R.txt to build patch apk, must input if there is resource changed
    tinkerApplyResourcePath = "${bakPath}/app-release-1026-17-04-59-R.txt"

    //only use for build all flavor, if not, just ignore this field
    tinkerBuildFlavorDirectory = "${bakPath}/app-release-1026-17-04-59"
}Copy the code

Source locationgithub