Firebase send push notification twice

Question

I wrote a very simple android app to test firebase push notification and I get one notification twice.

this is the manifest service:

<service
        android:name="com.google.firebase.messaging.FirebaseMessagingService">
        <intent-filter>
            <action android:name="com.google.firebase.MESSAGING_EVENT"/>
        </intent-filter>
    </service>
    <service
        android:name="com.google.firebase.iid.FirebaseInstanceIdService">
        <intent-filter>
            <action android:name="com.google.firebase.INSTANCE_ID_EVENT"/>
        </intent-filter>
    </service>

this is the app gradle:

    compile 'com.google.android.gms:play-services:9.0.0'
    compile 'com.google.firebase:firebase-core:9.0.0'
    compile 'com.google.firebase:firebase-messaging:9.0.0'
}
apply plugin: 'com.google.gms.google-services'

and here is the project level gradle:

classpath 'com.google.gms:google-services:3.0.0'

Could you give us a portion code wheren messaging is handled ?. The error could be from that part. — ישו אוהב אותך, Jul 03 '16 at 05:54
@isnotmenow this is all of code that related to firebase except google-services.json — Siavash Abdoli, Jul 03 '16 at 06:06
there is should be a receiving class service in your android code, something like MyFirebaseMessagingService.java. — ישו אוהב אותך, Jul 03 '16 at 06:20
@isnotmenow You can see that I use basic class instead of My*.java — Siavash Abdoli, Jul 03 '16 at 06:34
I'm sorrry. It's turn out that you use FirebaseMessagingService.java. Take a look at that class. — ישו אוהב אותך, Jul 03 '16 at 06:58
You need to be sure that the device is not being registered more than once. I once had that mistake, deleting duplicates solved the problem for me. — Omolara, Jul 03 '16 at 15:57
@Omolara I think you are right an I registered twice but how to avoid this? — Siavash Abdoli, Jul 04 '16 at 09:42
@SiavashA You can store a boolean or a value that makes you know when the device is successfully registered. Then you check this value before initiating a new registration. — Omolara, Jul 04 '16 at 10:59
@SiavashAbdoli I'm also getting a similar kind of multiple notification but after a period of time. Not 2 notifications at a time. Any idea? — Sachin Prasad, Oct 31 '18 at 08:17
@SachinPrasad I don't know maybe server send it again after one fail and it cause duplication. — Siavash Abdoli, Nov 02 '18 at 19:24

score 10 · Accepted Answer · answered Jul 04 '16 at 13:48

It looks like you are using com.google.android.gms:play-services:9.0.0 (which includes play-services-gcm) and com.google.firebase:firebase-messaging:9.0.0

FCM from firebase-massaging automatically registers an Instance ID token (device ID) so if you have logic that registers for a token in your app it is likely that you are registering twice. This could account for you receiving multiple notifications. More generally though you should not use FCM and GCM in the same app for exactly this reason. So if you are going to use FCM you should remove GCM from your app.

Also, using play-services includes all the play-services-x APIs like play-services-gcm and play-services-drive etc. So always use the split libraries like play-services-x instead of just play-services.

If the device is registered twice in a production app . Please suggest solution for it? — Nitin, Feb 27 '18 at 07:28
You also need to make sure you clean your build to remove all GCM related classes This worked for me https://stackoverflow.com/questions/48785262/receiving-the-fcm-notifications-multiple-times-on-nougat/49177709#49177709 — amitfr, Mar 08 '18 at 16:18

score 5 · Answer 2 · answered Sep 13 '16 at 10:12

5

For me it was a 3th party sdk that was using GCM while our app was using FCM. Registering with both services will give you two notifications.

(Also I was calling super.onMessageReceived(remoteMessage) in my FirebaseMessagingService causing a third notification to appear :p

answered Sep 13 '16 at 10:12

Tom Bevelander

1,686
1
22
31

seems one 3th party sdk use GCM and i don't know wichone :D how to find that? – Siavash Abdoli Sep 25 '16 at 12:25
Use logic. Most libraries don't need GCM. Big (payed) services with admin panels or with build in chat. Things like Parse, Intercom, payment services etc. could use it. – Tom Bevelander Sep 26 '16 at 11:42
Also: check this question: http://stackoverflow.com/questions/21645071/using-gradle-to-find-dependency-tree – Tom Bevelander Sep 26 '16 at 11:47
For me it was AndroidJobs which is using GCM to schedule Notification to older devices. – pratham kesarkar Sep 28 '17 at 07:13
Thanks for that (Also...) - that was exactly why I was seeing two :-) – karora Jun 17 '19 at 22:12

score 2 · Answer 3 · answered Sep 07 '16 at 11:25

The accepted answer did not work for me. Below is what worked:

I used data-messages instead of display-messages so that even if the app is in foreground or background, the only single notification will appear.

Replace

{
      "to": "/topics/journal",
      "notification": {
        "title" : "title",
        "text": "data!",
        "icon": "ic_notification"
       }
}

With

{
  "to": "/topics/dev_journal",
   "data": {
       "text":"text",
       "title":"",
       "line1":"Journal",
       "line2":"刊物"
   }
}

Reference : How to handle notification when app in background in firebase

YES! The second example fires the onbackgroundmessage function.. more here: https://github.com/firebase/quickstart-js/issues/71 — Martin Zvarík, Jun 11 '18 at 21:53

score 1 · Answer 4 · answered Jun 08 '17 at 12:44

1

I was having the same problem when application was in background or closed (and sending both notification and data). Caused by requesting old GCM permissions in AndroidManifest.xml

Take a look at https://stackoverflow.com/a/44435980/1533285

answered Jun 08 '17 at 12:44

jlbofh

433
5
7

score 1 · Answer 5 · answered Sep 08 '19 at 10:22

I had to remove

<receiver android:name="com.google.android.gms.gcm.GcmReceiver" 
android:exported="true" android:permission="com.google.android.c2dm.permission.SEND"> 
  <intent-filter> <action android:name="com.google.android.c2dm.intent.RECEIVE" /> 
  <category android:name="${applicationId}" /> 
  </intent-filter> 
</receiver>

from AndroidManifest.xml

This worked for me, thanks

score 0 · Answer 6 · edited Sep 14 '22 at 14:16

0

Use in build gradle file

compile 'com.google.firebase:firebase-core:10.2.1'
compile 'com.google.firebase:firebase-messaging:10.2.1'

and use handleIntent() in receiver.

edited Sep 14 '22 at 14:16

jmizv

1,172
2
11
28

answered Jun 22 '17 at 11:28

Mahesh

95
1
4

Firebase send push notification twice

6 Answers6

Linked