简体   繁体   English

支持库26.0.0的Firebase性能监视器问题

[英]Firebase performance monitor issue with support lib 26.0.0

I am getting the below error in com.google.firebase.firebase-perf plugin. 我在com.google.firebase.firebase-perf插件中收到以下错误。

Caused by: java.lang.NoClassDefFoundError: android/support/v7/app/ActionBarActivity at com.google.firebase.perf.plugin.instrumentation.InstrumentationConfigFactory.setAppStartConfig(InstrumentationConfigFactory.java:70) at com.google.firebase.perf.plugin.instrumentation.InstrumentationConfigFactory.(InstrumentationConfigFactory.java:62) at com.google.firebase.perf.plugin.instrumentation.Instrument.(Instrument.java:34) at com.google.firebase.perf.plugin.FirebaseTransform.transform(FirebaseTransform.java:192) at com.android.build.gradle.internal.pipeline.TransformTask$2.call(TransformTask.java:222) at com.android.build.gradle.internal.pipeline.TransformTask$2.call(TransformTask.java:218) at com.android.builder.profile.ThreadRecorder.record(ThreadRecorder.java:102) at com.android.build.gradle.internal.pipeline.TransformTask.transform(TransformTask.java:213) at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:73) at org.gradle.api.internal.project.taskfactory.DefaultTaskClassI 由以下原因引起:java.lang.NoClassDefFoundError:com.google.firebase.perf上com.google.firebase.perf.plugin.instrumentation.InstrumentationConfigFactory.setAppStartConfig(InstrumentationConfigFactory.java:70)上的android / support / v7 / app / ActionBarActivity。 com.google.firebase.perf.plugin.instrumentation.Instrument。(Instrument.java:34)上的plugin.instrumentation.InstrumentationConfigFactory。(InstrumentationConfigFactory.java:62),位于com.google.firebase.perf.plugin.FirebaseTransform.transform( com.android.build.gradle.internal.pipeline.TransformTask $ 2.call(TransformTask.java:222)的FirebaseTransform.java:192)com.android.build.gradle.internal.pipeline.TransformTask $ 2.call(TransformTask。 com.android.builder.profile.ThreadRecorder.record(ThreadRecorder.java:102)处com.android.build.gradle.internal.pipeline.TransformTask.transform(TransformTask.java:213)处的com.android.builder.profile.ThreadRecorder.record(ThreadRecorder.java:102)处的org.gradle org.gradle.api.internal.project.taskfactory.DefaultTaskClassI上的.internal.reflect.JavaMethod.invoke(JavaMethod.java:73) nfoStore$IncrementalTaskAction.doExecute(DefaultTaskClassInfoStore.java:168) at org.gradle.api.internal.project.taskfactory.DefaultTaskClassInfoStore$StandardTaskAction.execute(DefaultTaskClassInfoStore.java:134) at org.gradle.api.internal.project.taskfactory.DefaultTaskClassInfoStore$StandardTaskAction.execute(DefaultTaskClassInfoStore.java:121) at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$1.run(ExecuteActionsTaskExecuter.java:122) at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:336) at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:328) at org.gradle.internal.progress.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:197) at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:107) at org.gradle.api.internal.tasks.execution.E org.gradle.api.internal.project.taskfactory.DefaultTaskClassInfoStore $ StandardTaskAction.execute(DefaultTaskClassInfoStore.java:134)上的nfoStore $ IncrementalTask​​Action.doExecute(DefaultTaskClassInfoStore.java:168)在org.gradle.api.internal.project.taskfactory上。 org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter $ 1.run(ExecuteActionsTaskExecuter.java:122)处的DefaultTaskClassInfoStore $ StandardTaskAction.execute(DefaultTaskClassInfoStore.java:121)在org.gradle.internal.progress.DefaultBuildOperationExuteutor $ RunnableBuildOperationWorker。 (DefaultBuildOperationExecutor.java:336)在org.gradle.internal.progress.DefaultBuildOperationExecutor $ RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:328)在org.gradle.internal.progress.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java) gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:107)at org.gradle.api.internal.tasks.execution.E xecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:111) at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:92) ... 101 more Caused by: java.lang.ClassNotFoundException: android.support.v7.app.ActionBarActivity ... 120 more org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:92)处的xecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:111)... 101更多原因:java.lang.ClassNotFoundException:android.support .v7.app.ActionBarActivity ...还有120个

I am using the following libs : 我正在使用以下库:

  • com.google.firebase:firebase-plugins:1.1.1 com.google.firebase:firebase-plugins:1.1.1
  • com.google.firebase:firebase-perf:11.0.4 com.google.firebase:firebase-perf:11.0.4
  • Support lib 26.0.0 支持lib 26.0.0
  • build tool version 26.0.1 生成工具版本26.0.1

*fyi : It is working fine below support lib 26 * fyi:在支持库26下运行良好

We were facing similar issue. 我们面临着类似的问题。 It was one of the libraries which was causing this issue. 这是导致此问题的库之一。 That library was still using ActionBarActivity in their code. 该库仍在其代码中使用ActionBarActivity。 It worked fine after removing that library. 删除该库后,它工作正常。

EDIT: Alternatively, you can create a proxy class in your project. 编辑:或者,您可以在您的项目中创建一个代理类。 Create a class named ActionBarActivity under same package name as it is there in support library and make it extend AppCompatActivity class. 在与支持库中相同的程序包名称下创建一个名为ActionBarActivity的类,并扩展AppCompatActivity类。

https://developer.android.com/reference/android/support/v7/app/ActionBarActivity.html https://developer.android.com/reference/android/support/v7/app/ActionBarActivity.html

This class was deprecated in API level 24.2.0. 此类已在API级别24.2.0中弃用。 Use AppCompatActivity instead. 请改用AppCompatActivity。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 自支持lib 26.0.0起,折叠工具栏会出现小故障 - Collapsing Toolbar bouncing glitch since support lib 26.0.0 Firebase 性能监视器总是在使用 Retrofit 和 OkHttp 时崩溃 - Firebase Performance monitor crash always with Retrofit and OkHttp Firebase性能集成问题 - Firebase Performance integration issue 无法解析:com.android.support:appcompat-v7:26.0.0 - Failed to resolve: com.android.support:appcompat-v7:26.0.0 支持库26.0.0-beta2中的字体:错误:序言中不允许内容 - Fonts in Support Library 26.0.0-beta2: Error: Content is not allowed in prolog Firebase 性能监视器导致“D8:不支持的源文件类型” - Firebase performance monitor causing "D8: Unsupported source file type" 有什么方法可以在Firebase性能监视器中包括设备标识符? - Is there any way to include device identifier in firebase performance monitor? 如何在库模块内为 firebase 性能监视器添加自定义跟踪? - How to add custom traces for firebase performance monitor inside library module? 使用带有 slyce android sdk 的 Firebase 性能库时获取 classNotFindException - Getting classNotFindException when using Firebase performance lib with slyce android sdk Firebase性能测试版/插件构建问题 - Firebase Performance Beta / Plugin build issue
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM