quickstart-unity: java.lang.NoClassDefFoundError: aewt

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.

Hi @all

Sorry it takes a while for me to give update. Here’s what I’d like to share with the status:

1. This crash should not block the pre launch process, and developers should be able to upload the apps and get published.
2. This crash is not directly related to Firebase Unity SDK, we’ve already received reports from very different channels and products.
3. 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.

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 experiencing this issue and cannot upgrade the application on Playstore…

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.

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.

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!

same problem with flutter app

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?

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

Play Console -> devices Delete Huawei P8 Delete Nokia 1 and all incompatible devices.

Hope google solve that issue

Same issuer … and I cant Resume Track on Open Testing

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

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.

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.

Experiencing the same issue for my Flutter App.

minSDK = 18 targetSDK = 29

Seems that it was fixed: https://issuetracker.google.com/issues/160907013#comment149

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.

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.

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.

Identical problem. Made in Unity

Are you all getting this crash after updating Firebase dependencies?

I’m not even using Firebase in my project and still have this problem

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 issuer. Huawei P8 青春版 720x1280 Android 5.0 (SDK 21) 2,048 MB ARM64_V8 en_US

I face the same problem! Does anybody have a workaround?

“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

HI @MehmetKaplan , for me it works changing the min sdk to 28 , i was able to promote to internal testing , at lest

The very same error. app is based on flutter. minSDK=21, targetSDK=29 in my case.

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)

Same problem has someone found the solution

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

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)

Same Issuer. Why Play Store(beta) don’t publish my apk?

Same here:

Crashes

Devices without issues 4

Devices with issues 2

Device(s) with issues Samsung Galaxy S9 (US) (starqlteue) - Android 8.0 Nokia 1 Android Go (FRT) - Android 8.1

Exceptions java.lang.NoClassDefFoundError: aewt

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

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.

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 error, but I’m wondering how come the crash is from youtube and affect the test?

Process: com.google.android.youtube, PID: 26795

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… 😕

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’ … } …

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

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

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.