-
Notifications
You must be signed in to change notification settings - Fork 433
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
Comments
People are getting this same problem with the Nokia 1 and Huawei P8 青春版, without using any Firebase libraries. Please see: |
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: Below are the stack traces (which are slightly different through) Huawei P8 青春版: FATAL EXCEPTION: Firebase-Messaging-Intent-Handle Nokia Nokia 1: FATAL EXCEPTION: Firebase-Messaging-Intent-Handle |
I face the same problem! |
Ran into the same problem: java.lang.NoClassDefFoundError: aewt |
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 FATAL EXCEPTION: Firebase-Messaging-Intent-Handle |
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. |
Similar prelaunch errors referring to youtube and firebase messaging for my app as well. (The app doesn't even require internet permission to work!?) |
堆栈轨迹 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. |
The target version is 29. It fixed for us. 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? |
@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. nokia 1 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) |
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: |
Same problem, Nokia Nokia 1 and Huawei P8 青春版 devices
|
Play Console -> devices |
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>
Batphone: +61 (0)4 1965 9866 ~ Skype Phone: +61 (0)7 3040 2228
------------------------------
…On Wed, 6 Jan 2021 at 12:47, Super Shanks ***@***.***> wrote:
anyone help
—
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/AIEJGPAQD7ZTSON7BZGGWRDSYPFMRANCNFSM4TOHLAJA>
.
|
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) |
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 |
Glad to find all this comments. |
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. |
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. |
same issue. |
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 , |
"Any suggestion for a workaround? It seems the guys at google don't care this." |
Hey GyuriMajercsik |
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/) . On the other hand, I've seen other workarounds for this issue but I've not tested. For example:
|
Thanks GyuriMajercsik |
The crash report should be fixed in the backend on 1/26. Close for now, and if anyone still see it, please reopen. Thanks. |
[REQUIRED] Please fill in the following fields:
[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.
}
});
}
The text was updated successfully, but these errors were encountered: