The Build is success. And then I upload to Google Play Console, In Test report , there are two devices has report the error.
On device Huawei P8 ้ๆฅ็:
FATAL EXCEPTION: Firebase-Messaging-Intent-Handle
Process: com.google.android.youtube, PID: 25323
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)
On device Nokia Nokia 1:
FATAL EXCEPTION: Firebase-Messaging-Intent-Handle
Process: com.google.android.youtube, PID: 16634
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: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
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 duc.a(PG:174)
at duc.get(PG:247)
at aeqv.a(PG:6)
at acpw.b(PG:2)
at dxe.a(PG:8)
at dus.onCreate(PG:41)
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)
at dkq.a(PG:6)
at duv.a(Unknown Source:8)
at avlz.f(PG:8)
at avlz.e(PG:5)
at avlz.a(PG:1)
at wqq.a(PG:1)
at aewt.
... 21 more
If i do not use the follow code , only Huawei P8 ้ๆฅ็ get error.
[RuntimeInitializeOnLoadMethod(RuntimeInitializeLoadType.AfterSceneLoad)]
private static void InitFirebase()
{
Firebase.FirebaseApp.CheckAndFixDependenciesAsync().ContinueWith(task =>
{
var dependencyStatus = task.Result;
if (dependencyStatus == Firebase.DependencyStatus.Available)
{
Firebase.Analytics.FirebaseAnalytics.SetAnalyticsCollectionEnabled(true);
}
else
{
string error = System.String.Format(
"Could not resolve all Firebase dependencies: {0}", dependencyStatus);
Log.Write(error);
// Firebase Unity SDK is not safe to use here.
}
});
}
// TODO(you): code here to reproduce the problem
[logcat_HuaweiP8.txt](https://github.com/firebase/quickstart-unity/files/5506148/logcat_HuaweiP8.txt)
[logcat_NokiaNokia1.txt](https://github.com/firebase/quickstart-unity/files/5506149/logcat_NokiaNokia1.txt)
People are getting this same problem with the Nokia 1 and Huawei P8 ้ๆฅ็, without using any Firebase libraries. Please see:
https://stackoverflow.com/questions/64706041/fatal-exception-firebase-messaging-intent-handle-java-lang-noclassdeffounder
We are experiencing this issue and cannot upgrade the application on Playstore...
Same issuer .... and I cant Resume Track on Open Testing
We also have the same issue with Huawei P8 ้ๆฅ็ and Nokia Nokia 1. From the Play Console pre-launch video, it appears that the crash happens randomly without any input from the user.
We are confused with the Process name which states this for each of the crash:
Process: com.google.android.youtube
This is not our process/app. Why is it causing our App to crash?
Any suggestions/work arounds?
Below are the stack traces (which are slightly different through)
Huawei P8 ้ๆฅ็:
FATAL EXCEPTION: Firebase-Messaging-Intent-Handle
Process: com.google.android.youtube, PID: 28021
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)
Nokia Nokia 1:
FATAL EXCEPTION: Firebase-Messaging-Intent-Handle
Process: com.google.android.youtube, PID: 16465
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: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
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 duc.a(PG:174)
at duc.get(PG:247)
at aeqv.a(PG:6)
at acpw.b(PG:2)
at dxe.a(PG:8)
at dus.onCreate(PG:41)
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)
at dkq.a(PG:6)
at duv.a(Unknown Source:8)
at avlz.f(PG:8)
at avlz.e(PG:5)
at avlz.a(PG:1)
at wqq.a(PG:1)
at aewt.
... 21 more
I face the same problem!
Does anybody have a workaround?
Ran into the same problem:
Huawei P8 ้ๆฅ็, 720x1280, Android 5.0 (SDK 21), 2,048 MB, ARM64_V8, en_US
java.lang.NoClassDefFoundError: aewt
FATAL EXCEPTION: Firebase-Messaging-Intent-Handle
Process: com.google.android.youtube, PID: 25984
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)
I face the same problem!
Does anybody have a workaround?
As a temporary solution we increased the minimum SDK version to 22 to force skipping the faulty devices.
Yep, same problem here! Nokia Nokia 1
480x854
Android 8.1 (SDK 27)
FATAL EXCEPTION: Firebase-Messaging-Intent-Handle
Process: com.google.android.youtube, PID: 16483
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: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
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 duc.a(PG:174)
at duc.get(PG:247)
at aeqv.a(PG:6)
at acpw.b(PG:2)
at dxe.a(PG:8)
at dus.onCreate(PG:41)
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)
at dkq.a(PG:6)
at duv.a(Unknown Source:8)
at avlz.f(PG:8)
at avlz.e(PG:5)
at avlz.a(PG:1)
at wqq.a(PG:1)
at aewt.
... 21 more
I face the same problem!
Does anybody have a workaround?As a temporary solution we increased the minimum SDK version to 22 to force skipping the faulty devices.
Thank you, but the error appears at Huawei P8 (SDK21), bu also Nokia 1 (SDK27), so I don't think the minimum SDK 22 will fix this.
What Target API Level did you use?

Same issuer.
Huawei P8 ้ๆฅ็
720x1280
Android 5.0 (SDK 21)
2,048 MB
ARM64_V8
en_US

Similar prelaunch errors referring to youtube and firebase messaging for my app as well. (The app doesn't even require internet permission to work!?)
ๅ ๆ ่ฝจ่ฟน
java.lang.NoClassDefFoundError: aewt
FATAL EXCEPTION: Firebase-Messaging-Intent-Handle
Process: com.google.android.youtube, PID: 28016
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)
ๆต่ฏๆ้ดๅจ 1 ๅฐ่ฎพๅคไธๆฃๆตๅฐๆญค้ฎ้ข
Huawei P8 ้ๆฅ็
720x1280
Android 5.0 (SDK 21)
2,048 MB
ARM64_V8
vi_VN
We have the same problem. Has anyone solved it?
And it seems to me, that that problem is kinda breaking whole pre-launch report. Normally it takes about hour and has 11-12 devices. But today it was only 4 and that buggy Nokia 1 was last. Nasty.
I face the same problem!
Does anybody have a workaround?As a temporary solution we increased the minimum SDK version to 22 to force skipping the faulty devices.
Thank you, but the error appears at Huawei P8 (SDK21), bu also Nokia 1 (SDK27), so I don't think the minimum SDK 22 will fix this.
What Target API Level did you use?
The target version is 29.
It fixed for us.
We noticed that is not always crashing on Nokia 1 so this was the reason why increased the minimum version.

