New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
如果有加固的需求的话,该怎么使用呢 #2
Comments
Tinker目前支持梆梆加固吗?你这种方式每个APK的Dex的CRC值肯定不一样。 |
按照 @ltlovezh 的提示是可以的。
|
请问你是怎么做的啊,我打包后加固就读不到渠道信息了 |
(添加渠道信息一定要是最后一步) |
@ltlovezh 总结的很好 |
渠道包打好了但是补丁包还是没起作用,补丁包是打之前基础包的还是渠道包的 |
补丁包针对基础包打就好了,如果每个渠道包都生成补丁包,那岂不是也累死... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
看了你的文章介绍,如果有加固需求的话,这种改怎么弄了。
我们的场景如下,首先打出一个未签名的apk,然后使用梆梆加固,加固后添加渠道列表,得到10多个渠道包,然后再签名。这种场景下。怎么使用tinker的热修复呢。也就是我加固后的渠道包,他们的crc应该都不一样了吧。
The text was updated successfully, but these errors were encountered: