FCM background notifications do not trigger custom Analytics event
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 25/100
- Tipo de issue
- Error
- Claridad
- Necesita aclaración
- Estado de actividad
- Estancado
- Área
- mobile-dev
Línea de trabajo
Comienza con MyFirebaseMessagingService.onMessageReceived y compara el comportamiento de los payloads de notification y data descrito en los pasos de reproducción. Consulta la documentación sobre la entrega en segundo plano de Firebase Messaging y la carga de Analytics; después, verifica si el evento reportado aparece cuando la aplicación vuelve a estar en primer plano. El trabajo requiere confirmar la causa o disponer de un problema de quickstart más claro y reproducible.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Description
I am trying to log a custom Analytics event from onMessageReceived in my FirebaseMessagingService when a background notification is delivered. However, the custom event is never showing up in Firebase DebugView or the Analytics dashboard. I suspect that onMessageReceived is not being called in the background or that the payload might not be set up correctly. I’d like help diagnosing why the custom event is not appearing.
Step 1: Describe your environment
- Android device: Pixel 5 (example)
- Android OS version: 12 (example)
- Google Play Services version: 22.12.13 (example)
- Firebase/Play Services SDK version:
- Firebase Messaging: 23.0.0
- Firebase Analytics: 21.2.0
(examples—replace with your actual versions)
Step 2: Describe the problem
Steps to reproduce
- Create a subclass of
FirebaseMessagingService(e.g.,MyFirebaseMessagingService) that overridesonMessageReceived. - In
onMessageReceived, log a custom event usingFirebaseAnalytics.logEvent(...)when a data payload is present. - Send an FCM message from the Firebase Console or a server with both
notificationanddatapayloads. - Put the app in the background.
- Wait for the notification to arrive, then check Firebase DebugView for the custom event.
Observed Results
- The
onMessageReceivedmethod seems to run when the app is in the foreground (and the custom event appears in DebugView). - When the app is in the background, the custom event (
notification_received_background) never appears in DebugView or in the Analytics dashboard. - It appears that
onMessageReceivedis not being triggered, or the event is not being uploaded in the background.
Expected Results
- Even if the notification is received while the app is in the background, the custom event (
notification_received_background) should be logged and appear in DebugView (after the app comes to the foreground to upload events).
Relevant Code
package com.example.myapplication
import android.app.NotificationChannel
import android.app.NotificationManager
import android.app.PendingIntent
import android.content.Context
import android.content.Intent
import android.os.Build
import android.os.Bundle
import android.util.Log
import androidx.core.app.NotificationCompat
import com.google.firebase.analytics.FirebaseAnalytics
import com.google.firebase.analytics.ktx.analytics
import com.google.firebase.ktx.Firebase
import com.google.firebase.messaging.FirebaseMessagingService
import com.google.firebase.messaging.RemoteMessage
import com.example.myapplication.extension.isAppInForeground
class MyFirebaseMessagingService : FirebaseMessagingService() {
private val firebaseAnalytics: FirebaseAnalytics by lazy {
Firebase.analytics
}
override fun onMessageReceived(remoteMessage: RemoteMessage) {
// Log data payload
if (remoteMessage.data.isNotEmpty()) {
Log.d("FirebaseMessagingService", "Data payload: ${remoteMessage.data}")
// Log custom event
logEventToFirebase("notification_received_background", "Android", "google.com")
}
val isInForeground = applicationContext.isAppInForeground()
if (isInForeground) {
logEventToFirebase("notification_user_foreground", "Android", "google.com")
}
// Show a local notification
showNotification(remoteMessage, "Android", "google.com")
}
override fun onNewToken(token: String) {
super.onNewToken(token)
Log.d("FCM", "New FCM Token: $token")
}
private fun showNotification(
remoteMessage: RemoteMessage,
operatorName: String,
subDomain: String
) {
val notificationManager =
getSystemService(Context.NOTIFICATION_SERVICE) as NotificationManager
val channelId = "default_channel"
if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.O) {
val channel = NotificationChannel(
channelId,
"Default Channel",
NotificationManager.IMPORTANCE_DEFAULT
)
notificationManager.createNotificationChannel(channel)
}
val tapIntent = Intent(this, MainActivity::class.java).apply {
flags = Intent.FLAG_ACTIVITY_NEW_TASK or Intent.FLAG_ACTIVITY_CLEAR_TASK
putExtra("operator_name", operatorName)
putExtra("sub_domain", subDomain)
}
val pendingTapIntent = PendingIntent.getActivity(
this, 0, tapIntent, PendingIntent.FLAG_IMMUTABLE
)
val dismissIntent = Intent(this, NotificationDismissReceiver::class.java)
val pendingDismissIntent = PendingIntent.getBroadcast(
this, 1, dismissIntent, PendingIntent.FLAG_IMMUTABLE
)
val builder = NotificationCompat.Builder(this, channelId)
.setSmallIcon(R.drawable.ic_notification)
.setContentTitle(remoteMessage.data["title"] ?: "Title")
.setContentText(remoteMessage.data["body"] ?: "Body")
.setContentIntent(pendingTapIntent)
.setDeleteIntent(pendingDismissIntent)
.setAutoCancel(true)
notificationManager.notify(0, builder.build())
}
private fun logEventToFirebase(eventName: String, operatorName: String, subDomain: String) {
val params = Bundle().apply {
putString("operator_name", operatorName)
putString("sub_domain", subDomain)
}
firebaseAnalytics.logEvent(eventName, params)
}
}
- Lenguaje dominante
- Kotlin
- Estrellas
- 9.3k
- Forks
- 7.4k
- Merge medio
- 7 d 9 h
- PR fusionados (30 d)
- 6
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de firebase/quickstart-android
-
Dificultad 3/5 1-2 días Aptitud para principiantes 35/100
firebase/quickstart-android#2756 · 1 comentario ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
firebase/quickstart-android#2754 · 5 comentarios · 1 reacción ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 32/100
firebase/quickstart-android#2668 ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 25/100
firebase/quickstart-android#1669 · 3 comentarios ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 25/100
firebase/quickstart-android#1580 · 1 comentario ·
Todos los issues de firebase/quickstart-android
Issues similares
-
android:plan main:plan packages:learn
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
Los mantenedores suelen responder en 1 día
-
Needs Triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
ankidroid/Anki-Android#23453 ·
Los mantenedores suelen responder en 1 día
-
afk-ok area:data-quality importer size:S
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
enorm-labs/event-junkie#5278 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
bazel-contrib/rules_kotlin#1846 ·
Los mantenedores suelen responder en 2 días