Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Duplicate Notifications Delivered through FC

Open
#863 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
firebase, java
Domain
api, backend

Research direction

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.

Written by the indexing model from the issue text.

Description

api: messaging
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)}")
Dominant language
Java
Stars
620
Forks
305
Avg merge
3h 23m
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from firebase/firebase-admin-java

All issues in firebase/firebase-admin-java

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.