We also updated all of the plugins and libraries to the latest versions.
Same here, for Nokia and Huawai(We don't support this devices anyway). In this release I updated target and compile sdk to 29? May be this can the reason for failure?
Same here, for Nokia and Huawai(We don't support this devices anyway). In this release I updated target and compile sdk to 29? May be this can the reason for failure?
@lisichka999 We have updated target and compile SDK to 29 in the last release haven't faced the issue
So I ran a custom test on both Nokia 1 and Huawei p8 in the firebase test lab.
I am enclosing the portions of logcat wherever this error is referenced(~21 times).
I hope someone would be able to make some sense out of it.
Please have a look at these.
nokia 1 logcat prelaunch report crash.txt
huawei p8 logcat prelaunch report crash.txt
It is funny because I got this bug when I had support for Android 5.0 (Nokia and Huawei got this error)
When change minimum SDK wersion to 23 this problem not reproduce.
But when I was upload new version of application this problem come back on Android 8.1 (Nokia)...
(But the way - I don't use Firebase library)
Hope google solve that issue
Hi all, sorry that you are experiencing this issue and we are looking into what's going on and how to fix this. Please stay tuned.
facing same issue
New situation with new version app:
I have targetSDK on 30 and compileSDK on 30 and consoles don't show me error about it
It's really strange
Same problem, Nokia Nokia 1 and Huawei P8 ้ๆฅ็ devices
FATAL EXCEPTION: Firebase-Messaging-Intent-Handle
Process: com.google.android.youtube, PID: 16323
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: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
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 duc.a(PG:174)
at duc.get(PG:247)
at aeqv.a(PG:6)
at acpw.b(PG:2)
at dxe.a(PG:8)
at dus.onCreate(PG:41)
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)
at dkq.a(PG:6)
at duv.a(Unknown Source:8)
at avlz.f(PG:8)
at avlz.e(PG:5)
at avlz.a(PG:1)
at wqq.a(PG:1)
at aewt.<clinit>(PG:1)
... 21 more
This issue has nothing to do with Unity. Others not using Unity are having the exact same issue. It's a problem in the Pre-Launch Reports and is not related to your code.
How did you figure out I am using unity when I use libgdx? And I have received the message through pre launch report.
I can confirm that it's not related with Unity. I'm having the same issue and my app is just React Native, we use Firebase SDK for Analytics, Auth and Firestore.
Actually, has anyone tried this approach? I didn't yet, but seems promising.
Same problem: Huawei P8 ้ๆฅ็
FATAL EXCEPTION: Firebase-Messaging-Intent-Handle
Process: com.google.android.youtube, PID: 26355
java.lang.NoClassDefFoundError: aewt
(Using LibGDX also)
I received the same error on Google Play Console Pre-launch report.
I have fixed it by adding to module build.gradle file:
...
dependencies {
...
def multidex_version = "2.0.1"
implementation 'androidx.multidex:multidex:$multidex_version'
...
}
...
How did you figure out I am using unity when I use libgdx? And I have received the message through pre launch report.
I can confirm that it's not related with Unity. I'm having the same issue and my app is just React Native, we use Firebase SDK for Analytics, Auth and Firestore.
Actually, has anyone tried this approach? I didn't yet, but seems promising.
I tried that, but for me is still reproducible. Nevertheless, it created a new instability error.
I received the same error on Google Play Console Pre-launch report.
I have fixed it by adding to module build.gradle file:
...
dependencies {
...
def multidex_version = "2.0.1"
implementation 'androidx.multidex:multidex:$multidex_version'
...
}
...
Just tested it, and for me is still reproducible.
I received the same error on Google Play Console Pre-launch report.
I have fixed it by adding to module build.gradle file:
...
dependencies {
...
def multidex_version = "2.0.1"
implementation 'androidx.multidex:multidex:$multidex_version'
...
}
...Just tested it, and for me is still reproducible.
Same here, tested this suggestion but no improvements in my case... :-/
multidex isn't relevant for Android 5.0 (API 21) onwards. Please see:
https://developer.android.com/studio/build/multidex
I got the same issue on pre-launch report
FATAL EXCEPTION: Firebase-Messaging-Intent-Handle
Process: com.google.android.youtube, PID: 28331
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)
Google accepted my app with this error. It wen't live. So it may be something on their side. If I get some more explicit logs in production I will let you know.
Is it safe just ignore it?
Same error, but I'm wondering how come the crash is from youtube and affect the test?
Process: com.google.android.youtube, PID: 26795
Hello @cynthiajoan, do you have any updates about what's causing the issue? Thank you. Cheers
Chiming in: we just had the same error on an app that runs on our in-house C++ engine. Can confirm it's not Unity. Will try rolling our nonetheless.
Google accepted my app with this error. It wen't live. So it may be something on their side. If I get some more explicit logs in production I will let you know.
My app is now also live so I'd say safe to ignore it.
I received the same error on Google Play Console Pre-launch report.
I have fixed it by adding to module build.gradle file:
...
dependencies {
...
def multidex_version = "2.0.1"
implementation 'androidx.multidex:multidex:$multidex_version'
...
}
...
Tried this, now the prelaunch report updated and got crash only on Huawei device Nokia passed the test
Weird
24 hours in review now due to this error
The Nokia 1 is no longer having this error. I've changed nothing that would affect this. The Huawei is still having the error though. Nothing to do with multiDex since that is already supported since Android 5.0.
same problem, hope this will be fixed soon
Are you all getting this crash after updating Firebase dependencies?
Are you all getting this crash after updating Firebase dependencies?
I'm not even using Firebase in my project and still have this problem
same problem with flutter app
I am also facing the same issue in our flutter application. Any workarounds for this ?
Same issue for me on an Xamarin Android app targeting Android 11.
FATAL EXCEPTION: Firebase-Messaging-Intent-Handle
Process: com.google.android.youtube, PID: 16231
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: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
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 duc.a(PG:174)
at duc.get(PG:247)
at aeqv.a(PG:6)
at acpw.b(PG:2)
at dxe.a(PG:8)
at dus.onCreate(PG:41)
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)
at dkq.a(PG:6)
at duv.a(Unknown Source:8)
at avlz.f(PG:8)
at avlz.e(PG:5)
at avlz.a(PG:1)
at wqq.a(PG:1)
at aewt.<clinit>(PG:1)
... 21 more
Issue first time appeared on Nov. 7th 2020 on Pre-Launch Nokia 1 device.
I face the same problem!
Does anybody have a workaround?As a temporary solution we increased the minimum SDK version to 22 to force skipping the faulty devices.
We are at min SDK of 26 and still get the issue.
I face the same problem!
Does anybody have a workaround?As a temporary solution we increased the minimum SDK version to 22 to force skipping the faulty devices.
We are at min SDK of 26 and still get the issue.
Same issuer but SDK 27

