Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

java.lang.NoClassDefFoundError: aewt #861

Closed
programming2012 opened this issue Nov 8, 2020 · 146 comments
Closed

java.lang.NoClassDefFoundError: aewt #861

programming2012 opened this issue Nov 8, 2020 · 146 comments

Comments

@programming2012
Copy link

[REQUIRED] Please fill in the following fields:

  • Unity editor version: _____Unity 2019.4.13f1
  • Firebase Unity SDK version: _____Firebase Unity SDK 6.16.1
  • Source you installed the SDK: _____ .unitypackage
  • Problematic Firebase Component: _____ Analytics
  • Other Firebase Components in use: _____ No other
  • Additional SDKs you are using: _____ Facebook, AdMob
  • Platform you are using the Unity editor on: _____ Mac
  • Platform you are targeting: _____ Android
  • Scripting Runtime: _____ IL2CPP

[REQUIRED] Please describe the issue here:

The Build is success. And then I upload to Google Play Console, In Test report , there are two devices has report the error.

Steps to reproduce:

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.(PG:1)
... 21 more

Relevant Code:

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)


@grolschie
Copy link

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

@GyuriMajercsik
Copy link

We are experiencing this issue and cannot upgrade the application on Playstore...

@atrodriguez88
Copy link

Same issuer .... and I cant Resume Track on Open Testing

@dmitrymal
Copy link

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.(PG:1)
... 21 more

https://www.companova.com/

@Working4u
Copy link

Working4u commented Nov 9, 2020

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

@0x079
Copy link

0x079 commented Nov 9, 2020

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)

@GyuriMajercsik
Copy link

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.

@NadyaRnV
Copy link

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.(PG:1)
... 21 more

@Working4u
Copy link

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?

image

@jinpang
Copy link

jinpang commented Nov 11, 2020

Same issuer.
Huawei P8 青春版
720x1280
Android 5.0 (SDK 21)
2,048 MB
ARM64_V8
en_US

image

@teekamsuthar
Copy link

teekamsuthar commented Nov 11, 2020

Similar prelaunch errors referring to youtube and firebase messaging for my app as well. (The app doesn't even require internet permission to work!?)

@tianzexin
Copy link

堆栈轨迹
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?

@NadyaRnV
Copy link

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.

@GyuriMajercsik
Copy link

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.

image

We also updated all of the plugins and libraries to the latest versions.

@lisichka999
Copy link

lisichka999 commented Nov 11, 2020

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?

@manohar-octifi
Copy link

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

@teekamsuthar
Copy link

teekamsuthar commented Nov 11, 2020

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

@PatrykMCoder
Copy link

PatrykMCoder commented Nov 11, 2020

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)

@MahmoudMabrok
Copy link

Hope google solve that issue

@cynthiajoan
Copy link
Contributor

cynthiajoan commented Nov 11, 2020

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.

@scrapecoder
Copy link

facing same issue

@PatrykMCoder
Copy link

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

@tarsissantiago
Copy link

tarsissantiago commented Nov 12, 2020

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

@zandotc1
Copy link

zandotc1 commented Jan 4, 2021

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

@pundhir
Copy link

pundhir commented Jan 4, 2021

Having no reference for YouTube, still getting this crash, strange.

Screenshot 2021-01-04 at 17 48 25

@ding33211
Copy link

anyone help

@VizMAP
Copy link

VizMAP commented Jan 6, 2021 via email

@GrahamEvans31
Copy link

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.

@fazil-augr
Copy link

Same error is showing for me. I am publishing app for first time.

@williamgurzoni
Copy link

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

@elaneri
Copy link

elaneri commented Jan 8, 2021

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)

@fazil-augr
Copy link

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

@ghost
Copy link

ghost commented Jan 11, 2021

Subscribing, same here, API 29

@strmik
Copy link

strmik commented Jan 13, 2021

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

@RANSoftRA
Copy link

Experiencing the same issue for my Flutter App.

minSDK = 18
targetSDK = 29

@Janhgm
Copy link

Janhgm commented Jan 14, 2021

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

@Janhgm
Copy link

Janhgm commented Jan 14, 2021

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.

@Yajariyu
Copy link

Hi!! Someone has the issue solved ? How many days it took?

@pavelryaboff
Copy link

Hey everyone, same issue here.
Also for youtube.
minSDK = 21
targetSDK = 30

@uzairali001
Copy link

uzairali001 commented Jan 15, 2021

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?

@ggyyVSggyy
Copy link

same issue.
java.lang.NoClassDefFoundError: aewt

@elhaouzi
Copy link

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.

@Leoudayan
Copy link

Same issue here. I hope it gets resolved soon. My app is pending approval. Waiting for more than 4 days now.

@MehmetKaplan
Copy link

Any suggestion for a workaround? It seems the guys at google don't care this.

@elaneri
Copy link

elaneri commented Jan 22, 2021

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

@Janhgm
Copy link

Janhgm commented Jan 22, 2021

"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

@Faheem0331
Copy link

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?

@GyuriMajercsik
Copy link

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

@Faheem0331
Copy link

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?

@cynthiajoan
Copy link
Contributor

The crash report should be fixed in the backend on 1/26. Close for now, and if anyone still see it, please reopen. Thanks.

@firebase firebase locked and limited conversation to collaborators Feb 27, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests