致命异常:Firebase-Messaging-Intent-Handle -- java.lang.NoClassDefFoundError [英] FATAL EXCEPTION: Firebase-Messaging-Intent-Handle -- java.lang.NoClassDefFoundError

问题描述

我没有在我的项目中使用任何 Firebase 或 Youtube 代码/库.然而最近，在 Android Pre-Release Reports 中，我看到了这样的崩溃:

I am not using any Firebase or Youtube code/libraries in my project. Yet recently, in Android Pre-Release Reports I am seeing crashes with this:

FATAL EXCEPTION: Firebase-Messaging-Intent-Handle
Process: com.google.android.youtube, PID: 26820
java.lang.NoClassDefFoundError: aewt
    at aewu.b(PG:1)
    at duc.a(PG:230)
    at duc.get(PG:247)
    at aevw.b(PG:1)
    at dud.al(PG:5)
    at dud.aw(PG:4)
    at dud.bg(PG:8)
    at duc.a(PG:232)
    at duc.get(PG:247)
    at afke.a(PG:1)
    at aeri.b(PG:1)
    at dud.fv(PG:4)
    at duc.c(PG:269)
    at duc.get(PG:247)
    at amfk.a(PG:1)
    at eiu.K(PG:5)
    at dud.fV(PG:7)
    at duc.d(PG:334)
    at duc.get(PG:247)
    at com.google.android.apps.youtube.app.common.notification.FcmMessageListenerService.b(PG:1)
    at com.google.firebase.messaging.FirebaseMessagingService.g(PG:53)
    at avgp.run(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
    at usj.run(PG:2)
    at java.lang.Thread.run(Thread.java:831)

这是另一个日志，其中包含更多详细信息，但存在不同的问题:

Here's another log with more detail, but different problems:

Process: com.google.android.youtube, PID: 16751
java.lang.NoClassDefFoundError: aewt
    
    [redacted]

    at com.google.android.apps.youtube.app.common.notification.FcmMessageListenerService.b(PG:1)
    at com.google.firebase.messaging.FirebaseMessagingService.g(PG:53)
    at avgp.run(Unknown Source:7)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
    at usj.run(PG:2)
    at java.lang.Thread.run(Thread.java:764)
Caused by: java.lang.ExceptionInInitializerError
    
    [redacted]

    at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1119)
    at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5767)
    at android.app.ActivityThread.-wrap1(Unknown Source:0)
    at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1680)
    at android.os.Handler.dispatchMessage(Handler.java:106)
    at android.os.Looper.loop(Looper.java:164)
    at android.app.ActivityThread.main(ActivityThread.java:6523)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:857)
Caused by: dkp: libelements.so
    at dks.c(PG:52)
    ...

有什么想法吗?

我不知道什么dkp: libelements.so"是.谷歌搜索没有结果.

I have no idea what dkp: libelements.so" is. Googling shows no results.

我将 minifyEnabled 和 shr​​inkResources 都设置为 false 的版本上传到 Google Play，但在预发布中出现 Firebase/Youtube 错误报告仍然模糊不清.而且它只影响两款设备:诺基亚1和华为P8青春版.

I uploaded a version to Google Play with minifyEnabled and shrinkResources both set to false, yet the Firebase/Youtube errors in Pre-Launch Reports are still obfuscated. And it only affects two devices: Nokia 1 and Huawei P8 青春版.

当我将未经混淆的文件上传到 Google Play 时，有人警告我说我的应用包含经过混淆的代码，我应该上传地图文件.我不知道 Firebase/Youtube 代码在我的二进制文件中的位置，查看我的提交，在错误开始出现的时间前后，我的任何库都没有更新.

When I uploaded the unobfuscated file to Google Play, I was warned that my app contained obfuscated code and that I should upload a map file. I have no idea how the Firebase/Youtube code is in my binary, and looking through my commits there have been no updates to any of my libraries around the time the errors started showing up.

更新:再次标记为已修复:
https://issuetracker.google.com/issues/160907013#comment256

推荐答案

解决方案:忽略

所有迹象都表明这是 Google Play 发布前报告的问题，而不是我们的代码.

All signs point to this being a problem with Google Play's Pre-launch Reports and not our code.

Google 的产品和工程团队现已意识到这个问题.但似乎他们可能需要更多的人来让他们了解问题的严重程度.或许可以考虑在错误报告上发帖.

Google's product and engineering teams are now aware of the issue. But it seems they might need a few more people to give them a sense of the scale of the issue. Perhaps consider posting on the bug report.

更新:谷歌现在通过为该过程添加过滤器来修复它.请参阅关于错误报告的评论 256.

Update: Google have fixed it now by adding a filter for the process. See comment 256 on the bug report.

我已经上传了我的应用程序的几个版本，现在问题消失了.

I have uploaded a few versions of my app and the problem is now gone.

这篇关于致命异常:Firebase-Messaging-Intent-Handle -- java.lang.NoClassDefFoundError的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！