这类似于Rejecting class because it failed compile-time verification Android和java.lang.VerifyError: Verifier rejected class on Lollipop when using release APK,但我的问题的根源仍然未知,所有提出的解决方案都无济于事。
手动安装带有MultiDex支持且已启用ProGuard的签名版本apk会在启动时抛出此异常:
475-475/? E/AndroidRuntime: FATAL EXCEPTION: main
Process: ..., PID: 475
java.lang.VerifyError: Verifier rejected class android.support.g.b due to bad method void android.support.g.b.<init>() (declaration of 'android.support.g.b' appears in /data/app/...-2/base.apk)
at ...MyApp.attachBaseContext(Unknown Source)
at android.app.Application.attach(Application.java:181)
-dontoptimize
不会发生这种情况。当前最小优化设置:
-optimizations "code/*"
没有-optimizations
或限制较少的选项,我得到相同的错误。添加-keep class android.*
也不会有帮助。我没有得到"code/removal/*,code/simplification/*"
的错误,但这忽略了-assumenosideeffects
android.support.g.b是混淆的android.support.multidex.MultiDex类本身,并且在调用被覆盖的attachBaseContext(Context)
时会导致错误:
@Override
protected void attachBaseContext(Context base) {
super.attachBaseContext(base);
MultiDex.install(this);
}
使用字节代码查看器解码此方法(默认构造函数)会导致:
private b() { // <init> //()V
return
}
-optimizations
的最小-assumenosideeffects
选项不要将成员通配符与-assumenosideeffects
一起使用,因为这会为其他类“溢出”到Object。见https://sourceforge.net/p/proguard/bugs/716/#98d4
任何带接口的规则都可能出现类似的问题。例:
-assumenosideeffects class * implements Interface {
public <init>();
public Object interfacemethod(); # May concern methods with same signature in other Objects
}