firebase / firebase/firebase-admin-java

Duplicate Notifications Delivered through FC

オープン
#863 コメント 3 件 リアクション 0 件 担当者 0 名 GitHub で見る
api: messaging
主要言語
Java
スター
620
フォーク
305
平均マージ
3時間 23分
マージ済み PR(30日)
1

説明

### Environment:

* Operating System version: Java 8
* Firebase SDK version: 10.11.0
* Library version: 8.1.0
* Firebase Product: messaging (auth, database, storage, etc)

### Problem:

We're seeing multiple instances of a single message being sent via Cloud Messaging using the Firebase Admin SDK, and users seeing duplicates on iOS. We have logs both on the server side, directly before and after on the server side, and on the client side upon receipt in a Notification Service Extension.

We've verified through these logs (tied to data from user screenshots), that the message is sent only once on our server, we receive a success response from the Firebase SDK, and the user receives that exact notification twice.

#### Server Logs:
```
16:08:16.542 | al-pool-2228 | INFO | w.SendNotificationWorker$ | 303 | 31ec5101-b43e-4519-99a1-9bb3650471c7: Successfully sent notification 2273480
16:08:16.537 | al-pool-7377 | INFO | .n.NotificationDispatcher | 342 | Notification id 2273480 sent status true
16:08:16.537 | al-pool-7377 | INFO | c.s.f.s.FirebaseService$ | 158 | Submitted notification to Firebase with messageId: projects/{redacted}/messages/{redacted} for notification id: 2273480
16:08:16.336 | al-pool-4602 | INFO | w.SendNotificationWorker$ | 92 | 31ec5101-b43e-4519-99a1-9bb3650471c7: Sending notification 2273480
```

#### Client Logs:
```
16:08:21.092 AM -0700 | INFO | {redacted} | NotificationService | did receive notification | notificationId = 2273480
16:08:21.091 AM -0700 | INFO | {redacted} | NotificationService | did receive notification | notificationId = 2273480
```

#### Relevant Code:

```
val messageId = FirebaseMessaging.getInstance.send(messageBuilder.build)
logger.info(s"Submitted notification to Firebase with messageId: $messageId for notification id: ${notificationId
.getOrElse(0L)}")
```

コントリビューションガイド

コントリビューションガイドを開く

調査の方向性

No repository file or test is named. Start at the FirebaseMessaging.getInstance.send call and compare the server message ID and send logs with the Notification Service Extension receipt logs. Done requires identifying whether duplication originates in the SDK, Firebase Cloud Messaging, or downstream delivery, with a reproducible verification or documented external cause.

索引モデルが issue の本文から書いたものです。

評価

技術スタック
firebase, java
領域
api, backend
issue の種類
バグ
難易度
4/5
見積もり時間
3〜5日
活発さ
停滞
明瞭さ
説明が足りない
初心者へのやさしさ
25/100

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。