使用 minifyEnabled true 启动应用程序时 FirebaseInitProvider.onCreate 中的 java.lang.IncompatibleClassChangeError [英] java.lang.IncompatibleClassChangeError inside FirebaseInitProvider.onCreate when starting app with minifyEnabled true

查看:226
本文介绍了使用 minifyEnabled true 启动应用程序时 FirebaseInitProvider.onCreate 中的 java.lang.IncompatibleClassChangeError的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

  • Android Studio:Android Studio Arctic Fox Beta 2 和 Bumblebee Canary 1
  • AGP:7.1.0-alpha01
  • Firebase 分析:com.google.firebase:firebase-analytics-ktx:19.0.0
  • Firebase Crashlytics:com.google.firebase:firebase-crashlytics-ktx:18.0.0
  • minifyEnabled:真
  • 专门针对 Firebase 的 Proguard 配置:无

当我使用 minifyEnabled = true 构建我的应用程序并尝试启动应用程序时,应用程序在启动后立即崩溃并显示以下崩溃日志:

When I build my app with minifyEnabled = true and try to start the app, app crashes right after it launches with the following crash log:

2021-05-29 22:30:37.652 16541-16541/com.my.app.package.name E/AndroidRuntime: FATAL EXCEPTION: main
    Process: com.my.app.package.name, PID: 16541
    java.lang.IncompatibleClassChangeError: Class j$.util.concurrent.i implements non-interface class e.a (declaration of 'j$.util.concurrent.i' appears in /data/app/~~xxxx==/com.my.app.package.name--xxxxxx==/base.apk!classes2.dex)
        at com.google.firebase.components.x.<init>(:37)
        at com.google.firebase.components.x.b(:44)
        at com.google.firebase.components.n.t(:219)
        at com.google.firebase.components.n.j(:138)
        at com.google.firebase.components.n.<init>(:91)
        at com.google.firebase.components.n.<init>(:45)
        at com.google.firebase.components.n$b.e(:360)
        at com.google.firebase.c.<init>(:427)
        at com.google.firebase.c.p(:299)
        at com.google.firebase.c.o(:267)
        at com.google.firebase.c.n(:252)
        at com.google.firebase.provider.FirebaseInitProvider.onCreate(:51)
        at android.content.ContentProvider.attachInfo(ContentProvider.java:2388)
        at android.content.ContentProvider.attachInfo(ContentProvider.java:2358)
        at com.google.firebase.provider.FirebaseInitProvider.attachInfo(:45)
        at android.app.ActivityThread.installProvider(ActivityThread.java:7242)
        at android.app.ActivityThread.installContentProviders(ActivityThread.java:6783)
        at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6700)
        at android.app.ActivityThread.access$1300(ActivityThread.java:237)
        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1913)
        at android.os.Handler.dispatchMessage(Handler.java:106)
        at android.os.Looper.loop(Looper.java:223)
        at android.app.ActivityThread.main(ActivityThread.java:7660)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)

注意事项

  • 配置 minifyEnabled = false 修复了问题,应用可以按预期启动.
  • 可能与以下内容有关或重复:由 R8 (AGP 7.0.0-beta02) 引起的 java.lang.IncompatibleClassChangeError.
  • Notes

    • Configuring minifyEnabled = false fixes the issue and app can start as expected.
    • Maybe it is related or dup of: java.lang.IncompatibleClassChangeError caused by R8 (AGP 7.0.0-beta02).
    • 推荐答案

      自 AGP 7.0.0-alpha12 以来,我们在发布时遇到了类似的崩溃.将脱糖库更新到版本 1.1.5 后,崩溃消失了.

      We had similar crashes in release since AGP 7.0.0-alpha12. The crashes are gone after updating the desugaring library to version 1.1.5.

      dependencies {
          coreLibraryDesugaring 'com.android.tools:desugar_jdk_libs:1.1.5'
      }
      

      更多信息:https://issuetracker.google.com/issues/189244205

      这篇关于使用 minifyEnabled true 启动应用程序时 FirebaseInitProvider.onCreate 中的 java.lang.IncompatibleClassChangeError的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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