java.lang.VerifyError：Verifier被拒絕的類 - 無法驗證

Question

我正在使用protobuf在我的Android客戶端中使用gRPC技術自動生成我的API服務。 我已經好幾個月沒有問題了。 現在突然間，AndroidRuntime Verifier拒絕了我的API的一個自動生成的方法。

---

這是堆棧跟蹤：

com.company.companyplayer E/AndroidRuntime: FATAL EXCEPTION: main
                                        Process: com.company.companyplayer, PID: 18181
                                        java.lang.VerifyError: Verifier rejected class company.v1.PlayerEarningsPageDataResponse: void company.v1.PlayerEarningsPageDataResponse.mergeNextDepositDate(com.google.protobuf.Timestamp) failed to verify: void company.v1.PlayerEarningsPageDataResponse.mergeNextDepositDate(com.google.protobuf.Timestamp): [0x26] register v5 has type Precise Reference: com.google.protobuf.Timestamp but expected Reference: com.google.protobuf.GeneratedMessageLiteVerifier rejected class company.v1.PlayerEarningsPageDataResponse: java.lang.Object company.v1.PlayerEarningsPageDataResponse.dynamicMethod(com.google.protobuf.GeneratedMessageLite$MethodToInvoke, java.lang.Object, java.lang.Object) failed to verify: java.lang.Object company.v1.PlayerEarningsPageDataResponse.dynamicMethod(com.google.protobuf.GeneratedMessageLite$MethodToInvoke, java.lang.Object, java.lang.Object): [0x16E] register v8 has type Precise Reference: com.google.protobuf.Timestamp but expected Reference: com.google.protobuf.GeneratedMessageLite (declaration of 'company.v1.PlayerEarningsPageDataResponse' appears in /data/app/com.company.companyplayer-1/split_lib_slice_4_apk.apk)
                                            at company.v1.PlayerEarningsPageDataResponse.getDefaultInstance(PlayerEarningsPageDataResponse.java:0)
                                            at company.v1.APIGrpc.<clinit>(APIGrpc.java:47)
                                            at company.v1.APIGrpc.newStub(APIGrpc.java:0)
                                            at com.company.companyplayer.backend.Client.getAuthAsyncStub(Client.java:103)
                                            at com.company.companyplayer.backend.Client.playerLogin(Client.java:119)
                                            at com.company.companyplayer.ui.activity.LoginActivity.loginAndGoToMainActivity(LoginActivity.java:202)
                                            at com.company.companyplayer.ui.activity.LoginActivity.onActivityResult(LoginActivity.java:127)
                                            at android.app.Activity.dispatchActivityResult(Activity.java:6935)
                                            at android.app.ActivityThread.deliverResults(ActivityThread.java:4086)
                                            at android.app.ActivityThread.handleSendResult(ActivityThread.java:4133)
                                            at android.app.ActivityThread.-wrap20(ActivityThread.java)
                                            at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1534)
                                            at android.os.Handler.dispatchMessage(Handler.java:102)
                                            at android.os.Looper.loop(Looper.java:154)
                                            at android.app.ActivityThread.main(ActivityThread.java:6121)
                                            at java.lang.reflect.Method.invoke(Native Method)
                                            at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:889)
                                            at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:779)

---

以下（類似SO帖子建議的解決方案）不起作用：

• 清潔和重建（甚至嘗試手動清潔）
• 使高速緩存無效並重新啟動IDE
• 從proto重新生成API定義

---

另外，這里是stacktrace中指出的自動生成方法：

  private void mergeNextDepositDate(com.google.protobuf.Timestamp value) {
    if (nextDepositDate_ != null && nextDepositDate_ != com.google.protobuf.Timestamp.getDefaultInstance()) {
      nextDepositDate_ = com.google.protobuf.Timestamp.newBuilder(nextDepositDate_).mergeFrom(value).buildPartial();
    } else {
      nextDepositDate_ = value;
    } 
  }

可以看出，該方法既不冗長，也不需要太多參數; 有人說過這個錯誤的常見原因。

---

以下是我的應用程序的build.gradle :(自上次所有這些工作正常以來，gradle中沒有更改）

apply plugin: 'com.android.application'
apply plugin: 'com.google.protobuf'

android {
    compileSdkVersion 25
    buildToolsVersion '25.0.3'
    defaultConfig {
        applicationId "com.company.companyplayer"
        minSdkVersion 15
        targetSdkVersion 25
        versionCode 5
        versionName "0.1"
        testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
        multiDexEnabled true
        vectorDrawables.useSupportLibrary = true
    }
    buildTypes {
        release {
            minifyEnabled false
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
            signingConfig signingConfigs.config
        }
    }
    lintOptions {
        disable 'InvalidPackage'
    }
}

protobuf {
    protoc {
        artifact = 'com.google.protobuf:protoc:3.2.0'
    }
    plugins {
        javalite {
            artifact = "com.google.protobuf:protoc-gen-javalite:3.0.0"
        }
        grpc {
            artifact = 'io.grpc:protoc-gen-grpc-java:1.3.0'
        }
    }
    generateProtoTasks {
        all().each { task ->
            task.plugins {
                javalite {}
                grpc {
                    // Options added to --grpc_out
                    option 'lite'
                }
            }
        }
    }
}

dependencies {
    compile fileTree(include: ['*.jar'], dir: 'libs')
    androidTestCompile('com.android.support.test.espresso:espresso-core:2.2.2', {
        exclude group: 'com.android.support', module: 'support-annotations'
    })
    /* android support libraries */
    compile 'com.google.android:flexbox:0.2.7'
    compile 'com.android.support:multidex:1.0.1'
    compile 'com.google.firebase:firebase-config:11.0.1'
    compile 'com.google.firebase:firebase-core:11.0.1'
    compile 'com.google.firebase:firebase-messaging:11.0.1'
    compile 'com.google.android.gms:play-services-maps:11.0.1'
    compile 'com.google.android.gms:play-services-location:11.0.1'
    compile 'com.google.maps.android:android-maps-utils:0.4.4'
    compile 'com.google.code.findbugs:jsr305:3.0.1'
    compile 'io.grpc:grpc-okhttp:1.3.0'
    compile 'io.grpc:grpc-protobuf-lite:1.3.0'
    compile 'io.grpc:grpc-stub:1.3.0'
    compile 'com.facebook.android:facebook-android-sdk:[4,5)'
    compile 'com.facebook.android:account-kit-sdk:4.22.0'
    compile 'javax.annotation:javax.annotation-api:1.2'
    compile 'com.google.api.grpc:googleapis-common-protos:0.0.3' // This is for importing "google/api/annotations.proto" in our proto file
    testCompile 'junit:junit:4.12'
    androidTestCompile 'com.google.code.findbugs:jsr305:3.0.1'
    protobuf 'com.google.protobuf:protobuf-java:3.1.0'
}

apply plugin: 'com.google.gms.google-services'

---

更新：該錯誤肯定與google.protobuf.Timestamp 。 以下是重現此問題的MWE的鏈接 。

Answer 1

你正在混合精簡和完整的protobuf。

你不能在googleapis-common-protos上擁有編譯或運行時依賴，因為它是為完整protobuf生成的代碼，它不適用於lite protobuf。 它還引入了對protobuf-java的依賴，當與protobuf-lite混合時會導致重復的類。 使用protobuf依賴項而不是編譯依賴項，使protobuf gradle插件生成來自JAR中包含的.proto的代碼。

你目前也沒有對protobuf-lite任何依賴，所以如果沒有普通的protos依賴，你就會遇到編譯失敗。 常見的原型也帶來了所需的grpc-protobuf-lite依賴。 我建議在io.grpc:grpc-protobuf-lite:1.3.0上添加一個編譯時依賴io.grpc:grpc-protobuf-lite:1.3.0 ，它也會引入protobuf-lite 。

簡而言之，對項目進行這些更改並編譯：

diff --git a/app/build.gradle b/app/build.gradle
index 8f606bb..2fb997b 100644
--- a/app/build.gradle
+++ b/app/build.gradle
@@ -62,7 +62,8 @@ dependencies {
     compile 'javax.annotation:javax.annotation-api:1.2'
     compile 'io.grpc:grpc-stub:1.3.0'
     compile 'io.grpc:grpc-okhttp:1.3.0'
+    compile 'io.grpc:grpc-protobuf-lite:1.3.0'

-    compile 'com.google.api.grpc:googleapis-common-protos:0.0.3'
+    protobuf 'com.google.api.grpc:googleapis-common-protos:0.0.3'
     protobuf 'com.google.protobuf:protobuf-java:3.1.0'
 }