Google App Engine中的java“平台方法缺失”和“NoSuchMethod”错误

Question

我有一个运行Google Cloud Endpoints v1和Firebase Admin SDK的Google App Engine服务器

当我的移动应用程序访问其中一个云端点时，我在服务器上收到了以下错误，特别是一个生成HTTP请求的端点（不确定这是否相关）。然而，从应用程序访问的所有其他云端点都正常工作

com.google.appengine.repackaged.com.google.protobuf.UnsafeUtil supportsUnsafeByteBufferOperations
WARNING: platform method missing - proto runtime falling back to safer methods: java.security.AccessControlException: access denied ("java.lang.RuntimePermission" "accessClassInPackage.sun.misc")
com.google.appengine.repackaged.com.google.protobuf.UnsafeUtil supportsUnsafeArrayOperations
WARNING: platform method missing - proto runtime falling back to safer methods: java.security.AccessControlException: access denied ("java.lang.RuntimePermission" "accessClassInPackage.sun.misc")
com.google.appengine.repackaged.com.google.protobuf.UnsafeUtil supportsUnsafeCopyMemory
WARNING: copyMemory is missing from platform - proto runtime falling back to safer methods.
com.google.api.server.spi.SystemServiceServlet init
INFO: SPI restricted: true
com.google.api.server.spi.SystemService invokeServiceMethod
SEVERE: exception occurred while calling backend method
java.lang.NoSuchMethodError: com.google.common.base.Preconditions.checkState(ZLjava/lang/String;Ljava/lang/Object;)V
    at com.google.firebase.FirebaseApp.checkNotDeleted(FirebaseApp.java:314)
    at com.google.firebase.FirebaseApp.getOptions(FirebaseApp.java:260)
    at com.google.firebase.auth.FirebaseAuth.<init>(FirebaseAuth.java:74)
    at com.google.firebase.auth.FirebaseAuth.<init>(FirebaseAuth.java:61)
    at com.google.firebase.auth.FirebaseAuth.<init>(FirebaseAuth.java:52)
    at com.google.firebase.auth.FirebaseAuth$FirebaseAuthService.<init>(FirebaseAuth.java:316)
    at com.google.firebase.auth.FirebaseAuth.getInstance(FirebaseAuth.java:98)
    at com.google.firebase.auth.FirebaseAuth.getInstance(FirebaseAuth.java:85)

有人能提供建议吗

我研究过类似的报告，这些报告表明，番石榴依赖性存在相互冲突的版本。当运行mvn dependency:tree时，它显示只有一个Guava依赖项（v20.0），Firebase Admin SDK包含了该依赖项

Answer 1

不知道发生了什么，但用mvn clean修复了它