Bugly problems encountered summary

Disclaimer: This article is a blogger original article, shall not be reproduced without the bloggers allowed. https://blog.csdn.net/qq_34262972/article/details/87708455

Some of the problems encountered with regard to the configuration of Bugly hot update

1, pay attention to packaging obfuscated code

// 构建类型
    buildTypes {
        release {
            minifyEnabled true
            signingConfig signingConfigs.release
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
        }
        debug {
            debuggable true
            minifyEnabled false
            signingConfig signingConfigs.debug
        }

Obfuscated code is not a necessary step, here is obfuscated code minifyEnabled role, not obfuscated code minifyEnabled to be set true

2.bugly version best use

compile 'com.tencent.tinker:tinker-android-lib:1.9.9'

There are two ways to use application 3.bugly

Using their own application, using one kind of official decoupling load, different ways cf official website on it.

4.thinker_id this is to be noted that the base package to fight to keep the consistency, playing patch when the corresponding base directory and modify baseApkDir thinker_id

5.

If the problem is probably not add this tinkerEnable = true

6.mainfest configuration, you need to modify

<!-- Bugly升级SDK配置开始  -->
        <activity
            android:name="com.tencent.bugly.beta.ui.BetaActivity"
            android:configChanges="keyboardHidden|orientation|screenSize|locale"
            android:theme="@android:style/Theme.Translucent" />
        <!--API 24以上配置-->
        <provider
            android:name="com.android.incongress.cd.conference.receiver.UpdateFileProvider"
            android:authorities="${applicationId}.fileProvider"
            android:exported="false"
            android:grantUriPermissions="true">
            <meta-data
                android:name="android.support.FILE_PROVIDER_PATHS"
                android:resource="@xml/provider_paths" />
        </provider>

7. upload the data packet may not detect the current base package will happen, there may not be successfully completed base package, you can verify

First lay the base package, after installation open the search tinkerid, to see if has been reported.

8.TinkerLoader: tryLoadPatchFiles:patch dir not exist:/data/user/0/com.mobile.

Met this, you need to finish packing base_apk, start the installation log carrier to see if there is tinkerId

There are a lot of problems in the integration process, not list them all, before recording it, if the problem can be made to explore together