Android新手求助：管理Job Queue实现多条Firebase通知不被覆盖

算力阿峰

2026-5-26

Fixing Duplicate Notification Overwrites in Android

Hey there! As someone who’s stumbled through this exact issue early in my Android dev journey, I know how frustrating it is when older notifications get wiped out by new ones of the same type. Let’s break down why this happens and how to fix it.

Why Your Notifications Are Being Overwritten

The most common culprit here is using the same notification ID every time you call NotificationManager.notify(). Android uses this ID to decide whether to create a new notification or update an existing one. Reusing the same ID will replace the old notification instead of adding a fresh one.

Step-by-Step Solutions

1. Generate Unique Notification IDs for Each Instance

You need a unique integer ID every time you trigger a notification. Here are a few straightforward ways to do this:

Use a timestamp: Grab the current time in milliseconds—this is almost guaranteed to be unique for each notification trigger:
```
val uniqueId = System.currentTimeMillis().toInt()
notificationManager.notify(uniqueId, notification)
```
(For Java: (int) System.currentTimeMillis())

Use an incrementing counter: Keep a static counter in your Service or BroadcastReceiver that increases each time a notification is sent:

class MyNotificationService : Service() {
    private var notificationCounter = 0
    
    private fun sendNotification() {
        val uniqueId = notificationCounter++
        notificationManager.notify(uniqueId, notification)
    }
}

Use a unique identifier from your data: If your notifications are tied to specific items (like a message ID or order ID), use that existing unique value as the notification ID. For example, if you’re receiving a broadcast with a messageId extra:
```
val messageId = intent.getIntExtra("MESSAGE_ID", -1)
if (messageId != -1) {
    notificationManager.notify(messageId, notification)
}
```

2. Group Notifications (For Cleaner Organization)

If you don’t want a cluttered notification shade but still want to keep all same-type notifications accessible, use Android’s notification grouping feature. This bundles related notifications under a single summary:

First, create a group summary notification:

val summaryNotification = NotificationCompat.Builder(this, CHANNEL_ID)
    .setContentTitle("You have 3 new alerts")
    .setContentText("Tap to view all")
    .setSmallIcon(R.drawable.ic_notification)
    .setStyle(NotificationCompat.InboxStyle()
        .addLine("Alert 1")
        .addLine("Alert 2")
        .addLine("Alert 3")
        .setSummaryText("+2 more"))
    .setGroup(GROUP_KEY_ALERTS)
    .setGroupSummary(true)
    .build()

Set the same group key on each individual notification:

val individualNotification = NotificationCompat.Builder(this, CHANNEL_ID)
    .setContentTitle("New Alert")
    .setContentText("Alert details here")
    .setSmallIcon(R.drawable.ic_notification)
    .setGroup(GROUP_KEY_ALERTS)
    .build()

Notify both the individual notification (with a unique ID) and the summary (use a fixed ID for the summary):

notificationManager.notify(uniqueId, individualNotification)
notificationManager.notify(SUMMARY_ID, summaryNotification)

3. Double-Check Your BroadcastReceiver/Service Logic

Make sure your BroadcastReceiver isn’t accidentally reusing the same ID each time it receives an intent. For example, hardcoding an ID like 1 in your notify() call will definitely overwrite notifications. Always ensure the ID is dynamic and unique per notification.

Bonus Tip: Managing Notifications Later

If you need to update or cancel specific notifications down the line, store the unique IDs you used. You can save them in SharedPreferences, a local database, or pass them back via intents when needed. That way, you can reference the exact notification you want to modify.

内容的提问来源于stack exchange，提问作者reema thacker