java.lang.IllegalStateException:预期为.,<或;,但是在解压缩时发现了firebaseperf [英] java.lang.IllegalStateException: Expecting .,<, or ;, but found firebaseperf while unpacking

查看:55
本文介绍了java.lang.IllegalStateException:预期为.,<或;,但是在解压缩时发现了firebaseperf的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在我的应用程序中集成了性能sdk之后,gradle在构建项目时会打印以下警告:

After integrating the performance sdk in my app, gradle is printing the following warning while building the project:

java.lang.IllegalStateException:预期为.,<或;,但在拆包时找到firebaseperf; BuilderType:Lcom/google/android/gms/internal/firebase-perf/zzam;> Ljava/lang/Object; Lcom/google/android/gms/internal/firebase-perf/zzdf;

java.lang.IllegalStateException: Expecting .,<, or ;, but found firebaseperf while unpacking ;BuilderType:Lcom/google/android/gms/internal/firebase-perf/zzam;>Ljava/lang/Object;Lcom/google/android/gms/internal/firebase-perf/zzdf;

尽管它不会使构建失败,但我不确定这意味着什么,因此在我确定它不会造成任何问题之前,不希望将其投入生产.

Though it's not failing the build, I am not sure what does this mean and therefore don't want to push this into production until I am sure that it won't cause any problem.

有人可以在这里帮忙吗?

Can anyone please help here?

Performance sdk version: 15.2.0

Firebase core version: 15.0.2

推荐答案

我自己遇到了一个单独的项目.您可以修改传递给hugo插件的类路径,以省略 firebase-perf 模块本身.

I ran into this myself with a separate project. You can modify the classpath that is passed to hugo's plugin to omit the firebase-perf module itself.

    def filtered_class_filetree = javaCompile.classpath.asFileTree.filter {
        !it.canonicalPath.contains("firebase-perf")
    }

我认为发生这种情况是因为Google/Firebase修改了原始方面的编译器以支持其他功能,因此在其上运行常规的ACJ编译器会使它报废.

I'm assuming this happens because Google/Firebase modified the original aspect compiler to support other functionality, thus running the normal ACJ compiler over it makes it crap out.

这篇关于java.lang.IllegalStateException:预期为.,&lt;或;,但是在解压缩时发现了firebaseperf的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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