FATAL EXCEPTION: Firebase-Messaging-Intent-Handle -- java.lang.NoClassDefFoundError

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)
	...

Any ideas please?

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

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 青春版.

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.

UPDATE: Marked as fixed again:
https://issuetracker.google.com/issues/160907013#comment256

Solution: ignore

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

Edit: 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.

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.

I also have the same problem when trying to publish a new version of my application also developed in java with android studio, in the pre launch an error is shown for the Huawei P8 青春 版 device with Android 5.0 (SDK 21). The error is as follows:

FATAL EXCEPTION: Firebase-Messaging-Intent-Handle
Process: com.google.android.youtube, PID: 27648
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)

But when downloading the full log I find that the error appears before the application starts:

11-08 06:57:29.438: E/AndroidRuntime(27648): FATAL EXCEPTION: Firebase-Messaging-Intent-Handle
11-08 06:57:29.438: E/AndroidRuntime(27648): Process: com.google.android.youtube, PID: 27648
11-08 06:57:29.438: E/AndroidRuntime(27648): java.lang.NoClassDefFoundError: aewt
...

But in the video that google makes for the test the application never fails and you can clearly see that it starts at 06:57:07, so the times don't match.

1-08 06:59:07.758: W/PGApi_client(3556): recv actoionId = 10000, action = com.huawei.pgmng.PGAction@13714f2a actionId =10000 pkg =com.MYAPP.MYAPP extend1 =0 extend2 = flag =3 type =1
11-08 06:59:07.758: W/PGMiddleWare jhh(3556): in handleAction method, action = 10000
11-08 06:59:07.758: W/PGMiddleWare jhh(3556): in handleAction, invoke client = com.huawei.pgmng.middleware.AudioEffectLowPowerImpl@2725ca70, action = com.huawei.pgmng.PGAction@13714f2a actionId =10000 pkg =com.MYAPP.MYAPP extend1 =0 extend2 = flag =3 type =1
11-08 06:59:07.758: I/AudioEffectLowPowerImpl jhh(3556): jhh handle default mActionId = 10000, action = com.huawei.pgmng.PGAction@13714f2a actionId =10000 pkg =com.MYAPP.MYAPP extend1 =0 extend2 = flag =3 type =1
11-08 06:59:07.758: W/AudioEffectLowPowerImpl jhh(3556): enter into DEFAULT_FRONT Scene.

Check the registry in detail, if it is the same case we can only wait for google to fix the problem on their test devices or publish the application and that some user with that device has the same error.

For me, this was happening because I deleted a class, but forgot to remove a reference to it in AndroidManifest.xml.

Go through your AndroidManifest.xml and make sure it doesn't reference any non-existent classes, they will likely show as red, but surprisingly the project will still build.

The name is likely showing as aewt because of build minification / obfuscation. I have absolutely no idea why the error message references youtube, it does for me too when I don't use youtube in the app.

The crash log in the pre-release report was totally useless, but a crash log in firebase crashlytics revealed the source of the issue.

I'm still waiting for a pre-release report to undoubtedly confirm, which I'll have later today, but it seems highly likely based on the firebase crashlytics report and the circumstances.

Edit: My pre-release report is no longer showing this error and is totally passing after removing the hanging reference from the androidmanifest.xml

I had the same problem and this problem is caused on specific devices (Nokia Nokia 1 and Huawei P8), the problems is a bug from Google pre-launch test lab, if this problems were this unique that showed to you, you just need ignore really, this problem appear more or less three months, Google will resolve it, we do not just know when...

Removing Nokia 1 from supported device list should help

I think the issue is not related to Firebase library because this problem occurs to many users who are not using Firebase library, after several days trying to understand this issue I think this issue is related to google play service app update method (app bundle). Why do I think the problem is in the google play service? because this problem occurs to users starting around 11/1/2020, I think on this date google update google play service and the problem starts from here, there is another reason for me, when I do some change in a certain place in my code and I republish the app in playstore the problem suddenly disappears and when I republish it the problem appears again. For all these reasons, I think the problem is in the google play service.

-Removing an unnecessary reference from the Manifest file temporarily fixes the problem, but if you try to republish your app, the problem reappears again!

For me it was because the title and message was an empty string.

I had this issue after updating to firebase latest SDK. The issue was, I hadn't remove the reference of a service which was previously removed from app.

• check your manifest and remove unnecessary references which will be shown by red color.

By doing that, I was able to remove this error from prelaunch report.