Amigo only take effect at first fix,then failed at second. And #29 can't solve it.

[letyouthgoon]

Amigo only take effect at first fix,then failed at second. And #29 can't solve it.

[FtheGFW]

需要你提供一下具体做了哪些操作, 步骤

[letyouthgoon]

@FtheGFW

./gradlew clean assembleRelease & adb install .../build/outputs/apk/app-release.apk
change code wherever you like & ./gradlew clean assembleRelease
adb push .../build/outputs/apk/app-release.apk /sdcard/demo.apk
kill Amigo demo by yourself & restart to check if your change works
________________________________________________________________________ok
change code wherever you like & ./gradlew clean assembleRelease
adb push .../build/outputs/apk/app-release.apk /sdcard/demo.apk
kill Amigo demo by yourself & restart to check if your change works
________________________________________________________________________no effect

[dxiaogang]

same as above .

[FtheGFW]

OK, 我觉得这个问题在#29中 @peacepassion 解释的比较清晰了，第二次load apk的时候，检测到在/data/data/me.ele.amigo.demo/files/amigo/下已存在一个demo.apk，然后就跳过load新的patch apk了

[letyouthgoon]

@OverRide
public void onCreate() {
super.onCreate();
Log.e(TAG, "onCreate: " + this);

    if (ProcessUtils.isMainProcess(this)) {
        File fixedApkFile = new File(Environment.getExternalStorageDirectory(), "demo.apk");
        if (fixedApkFile.exists()) {
            FileUtils.copyFile(fixedApkFile, Amigo.getHotfixApk(this));
        }
    }
}

so，这个就是＃29中的解决方案，然后报的就是本问题发的截图，现象是不停闪动。

[FtheGFW]

obviously, 陷入死循环了，建议你先用MD5比较一下fixedApkFile(新的pathc apk) 和 amigoApkFile (/data/data/me.ele.amigo.demo/files/amigo/demo.apk) 的md5值，然后如果这二者不同，再覆盖amigoApkFile

[FtheGFW]

或者简单暴力点，就直接清除app数据

[JackCho]

@letyouthgoon demo已更新，更容易理解Amigo的使用