FATAL EXCEPTION: Firebase-Messaging-Intent-Handle
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Anfängerfreundlichkeit
- 15/100
Rechercherichtung
Es wird keine bestimmte Quelldatei oder kein Reproduktionsschritt angegeben. Beginne mit dem Kotlin-Messaging-Sample unter messaging/app/src/main/java/com/google/firebase/quickstart/fcm/kotlin und vergleiche dessen Abhängigkeiten mit den gemeldeten Versionen von Firebase und Google-Diensten. Überprüfe die Stacktraces aus Firebase Test Lab und der Play Console, stelle anschließend einen reproduzierbaren Fall her und dokumentiere, ob das Messaging-Sample den gemeldeten Absturz vermeiden kann.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
Step 1: Describe your environment
- Android device: Nokia 1
- Android OS version: 8.1 (API 27)
- Google Play Services version: 203915062
- Firebase/Play Services SDK version: firebase-bom:26.0.0/google-services:4.3.4
buildscript {
ext.kotlin_version = "1.4.10"
repositories {
google()
jcenter()
}
dependencies {
classpath 'com.android.tools.build:gradle:4.1.0'
classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"
classpath 'com.google.gms:google-services:4.3.4'
classpath 'com.google.firebase:firebase-crashlytics-gradle:2.3.0'
}
}
*****************
plugins {
id 'com.android.application'
id 'kotlin-android'
id 'kotlin-android-extensions'
id 'com.google.gms.google-services'
id 'com.google.firebase.crashlytics'
}
dependencies {
***
implementation "com.google.gms:google-services:4.3.4"
implementation 'com.google.android.play:core:1.8.3'
implementation platform('com.google.firebase:firebase-bom:26.0.0')
implementation 'com.google.firebase:firebase-crashlytics-ktx'
implementation "com.google.firebase:firebase-functions-ktx"
implementation "com.google.firebase:firebase-messaging-ktx"
Step 2: Describe the problem:
Steps to reproduce:
- This problem shown on pre-release report of Google Play Console for two devices Nokia 1 and Huawei P8
- In local emulator or physical devices not showing this exception, but also shown in Firebase Test Lab devices.
- I tested messaging in local devices with FCM token and works fine
- I used the same code in this repo : https://github.com/firebase/quickstart-android/tree/master/messaging/app/src/main/java/com/google/firebase/quickstart/fcm/kotlin
Observed Results:
- Firbase Test Lab Logcat
11-06 02:29:25.410: E/AndroidRuntime(17339): FATAL EXCEPTION: Firebase-Messaging-Intent-Handle
11-06 02:29:25.410: E/AndroidRuntime(17339): Process: com.google.android.youtube, PID: 17339
11-06 02:29:25.410: E/AndroidRuntime(17339): java.lang.NoClassDefFoundError: aewt
11-06 02:29:25.410: E/AndroidRuntime(17339): at aewu.b(PG:1)
11-06 02:29:25.410: E/AndroidRuntime(17339): at duc.a(PG:230)
11-06 02:29:25.410: E/AndroidRuntime(17339): at duc.get(PG:247)
11-06 02:29:25.410: E/AndroidRuntime(17339): at aevw.b(PG:1)
11-06 02:29:25.410: E/AndroidRuntime(17339): at dud.al(PG:5)
11-06 02:29:25.410: E/AndroidRuntime(17339): at dud.aw(PG:4)
11-06 02:29:25.410: E/AndroidRuntime(17339): at dud.bg(PG:8)
11-06 02:29:25.410: E/AndroidRuntime(17339): at duc.a(PG:232)
11-06 02:29:25.410: E/AndroidRuntime(17339): at duc.get(PG:247)
11-06 02:29:25.410: E/AndroidRuntime(17339): at afke.a(PG:1)
11-06 02:29:25.410: E/AndroidRuntime(17339): at aeri.b(PG:1)
11-06 02:29:25.410: E/AndroidRuntime(17339): at dud.fv(PG:4)
11-06 02:29:25.410: E/AndroidRuntime(17339): at duc.c(PG:269)
11-06 02:29:25.410: E/AndroidRuntime(17339): at duc.get(PG:247)
11-06 02:29:25.410: E/AndroidRuntime(17339): at amfk.a(PG:1)
11-06 02:29:25.410: E/AndroidRuntime(17339): at eiu.K(PG:5)
11-06 02:29:25.410: E/AndroidRuntime(17339): at dud.fV(PG:7)
11-06 02:29:25.410: E/AndroidRuntime(17339): at duc.d(PG:334)
11-06 02:29:25.410: E/AndroidRuntime(17339): at duc.get(PG:247)
11-06 02:29:25.410: E/AndroidRuntime(17339): at com.google.android.apps.youtube.app.common.notification.FcmMessageListenerService.b(PG:1)
11-06 02:29:25.410: E/AndroidRuntime(17339): at com.google.firebase.messaging.FirebaseMessagingService.g(PG:53)
11-06 02:29:25.410: E/AndroidRuntime(17339): at avgp.run(Unknown Source:7)
11-06 02:29:25.410: E/AndroidRuntime(17339): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
11-06 02:29:25.410: E/AndroidRuntime(17339): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
11-06 02:29:25.410: E/AndroidRuntime(17339): at usj.run(PG:2)
11-06 02:29:25.410: E/AndroidRuntime(17339): at java.lang.Thread.run(Thread.java:764)
11-06 02:29:25.410: E/AndroidRuntime(17339): Caused by: java.lang.ExceptionInInitializerError
11-06 02:29:25.410: E/AndroidRuntime(17339): at aewu.b(PG:1)
11-06 02:29:25.410: E/AndroidRuntime(17339): at duc.a(PG:230)
11-06 02:29:25.410: E/AndroidRuntime(17339): at duc.get(PG:247)
11-06 02:29:25.410: E/AndroidRuntime(17339): at aevw.b(PG:1)
11-06 02:29:25.410: E/AndroidRuntime(17339): at dud.al(PG:5)
11-06 02:29:25.410: E/AndroidRuntime(17339): at duc.a(PG:174)
11-06 02:29:25.410: E/AndroidRuntime(17339): at duc.get(PG:247)
11-06 02:29:25.410: E/AndroidRuntime(17339): at aeqv.a(PG:6)
11-06 02:29:25.410: E/AndroidRuntime(17339): at acpw.b(PG:2)
11-06 02:29:25.410: E/AndroidRuntime(17339): at dxe.a(PG:8)
11-06 02:29:25.410: E/AndroidRuntime(17339): at dus.onCreate(PG:41)
11-06 02:29:25.410: E/AndroidRuntime(17339): at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1119)
11-06 02:29:25.410: E/AndroidRuntime(17339): at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5767)
11-06 02:29:25.410: E/AndroidRuntime(17339): at android.app.ActivityThread.-wrap1(Unknown Source:0)
11-06 02:29:25.410: E/AndroidRuntime(17339): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1680)
11-06 02:29:25.410: E/AndroidRuntime(17339): at android.os.Handler.dispatchMessage(Handler.java:106)
11-06 02:29:25.410: E/AndroidRuntime(17339): at android.os.Looper.loop(Looper.java:164)
11-06 02:29:25.410: E/AndroidRuntime(17339): at android.app.ActivityThread.main(ActivityThread.java:6523)
11-06 02:29:25.410: E/AndroidRuntime(17339): at java.lang.reflect.Method.invoke(Native Method)
11-06 02:29:25.410: E/AndroidRuntime(17339): at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
11-06 02:29:25.410: E/AndroidRuntime(17339): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:857)
11-06 02:29:25.410: E/AndroidRuntime(17339): Caused by: dkp: libelements.so
11-06 02:29:25.410: E/AndroidRuntime(17339): at dks.c(PG:52)
11-06 02:29:25.410: E/AndroidRuntime(17339): at dkq.a(PG:6)
11-06 02:29:25.410: E/AndroidRuntime(17339): at duv.a(Unknown Source:8)
11-06 02:29:25.410: E/AndroidRuntime(17339): at avlz.f(PG:8)
11-06 02:29:25.410: E/AndroidRuntime(17339): at avlz.e(PG:5)
11-06 02:29:25.410: E/AndroidRuntime(17339): at avlz.a(PG:1)
11-06 02:29:25.410: E/AndroidRuntime(17339): at wqq.a(PG:1)
11-06 02:29:25.410: E/AndroidRuntime(17339): at aewt.<clinit>(PG:1)
11-06 02:29:25.410: E/AndroidRuntime(17339): ... 21 more
- Play Console Pre-release Logcat
Process: com.google.android.youtube, PID: 27807
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)
Expected Results:
- I don't know why Process: com.google.android.youtube is showing and i'm not using any youtube library all
Relevant Code:
No specific code or step shown that produce the exception.
- Vorherrschende Sprache
- Kotlin
- Sterne
- 9.3k
- Forks
- 7.4k
- Ø Merge
- 7 T. 9 Std.
- Gemergte PRs (30 T.)
- 6
Entwicklungsumgebung
- Kein Dockerfile und keine Docker-Compose-Datei
- Keine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus firebase/quickstart-android
-
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 35/100
firebase/quickstart-android#2756 · 1 Kommentar ·
-
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 35/100
firebase/quickstart-android#2754 · 5 Kommentare · 1 Reaktion ·
-
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 32/100
firebase/quickstart-android#2668 ·
-
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 25/100
firebase/quickstart-android#2663 · 1 Kommentar ·
-
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 25/100
firebase/quickstart-android#1669 · 3 Kommentare ·
Alle Issues in firebase/quickstart-android
Ähnliche Issues
-
android:plan main:plan packages:learn
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
Maintainer antworten meist innerhalb von 1 Tag
-
bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 86/100
Maintainer antworten meist innerhalb von 1 Tag
-
Needs Triage
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
ankidroid/Anki-Android#23453 ·
Maintainer antworten meist innerhalb von 1 Tag
-
afk-ok area:data-quality importer size:S
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
enorm-labs/event-junkie#5278 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 65/100
bazel-contrib/rules_kotlin#1846 ·
Maintainer antworten meist innerhalb von 2 Tagen