Is this error that this version is not published in the Play Store (beta)?
Identical problem. Made in Unity
According to Stackoverflow thread this might be related to AndroidManifest.xml having references to non-existing activities or other class references.
For me I strongly suggest Facebook SDK is the underlying cause for this after having removed App Invite at some point leaving my AndroidManifest.xml file with now deprecated reference to com.facebook.unity.AppInviteDialogActivity
Check you AndroidManifest and see if you are referencing some non-existing classes.
According to Stackoverflow thread this might be related to AndroidManifest.xml having references to non-existing activities or other class references.
For me I strongly suggest Facebook SDK is the underlying cause for this after having removed App Invite at some point leaving my AndroidManifest.xml file with now deprecated reference to com.facebook.unity.AppInviteDialogActivityCheck you AndroidManifest and see if you are referencing some non-existing classes.
We have no changes in the Android Manifest, for sure no references to non existing classes and we are also not using the Facebook SDK.
The issue started on our November 7th built but afterwards some builds have the issue, some don't. Only on Nokia 1 Pre-Launch device.
My app with zero external dependencies is getting this crash.
This is error not specific to any SDK, framework, or game engine you folks are using.
I also got this error in Pre-Launch report.
11-19 12:38:47.661: I/GAv4-SVC(16829): Google Analytics 203.9.15 is starting up.
11-19 12:38:47.689: E/YouTube(16716): Failed to construct CronetEngine using CronetProvider: App-Packaged-Cronet-Provider, 87.0.4276.2
11-19 12:38:47.689: E/YouTube(16716): java.lang.UnsatisfiedLinkError: Cannot find or unzip library: libcronet.87.0.4276.2.so; Failed to unzip from ABIs: [armeabi-v7a, armeabi]; Did not find lib/armeabi-v7a/libcronet.87.0.4276.2.so in /data/app/com.google.android.youtube-ZQc13bKuehzBe6sDrz1VsQ==/base.apk, Did not find lib/armeabi/libcronet.87.0.4276.2.so in /data/app/com.google.android.youtube-ZQc13bKuehzBe6sDrz1VsQ==/base.apk
11-19 12:38:47.689: E/YouTube(16716): at adsb.a(PG:58)
11-19 12:38:47.689: E/YouTube(16716): at adaw.loadLibrary(PG:1)
11-19 12:38:47.689: E/YouTube(16716): at bofi.loadLibrary(PG:1)
11-19 12:38:47.689: E/YouTube(16716): at org.chromium.net.impl.CronetLibraryLoader.a(PG:6)
11-19 12:38:47.689: E/YouTube(16716): at org.chromium.net.impl.CronetUrlRequestContext.<init>(PG:6)
11-19 12:38:47.689: E/YouTube(16716): at boew.build(PG:2)
11-19 12:38:47.689: E/YouTube(16716): at org.chromium.net.ExperimentalCronetEngine$Builder.build(PG:1)
11-19 12:38:47.689: E/YouTube(16716): at adav.a(Unknown Source:262)
11-19 12:38:47.689: E/YouTube(16716): at adaq.a(PG:10)
11-19 12:38:47.689: E/YouTube(16716): at adax.get(Unknown Source:50)
11-19 12:38:47.689: E/YouTube(16716): at blwu.get(PG:1)
11-19 12:38:47.689: E/YouTube(16716): at blwt.get(PG:2)
11-19 12:38:47.689: E/YouTube(16716): at eio.Y(PG:1)
11-19 12:38:47.689: E/YouTube(16716): at dud.p(PG:1)
11-19 12:38:47.689: E/YouTube(16716): at duc.a(PG:338)
11-19 12:38:47.689: E/YouTube(16716): at duc.get(PG:247)
11-19 12:38:47.689: E/YouTube(16716): at adbk.run(Unknown Source:2)
11-19 12:38:47.689: E/YouTube(16716): at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:457)
11-19 12:38:47.689: E/YouTube(16716): at java.util.concurrent.FutureTask.run(FutureTask.java:266)
11-19 12:38:47.689: E/YouTube(16716): at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:301)
11-19 12:38:47.689: E/YouTube(16716): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
11-19 12:38:47.689: E/YouTube(16716): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
11-19 12:38:47.689: E/YouTube(16716): at acto.run(PG:12)
11-19 12:38:47.689: E/YouTube(16716): at java.lang.Thread.run(Thread.java:764)
11-19 12:38:47.689: E/YouTube(16716): Caused by: java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/com.google.android.youtube-ZQc13bKuehzBe6sDrz1VsQ==/base.apk"],nativeLibraryDirectories=[/data/app/com.google.android.youtube-ZQc13bKuehzBe6sDrz1VsQ==/lib/arm, /system/lib, /vendor/lib]]] couldn't find "libcronet.87.0.4276.2.so"
11-19 12:38:47.689: E/YouTube(16716): at java.lang.Runtime.loadLibrary0(Runtime.java:1011)
11-19 12:38:47.689: E/YouTube(16716): at java.lang.System.loadLibrary(System.java:1657)
11-19 12:38:47.689: E/YouTube(16716): at adsb.a(PG:1)
11-19 12:38:47.689: E/YouTube(16716): ... 23 more
11-19 12:38:47.835: I/Telecom(729): DefaultDialerCache: Refreshing default dialer for user 0: now com.google.android.dialer: DDC.oR@AOQ
11-19 12:38:47.852: W/zygote(16716): Skipping duplicate class check due to unsupported classloader
11-19 12:38:47.861: W/VoiceInteractionManagerService(729): no available voice interaction services found for user 0
11-19 12:38:47.886: I/LauncherAppsCompatVL(1718): onPackageChanged, packageName:com.google.android.music
11-19 12:38:48.027: I/DynamiteModule(16716): Considering local module com.google.android.gms.ads.dynamite:0 and remote module com.google.android.gms.ads.dynamite:21800
11-19 12:38:48.068: I/DynamiteModule(16716): Selected remote version of com.google.android.gms.ads.dynamite, version >= 21800
11-19 12:38:48.148: I/app_process(16857): The ClassLoaderContext is a special shared library.
11-19 12:38:48.319: I/DynamiteModule(16829): Considering local module com.google.android.gms.googlecertificates:6 and remote module com.google.android.gms.googlecertificates:6
11-19 12:38:48.321: I/DynamiteModule(16829): Selected local version of com.google.android.gms.googlecertificates
11-19 12:38:48.338: E/PowerHalWrapper(729): <setInstallationBoost> enable:true
11-19 12:38:48.388: I/app_process(16857): System.exit called, status: 0
11-19 12:38:48.388: I/AndroidRuntime(16857): VM exiting with result code 0.
11-19 12:38:48.459: I/SuperDelight(15777): SuperDelightDownloadSlicingStrategy.getSlices():230 DownloadSlicing#getSlices(): result {slices=[{delight:main_ru_ru_2020081300_1, m:*, fg}, {delight:main_en_gb_2020082400_1, m:*, fg}], last batch=true, sync metadata=false}
11-19 12:38:48.479: I/SP(15777): Syncing delight (2020110900) with slices: [{main_ru_ru_2020081300_1, m:*, fg}, {main_en_gb_2020082400_1, m:*, fg}], metadata: false
11-19 12:38:48.496: I/ADB_SERVICES(326): post waitpid (pid=16857) status=0000
11-19 12:38:48.525: I/ADB_SERVICES(326): service_to_fd shell:pm install-write 1037880736 2_io_sundeep_android__ /data/local/tmp/io.sundeep.android.2.apk
11-19 12:38:48.540: I/WifiService(729): getConnectionInfo uid=10047
11-19 12:38:48.758: I/ActivityManager(729): Start proc 16952:android.process.acore/u0a37 for content provider com.android.providers.contacts/.ContactsProvider2
11-19 12:38:48.758: W/ActivityManager(729): Slow operation: 51ms so far, now at startProcess: starting to update pids map
11-19 12:38:48.758: W/ActivityManager(729): Slow operation: 51ms so far, now at startProcess: done updating pids map
11-19 12:38:48.758: W/ActivityManager(729): Slow operation: 52ms so far, now at startProcess: done starting proc!
11-19 12:38:48.759: W/ActivityManager(729): Slow operation: 53ms so far, now at getContentProviderImpl: after start process
11-19 12:38:48.759: W/ActivityManager(729): Slow operation: 53ms so far, now at getContentProviderImpl: updating data structures
11-19 12:38:48.759: W/ActivityManager(729): Slow operation: 54ms so far, now at getContentProviderImpl: done!
11-19 12:38:48.561: I/WifiService(729): getConnectionInfo uid=10047
11-19 12:38:48.789: W/ProviderHelper(16751): Unknown dynamite feature providerinstaller
11-19 12:38:48.796: I/DynamiteModule(16751): Considering local module com.google.android.gms.providerinstaller:1 and remote module com.google.android.gms.providerinstaller:0
11-19 12:38:48.796: I/DynamiteModule(16751): Selected local version of com.google.android.gms.providerinstaller
11-19 12:38:48.871: I/SP.FP(15777): Fetched file delight:main_ru_ru_2020081300_1.fst-decompress.fetched is found with 2670592 bytes, expected: 6944716, will resume fetching with partial file.
11-19 12:38:48.876: I/qtaguid(16751): Tagging socket -1 with tag 3000040700000000(805307399) for uid -1 failed errno=-9
11-19 12:38:48.876: I/NetworkManagementSocketTagger(16751): tagSocketFd(-1, 805307399, -1) failed with errno-9
11-19 12:38:48.901: W/System(16751): ClassLoader referenced unknown path: system/framework/mediatek-cta.jar
11-19 12:38:48.912: I/System.out(16751): e:java.lang.ClassNotFoundException: com.mediatek.cta.CtaHttp
11-19 12:38:48.939: I/zygote(16952): The ClassLoaderContext is a special shared library.
11-19 12:38:48.953: I/zygote(16952): The ClassLoaderContext is a special shared library.
11-19 12:38:49.015: I/BufferQueueProducer(309): [com.google.android.apps.mtaas.backdrop/com.google.android.apps.mtaas.backdrop.BackdropActivity#0](this:0xa592d000,id:19,api:1,p:15843,c:309) queueBuffer: fps=1.00 dur=1990.12 max=996.33 min=993.79
11-19 12:38:49.022: I/DisplayDevice(309): [Built-in Screen (type:0)] fps:1.007669,dur:1984.78,max:992.49,min:992.29
11-19 12:38:49.109: I/SP(15777): Scheduling: download registered, 0 started, 0 paused, 0 scheduled, 3 pending: delight:main_en_gb_2020082400_1 @ {m:b, fg}, emoji:480abc59ea0f463d5c82d29756d0d5e1 {m:b, bg}, delight:main_ru_ru_2020081300_1 @ {m:b, fg}
11-19 12:38:49.196: I/zygote(16751): Background concurrent copying GC freed 34652(2MB) AllocSpace objects, 28(776KB) LOS objects, 49% free, 3MB/7MB, paused 828us total 587.535ms
11-19 12:38:49.214: I/SP(15777): Scheduling: download registered, 0 started, 0 paused, 0 scheduled, 3 pending: emoji:480abc59ea0f463d5c82d29756d0d5e1 {m:b, bg}, delight:main_ru_ru_2020081300_1 @ {m:b, fg}, delight:main_en_gb_2020082400_1 @ {m:b, fg}
11-19 12:38:49.219: I/[email protected](286): querySysInfo cmd:6, param:0
11-19 12:38:49.220: I/powerd(286): [powerd_req] POWER_MSG_QUERY_INFO: cmd:6, param:0
11-19 12:38:49.220: I/libPerfService(286): perfUserGetCapability - cmd:6, id:0, value:15843
11-19 12:38:49.230: I/SP(15777): GC for 'delight' (10) with ttl of 0 ms took 1 ms (0/1/0)
11-19 12:38:49.244: W/mtkmal(317): type=1400 audit(0.0:395): avc: denied { open } for path="/proc/317/net/dev" dev="proc" ino=4026533568 scontext=u:r:mtkmal:s0 tcontext=u:object_r:proc_net:s0 tclass=file permissive=0
11-19 12:38:49.253: I/AbstractSyncResultCallback(15777): AbstractSyncResultCallback.onFailure():36 onFailure(): delight.sync cancelled; expected if new request supersedes pending one.
11-19 12:38:49.253: I/AbstractSyncResultCallback(15777): AbstractSyncResultCallback.onFailure():36 onFailure(): delight.sync cancelled; expected if new request supersedes pending one.
11-19 12:38:49.347: I/ContactsPerf(16952): VoicemailContentProvider.onCreate start
11-19 12:38:49.381: I/ContactsPerf(16952): VoicemailContentProvider.onCreate finish
11-19 12:38:49.396: I/zygote(16829): Waiting for a blocking GC ProfileSaver
11-19 12:38:49.395: I/zygote(16716): The ClassLoaderContext is a special shared library.
11-19 12:38:49.424: I/zygote(16952): The ClassLoaderContext is a special shared library.
11-19 12:38:49.483: I/SignalClusterView(1042): updateDisplayVoLte mShowVoLteIcon: false mNoSimsVisible: true mIsAirplaneMode: false showWfc: false showVolte: false
11-19 12:38:49.484: I/SignalClusterView(1042): updateDisplayVoLte mShowVoLteIcon: false mNoSimsVisible: true mIsAirplaneMode: false showWfc: false showVolte: false
11-19 12:38:49.487: I/zygote(16829): WaitForGcToComplete blocked ProfileSaver on HeapTrim for 91.190ms
11-19 12:38:49.498: I/zygote(16952): The ClassLoaderContext is a special shared library.
11-19 12:38:49.507: I/zygote(16829): WaitForGcToComplete blocked CollectorTransition on ProfileSaver for 14.361ms
11-19 12:38:49.524: I/WifiService(729): getConnectionInfo uid=10047
11-19 12:38:49.609: I/zygote(16716): Rejecting re-init on previously-failed class java.lang.Class<aewt>: java.lang.ExceptionInInitializerError:
11-19 12:38:49.609: I/zygote(16716): at aewt aewu.b(altt, acwg, bnsx, afbc, java.util.Map, java.util.concurrent.Executor) (PG:1)
11-19 12:38:49.609: I/zygote(16716): at java.lang.Object duc.a() (PG:230)
11-19 12:38:49.609: I/zygote(16716): at java.lang.Object duc.get() (PG:247)
11-19 12:38:49.609: I/zygote(16716): at afaa aevw.b(bnsx) (PG:1)
11-19 12:38:49.609: I/zygote(16716): at afaa dud.al() (PG:5)
11-19 12:38:49.609: I/zygote(16716): at java.lang.Object duc.a() (PG:174)
11-19 12:38:49.609: I/zygote(16716): at java.lang.Object duc.get() (PG:247)
11-19 12:38:49.609: I/zygote(16716): at void aeqv.a() (PG:6)
11-19 12:38:49.609: I/zygote(16716): at void acpw.b() (PG:2)
11-19 12:38:49.609: I/zygote(16716): at void dxe.a(egv) (PG:8)
11-19 12:38:49.609: I/zygote(16716): at void dus.onCreate() (PG:41)
11-19 12:38:49.609: I/zygote(16716): at void android.app.Instrumentation.callApplicationOnCreate(android.app.Application) (Instrumentation.java:1119)
11-19 12:38:49.609: I/zygote(16716): at void android.app.ActivityThread.handleBindApplication(android.app.ActivityThread$AppBindData) (ActivityThread.java:5767)
11-19 12:38:49.609: I/zygote(16716): at void android.app.ActivityThread.-wrap1(android.app.ActivityThread, android.app.ActivityThread$AppBindData) (ActivityThread.java:-1)
11-19 12:38:49.609: I/zygote(16716): at void android.app.ActivityThread$H.handleMessage(android.os.Message) (ActivityThread.java:1680)
11-19 12:38:49.609: I/zygote(16716): at void android.os.Handler.dispatchMessage(android.os.Message) (Handler.java:106)
11-19 12:38:49.609: I/zygote(16716): at void android.os.Looper.loop() (Looper.java:164)
11-19 12:38:49.609: I/zygote(16716): at void android.app.ActivityThread.main(java.lang.String[]) (ActivityThread.java:6523)
11-19 12:38:49.609: I/zygote(16716): at java.lang.Object java.lang.reflect.Method.invoke(java.lang.Object, java.lang.Object[]) (Method.java:-2)
11-19 12:38:49.609: I/zygote(16716): at void com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run() (RuntimeInit.java:438)
11-19 12:38:49.609: I/zygote(16716): at void com.android.internal.os.ZygoteInit.main(java.lang.String[]) (ZygoteInit.java:857)
11-19 12:38:49.616: I/PeopleSearchIndexManage(16829): Index version changed from 0
11-19 12:38:49.696: I/PeopleSearchIndexManage(16829): Rebuilding index...
11-19 12:38:49.799: I/System.out(16716): checkUrl: https://youtubei.googleapis.com/generate_204
This line above Rejecting re-init on previously-failed class java.lang.Class<aewt>: java.lang.ExceptionInInitializerError: is causing the error. Sorry had to give all logs above. I guess if you have a YouTube API dependency (debatable), you might get this error. Saw on a Nokia one device. This app is the issue -> com.google.android.youtube (which is the official youtube app)
Hi @all
Sorry it takes a while for me to give update. Here's what I'd like to share with the status:
I totally understand it's annoying, but hope you are not getting stuck on development by this. I will give more update when there is further progress.
Google accepted my app with this error. It wen't live. So it may be something on their side. If I get some more explicit logs in production I will let you know.
My app is now also live so I'd say safe to ignore it.
Hello @mosalex
May i know please when my app will be live on the play store after i submit it ? How much time it usually takes from the date of receiving the pre-launch report ? for example i have submitted the App on 19th this month.
Also do i have to solve out all the issues that i have received in the pre-lunch report to be accepted on the play store ? or i can ignore it as long as its not critical ?
Thanks in advance
@AhmedElmaydoub, they have 7 days for checking your app. For new accounts more. On main page (panel) you have information about checking app and how much time. Check it
@PatrykMCoder
I have submitted my app on 1 Nov and still "Under reviewing" and my account is old from 2018
@MahmoudMabrok that's no matter. They need more time for checking news apps and updates. Read information form panel
@PatrykMCoder
it is not news app
just play videos
@MahmoudMabrok from: https://support.google.com/googleplay/android-developer/answer/9859751?hl=en&visit_id=637415684804244964-417953870&rd=1
_"Whether you're publishing an app for the first time or making an update, your appโs publishing status helps you understand its availability on Google Play."_
You just need to wait :) don't worry :)
Same problem with flutter app after update =/
App won't open and white screen.
The issue like a bolt out of the blue! Iโm trying publish my first flutter Android app.
Same with Ionic + Capacitor app ... sad that there is still no fix for this after more than two weeks.
Has anyone found a downgraded version of firebase that works?
Has anyone found a downgraded version of firebase that works?
It's got nothing to do with Firebase. People are getting this without even using Firebase or Youtube. It's a problem with the Pre-Launch reports, not your code, most likely. One person even got the error after uploading a bare bones app.
I have faced this error, And My App is now live on google play. It seems error with pre-launch report.
I did not add any thing just wait till app be live.
Is secure send my app to production even with this error? I need run my official app version (release)
Any ideal to resolve it. My update still pending for a couple of days.
I face the same problem!
Does anybody have a workaround?
FATAL EXCEPTION: Firebase-Messaging-Intent-Handle
Process: com.google.android.youtube, PID: 27466
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)
Same issue on Huawei P8 running SDK 21 and Nokia 1 running SDK 27.
No Unity code in my app but using Firebase functionality. Following is the stack trace from Firebase test labs
java.lang.NoClassDefFoundError: aewt
FATAL EXCEPTION: Firebase-Messaging-Intent-Handle
Process: com.google.android.youtube, PID: 16350
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: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
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 duc.a(PG:174)
at duc.get(PG:247)
at aeqv.a(PG:6)
at acpw.b(PG:2)
at dxe.a(PG:8)
at dus.onCreate(PG:41)
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)
at dkq.a(PG:6)
at duv.a(Unknown Source:8)
at avlz.f(PG:8)
at avlz.e(PG:5)
at avlz.a(PG:1)
at wqq.a(PG:1)
at aewt.
are there any solution?
help me!
Hi all, sorry that you are experiencing this issue and we are looking into what's going on and how to fix this. Please stay tuned.
Have you got this issue resolved? It's acting like a blocker for us.
In our recent releases we got this issue along with some other crashes, They all were reported in Sentry and Crashlytics and never this one, and Email from the relaunch report never mentioned this as crash
Crashes
Devices without issues 4
So we can safely ignore this
facing same issue
Same issue here.
Same here:
Crashes
Devices without issues
4Devices with issues
2Device(s) with issues
Samsung Galaxy S9 (US) (starqlteue) - Android 8.0
Nokia 1 Android Go (FRT) - Android 8.1Exceptions
java.lang.NoClassDefFoundError: aewt

same issue here when using react-native multi-platform.
min android version +22
max android version 30
devices crashed Nokia Nokia 1 | Android 8.1 (SDK 27)

java.lang.NoClassDefFoundError: aewt
FATAL EXCEPTION: Firebase-Messaging-Intent-Handle
Process: com.google.android.youtube, PID: 16133
java.lang.NoClassDefFoundError: aewt
I have the same problem. is there any solution?I work flutter and I try many solution but don t work.
Same Issuer. Why Play Store(beta) don't publish my apk?
Same problem on Huawei P8 while Google Play Console Pre-Launch test.
FATAL EXCEPTION: Firebase-Messaging-Intent-Handle
Process: com.google.android.youtube, PID: 32466
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)
Hello,
for the record, same problem here through RN SDK 39, on Nokia 1 (8.1 SDK 27).
This is the excerpt from the phone pane (sorry it's in french).
Spรฉcifications de l'appareil
Nom du modรจle
Nokia 1
Fabricant
Nokia
Version d'Android (SDK)
Android 8.1 (SDK 27)
Paramรจtres rรฉgionaux
en_US
Taille de l'รฉcran
480 x 854
Densitรฉ d'รฉcran (PPP)
240
RAM (mรฉmoire totale)
1โฏ024 Mo
Version OpenGL ES
3.1
ABI
ARM_V7
CPU
Mediatek MT6737M
I have no clue what Firebase or Youtube have to do with it, not even using them :)
Hth,
Guillaume
Hello, got same problem with Huawei P8
Has anyone figured a way around this issue?
I'm building with Expo (SDK38) and I can't see any way to specify a minSdkVersion for Android . . .
Not sure if this is specific to a version of the Firebase client, and maybe just upgrading to a newer release would fix it (which will mean I need to upgrade my Expo SDK, the latest is SDK39 and SKD40 is in beta).
Same here commenting to get updates
Same problem has someone found the solution
Same here!
Can the app be approved or work with this error? I'm really stuck
Same problem at my end does anyone fixed this issue
I also have the same error
I have temporarily disabled Pre-Launch check in my project, now waiting to see if the app gets approved for Production release.
Play Console >> Pre-Launch >> Settings >> Pre-launch report preferences (checkbox at the very bottom of the page)
If anyone knows whether this will resolve the release block, or has some other insight to this, please share!
Hi all, sorry that you are experiencing this issue and we are looking into what's going on and how to fix this. Please stay tuned.
Same problem. Will this be sorted soon?
I have faced this error, And My App is now live on google play. It seems error with pre-launch report.
I did not add any thing just wait till app be live.
MahmoudMabrok - how long to wait for the app to go live?
Same question, how long to wait for the app to go live?
On Sat, 12 Dec 2020 at 11:06, Graeme Brooke notifications@github.com
wrote:
I have faced this error, And My App is now live on google play. It seems
error with pre-launch report.I did not add any thing just wait till app be live.
MahmoudMabrok - how long to wait for the app to go live?
โ
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/firebase/quickstart-unity/issues/861#issuecomment-743721401,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJWUYXU4C2CCO53K6IBF7KLSUMP7LANCNFSM4TOHLAJA
.
Same problem here, with an app build using Godot Game Engine, failing on Nokia 1 with this exception.
Same problem on Huawei P8 while Google Play Console Pre-Launch test.
FATAL EXCEPTION: Firebase-Messaging-Intent-Handle Process: com.google.android.youtube, PID: 32466 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)
I release our app 3 day's ago.
Up to now 200000 updated without a problem.
It looks like is a Google Firebase environment problem.
Our app didn't use com.google.android.apps.youtube.app.common.notification.FcmMessageListenerService
Anyone solved?
We have the same error reported in our pre-launch report - will this prevent our app from being released?
FATAL EXCEPTION: Firebase-Messaging-Intent-Handle
Process: com.google.android.youtube, PID: 29044
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)
I temporarily disabled Pre-Launch check in my project. Then 3.5 days after submitting a new build, my app was approved to go to Production.
Play Console >> Pre-Launch >> Settings >> Pre-launch report preferences (checkbox at the very bottom of the page)
If anyone has more insight to this, please share!
Hi @ALL
Sorry it takes a while for me to give update. Here's what I'd like to share with the status:
- This crash should not block the pre launch process, and developers should be able to upload the apps and get published.
- This crash is not directly related to Firebase Unity SDK, we've already received reports from very different channels and products.
- Our team in multiple branches are collaborating on solving the issue.
I totally understand it's annoying, but hope you are not getting stuck on development by this. I will give more update when there is further progress.
same problem with Andorid project
Thanks for that. Good to know.
How long does it take to launch a new app? This is my first.
Ciao,
Graeme
GRAEME BROOKE
VizMAP http://www.vizmap.com.au ~ Grime http://www.grime.net
On Tue, 15 Dec 2020 at 12:58, Grapher notifications@github.com wrote:
Hi @ALL https://github.com/ALL
Sorry it takes a while for me to give update. Here's what I'd like to
share with the status:
- This crash should not block the pre launch process, and developers
should be able to upload the apps and get published.- This crash is not directly related to Firebase Unity SDK, we've
already received reports from very different channels and products.- Our team in multiple branches are collaborating on solving the
issue.I totally understand it's annoying, but hope you are not getting stuck on
development by this. I will give more update when there is further progress.same problem with Andorid project
โ
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/firebase/quickstart-unity/issues/861#issuecomment-745019364,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIEJGPATHJRYUFFYMFGWYU3SU3GDDANCNFSM4TOHLAJA
.
Seeing the same issue.
Seems to be connected with youtube app making a call to firebase ?!
FATAL EXCEPTION: Firebase-Messaging-Intent-Handle
Process: com.google.android.youtube, PID: 29981
java.lang.NoClassDefFoundError: aewt
Same issue delay on releasing the app
Same issue here.
I had the same issue and it took 3 days for app to be live on playstore
On Fri, 18 Dec 2020 at 20:53, Andrey Rezende notifications@github.com
wrote:
Same issue here.
โ
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/firebase/quickstart-unity/issues/861#issuecomment-748229741,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJWUYXXMA7BCTPA2GDZB3MLSVOJHXANCNFSM4TOHLAJA
.
Same issue here.
Ignore it and wait for a few days. Itโll be published soon.
On Mon, 21 Dec 2020 at 4:36 pm, ronald mojica notifications@github.com
wrote:
Same issue here.
โ
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/firebase/quickstart-unity/issues/861#issuecomment-748791886,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIEJGPAKSRNU6XORHLQDAULSV3UGBANCNFSM4TOHLAJA
.>
Graeme Brooke
ph. 0419659866
Sent from my iPhone... Technology rocks.
Ignore it and wait for a few days. Itโll be published soon.
On Mon, 21 Dec 2020 at 4:36 pm, ronald mojica @.*> wrote: Same issue here. โ You are receiving this because you commented. Reply to this email directly, view it on GitHub <#861 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIEJGPAKSRNU6XORHLQDAULSV3UGBANCNFSM4TOHLAJA .
-- Graeme Brooke ph. 0419659866 Sent from my iPhone... Technology rocks.
how long did it take for your app to be approved?
On Mon, 21 Dec 2020 at 4:51 pm, ronald mojica notifications@github.com
wrote:
Ignore it and wait for a few days. Itโll be published soon.
On Mon, 21 Dec 2020 at 4:36 pm, ronald mojica @.*> wrote: Same issue
here. โ You are receiving this because you commented. Reply to this email
directly, view it on GitHub <#861 (comment)
https://github.com/firebase/quickstart-unity/issues/861#issuecomment-748791886>,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIEJGPAKSRNU6XORHLQDAULSV3UGBANCNFSM4TOHLAJA
.
-- Graeme Brooke ph. 0419659866 Sent from my iPhone... Technology rocks.how long did it take for your app to be approved?
โ
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/firebase/quickstart-unity/issues/861#issuecomment-748798250,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIEJGPEXCKI4WS7SB7DT7PDSV3V75ANCNFSM4TOHLAJA
.It was live 5 days after I posted it. --
Graeme Brooke
ph. 0419659866
Sent from my iPhone... Technology rocks.
Yes, with me it was approved even with this error. It is already in production.
Sorry for my english. I don't know if this is a solution to the problem for everyone, but in my case I seem to have found the problematic place where java.lang.NoClassDefFoundError is called: aewt for Nokia 1. Most likely, the robot that is testing the application is out of bounds and starts testing the youtube application, which contains bugs for this smartphone model. My app had a link to a YouTube video. I uploaded my application to firebase testlab, the same thing that I tried to upload to the play market, and in 2 tests for nokia in different orientations I get the error NoClassDefFoundError: aewt. Then I rebuilt my application, just commented out the place where YouTube was supposed to open and repeated the tests for Nokia, there were no more errors in any of the tests. You can also test your application. The free plan includes 5 tests per day.
Subscribing
I also have zero references to youtube, no links and none of the web pages I link to from the app have no references to youtube neither. And I'm not the official youtube developer :stuck_out_tongue:
Seems related to Firebase messaging, which I'm using (ionic5+angular+capacitor+(firebase incl messaging, storage, auth)

