2017-08-12 46 views
0

我有一臺運行Google Cloud Endpoints v1和Firebase Admin SDK的Google App Engine服務器。Google App Engine中'平臺方法丟失'和'NoSuchMethod'錯誤

當我的移動應用程序訪問其中一個雲端點時,我發現服務器上出現了以下錯誤,特別是生成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時,它顯示Firebase Admin SDK僅包含一個Guava依賴項(v20.0)。

回答

0

不知道發生了什麼,但用mvn clean修復了它。

+1

機會是你的項目建立與番石榴19.0。運行'mvn clean'從你的'target /'目錄中刪除舊的工件,然後用guava 20.0重新編譯這個工程 –