验证错误:验证器拒绝使用 Gradle 插件 3.2.0 + Proguard 去除日志的类 com.google.firebase.FirebaseApp [英] VerifyError: Verifier rejected class com.google.firebase.FirebaseApp using Gradle Plugin 3.2.0 + Proguard to strip logs

查看:35
本文介绍了验证错误:验证器拒绝使用 Gradle 插件 3.2.0 + Proguard 去除日志的类 com.google.firebase.FirebaseApp的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在我们的项目中我们已经成功使用了:

In our project we have been using successfully:

  • Firebase(用于 FCM)
  • Crashlytics(用于报告崩溃)
  • Proguard(优化版)

一切都很顺利,直到上周我们升级到 gradle 插件 3.2.0.

All was going fine until last week, when we upgraded to gradle plugin 3.2.0.

在这个版本中,如果我们有以下proguard配置来移除对Log的调用:

In this version, if we have the following proguard configuration to remove calls to Log:

-assumenosideeffects class android.util.Log { *; }

运行应用程序时,我们得到:

when running the app, we get:

java.lang.VerifyError: 验证器拒绝类 com.google.firebase.FirebaseApp: void com.google.firebase.FirebaseApp.() 验证失败: void com.google.firebase.FirebaseApp.(): [0x37]注册 v0 具有类型未初始化参考:java.lang.Object 分配 PC:53 但预期参考:java.lang.Objectvoid com.google.firebase.FirebaseApp.(android.content.Context, java.lang.String, com.google.firebase.b) 验证失败:void com.google.firebase.FirebaseApp.(android.content.Context,java.lang.String, com.google.firebase.b): [0x3C] register v8 的类型为未初始化参考:com.google.firebase.internal.a 分配 PC:58 但预期参考:com.google.firebase.FirebaseApp$一种com.google.firebase.FirebaseApp com.google.firebase.FirebaseApp.a(android.content.Context, com.google.firebase.b, java.lang.String) 未能验证:com.google.firebase.FirebaseApp com.google.firebase.FirebaseApp.a(android.content.Context, com.google.firebase.b, java.lang.String): [0x17] 寄存器 v1 的类型为未初始化参考:com.google.firebase.FirebaseApp$1 分配 PC:21 但预期参考:com.google.android.gms.common.api.internal.a$a('com.google.firebase.FirebaseApp' 的声明出现在/data/app/com.example.app-2/base.apk)`

java.lang.VerifyError: Verifier rejected class com.google.firebase.FirebaseApp: void com.google.firebase.FirebaseApp.() failed to verify: void com.google.firebase.FirebaseApp.(): [0x37] register v0 has type Uninitialized Reference: java.lang.Object Allocation PC: 53 but expected Reference: java.lang.Object void com.google.firebase.FirebaseApp.(android.content.Context, java.lang.String, com.google.firebase.b) failed to verify: void com.google.firebase.FirebaseApp.(android.content.Context, java.lang.String, com.google.firebase.b): [0x3C] register v8 has type Uninitialized Reference: com.google.firebase.internal.a Allocation PC: 58 but expected Reference: com.google.firebase.FirebaseApp$a com.google.firebase.FirebaseApp com.google.firebase.FirebaseApp.a(android.content.Context, com.google.firebase.b, java.lang.String) failed to verify: com.google.firebase.FirebaseApp com.google.firebase.FirebaseApp.a(android.content.Context, com.google.firebase.b, java.lang.String): [0x17] register v1 has type Uninitialized Reference: com.google.firebase.FirebaseApp$1 Allocation PC: 21 but expected Reference: com.google.android.gms.common.api.internal.a$a (declaration of 'com.google.firebase.FirebaseApp' appears in /data/app/com.example.app-2/base.apk)`

如果我们删除该配置以去除对 Log 的调用,一切都很好,就像在以前的 gradle 插件版本 (3.1.4) 中一样.

If we remove that config to strip the calls to Log all is fine, as it was in the previous version of the gradle plugin (3.1.4).

有没有人知道可能导致这种情况的原因?

Does anyone have an idea on what might be causing this?

推荐答案

proguard -assumenosideeffectsLog 好像有问题.

Seems like there is some problem with proguard -assumenosideeffects and Log.

尝试仅在您使用的方法以及依赖于那些 Log 方法的任何方法上使用 -assumenosideffects.

Try using -assumenosideffects only on the methods you use and whichever methods that depend on those Log methods.

类似于:

-assumenosideeffects class android.util.Log {
    public static *** v(...);
    public static *** d(...);
    public static *** i(...);
    public static *** w(...);
    public static *** e(...);
}

而不是通常的

-assumenosideeffects class android.util.Log {*;}

希望这会有所帮助.

这篇关于验证错误:验证器拒绝使用 Gradle 插件 3.2.0 + Proguard 去除日志的类 com.google.firebase.FirebaseApp的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
相关文章
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