Sorry for my english. I don't know if this is a solution to the problem for everyone, but in my case I seem to have found the problematic place where java.lang.NoClassDefFoundError is called: aewt for Nokia 1. Most likely, the robot that is testing the application is out of bounds and starts testing the youtube application, which contains bugs for this smartphone model. My app had a link to a YouTube video. I uploaded my application to firebase testlab, the same thing that I tried to upload to the play market, and in 2 tests for nokia in different orientations I get the error NoClassDefFoundError: aewt. Then I rebuilt my application, just commented out the place where YouTube was supposed to open and repeated the tests for Nokia, there were no more errors in any of the tests. You can also test your application. The free plan includes 5 tests per day.
Hi, it can be a false positive result I suppose.
Same issue here...
Does it cause the app to crash for users? Or is this only in the background without any impact for users?
Does it cause the app to crash for users? Or is this only in the background without any impact for users?
Looks like it never leads to an ANR. So, it might be just a background error with no impact.
I have been 6 days and still nothing, before it delayed 1 to 2 days.
Play Console -> devices
Delete Huawei P8
Delete Nokia 1
and all incompatible devices.
Having no reference for YouTube, still getting this crash, strange.

anyone help
I did nothing and a few days later it went live.
Ciao,
Graeme
GRAEME BROOKE
VizMAP http://www.vizmap.com.au ~ Grime http://www.grime.net
On Wed, 6 Jan 2021 at 12:47, Super Shanks notifications@github.com wrote:
anyone help
โ
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/firebase/quickstart-unity/issues/861#issuecomment-755041285,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIEJGPAQD7ZTSON7BZGGWRDSYPFMRANCNFSM4TOHLAJA
.
FATAL EXCEPTION: Firebase-Messaging-Intent-Handle
Process: com.google.android.youtube, PID: 29101
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)
...
Same error on my first push to publish a new app, I have no references to youtube in my code. React-Native project, its been delayed only 1 day so far, will wait for a few days see if it publishes.
Same error is showing for me. I am publishing app for first time.
Seems that it was fixed: https://issuetracker.google.com/issues/160907013#comment149
Hi , to solve this min sdk has to be 28
Nokia Nokia 1 Android 8.1 (SDK 27)
Huawei P8 ้ๆฅ็ Android 5.0 (SDK 21)
So my app will support only for android 9 and 10. It is not a right way. We will miss majority of users. we need to support from marshmallow..
Subscribing, same here, API 29
The very same error. app is based on flutter. minSDK=21, targetSDK=29 in my case.
Experiencing the same issue for my Flutter App.
minSDK = 18
targetSDK = 29
Glad to find all this comments.
Same issue reported for Nokia 1, also report about youtube
minSDK = 21
targetSDK = 29
Stacktrace java.lang.NoClassDefFoundError: aewt
_My app had a link to a YouTube video. I uploaded my application to firebase testlab, the same thing that I tried to upload to the play market, and in 2 tests for nokia in different orientations I get the error NoClassDefFoundError: aewt. Then I rebuilt my application, just commented out the place where YouTube was supposed to open_
So you say/suggest that because Google now asks us to made an video wherein one must explain how its app handles users permission and why our app's collapse. Can make sense. We filled in a video location and our video is not yet made at all. Can created a dummy and see what happens then.
Hi!! Someone has the issue solved ? How many days it took?
Hey everyone, same issue here.
Also for youtube.
minSDK = 21
targetSDK = 30
This issue is still there and look like it's only google's test bot bug or something. Despite the test failure my application is running on production without any problem at all.
by the way I've built my app with Xamarin.Forms did you guys use Java or Kotlin?
same issue.
java.lang.NoClassDefFoundError: aewt
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 playstore app update method (app bundle). Why do I think the problem is in the playstore system? because this problem occurs to users starting around 11/1/2020, I think on this date google update google play system system 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 upload the app in playstore the problem suddenly disappears and when I reupload it the problem appears again. For all these reasons, I think the problem is the playstore system.
Same issue here. I hope it gets resolved soon. My app is pending approval. Waiting for more than 4 days now.
Any suggestion for a workaround? It seems the guys at google don't care this.
HI @MehmetKaplan ,
for me it works changing the min sdk to 28 , i was able to promote to internal testing , at lest
_"Any suggestion for a workaround? It seems the guys at google don't care this."_
Remove the phone that do not work from the list of supported phones
I face the same problem!
Does anybody have a workaround?As a temporary solution we increased the minimum SDK version to 22 to force skipping the faulty devices.
Hey GyuriMajercsik
I upgrade my game's minimum API level to 22 , this issue was solved but by using this our game skipped many devices, But in current situation i again upload my game with minimum 22 API level, i found this issue again can you tell me, why this happen so?
I face the same problem!
Does anybody have a workaround?As a temporary solution we increased the minimum SDK version to 22 to force skipping the faulty devices.
Hey GyuriMajercsik
I upgrade my game's minimum API level to 22 , this issue was solved but by using this our game skipped many devices, But in current situation i again upload my game with minimum 22 API level, i found this issue again can you tell me, why this happen so?
Indeed, you will limit the supported devices by increasing the minimum level to 22, but based on our research that percentage is not very big (https://www.xda-developers.com/android-version-distribution-statistics-android-studio/) .
Anyway, the decision depends on your target audience as well.
On the other hand, I've seen other workarounds for this issue but I've not tested. For example:
_"Any suggestion for a workaround? It seems the guys at google don't care this."_
Remove the phone that do not work from the list of supported phones
I face the same problem!
Does anybody have a workaround?As a temporary solution we increased the minimum SDK version to 22 to force skipping the faulty devices.
Hey GyuriMajercsik
I upgrade my game's minimum API level to 22 , this issue was solved but by using this our game skipped many devices, But in current situation i again upload my game with minimum 22 API level, i found this issue again can you tell me, why this happen so?Indeed, you will limit the supported devices by increasing the minimum level to 22, but based on our research that percentage is not very big (https://www.xda-developers.com/android-version-distribution-statistics-android-studio/) .
Anyway, the decision depends on your target audience as well.On the other hand, I've seen other workarounds for this issue but I've not tested. For example:
_"Any suggestion for a workaround? It seems the guys at google don't care this."_
Remove the phone that do not work from the list of supported phones
Thanks GyuriMajercsik
But by target the minimum API level to 22 , I still find this crash, you have any idea?
The crash report should be fixed in the backend on 1/26. Close for now, and if anyone still see it, please reopen. Thanks.
Most helpful comment
Hi all, sorry that you are experiencing this issue and we are looking into what's going on and how to fix this. Please stay tuned.