[firebase_messaging] onMessage/onResume is called twice on Android/iOS

[woprandi]

Describe the bug
The onMessage callback is always called twice

To Reproduce
Steps to reproduce the behavior:

1. Setup the plugin, do a print statement in the onMessage callback
2. Keep the app in the foreground
3. Send a FCM message
4. 2 print on the console

Expected behavior
Only one print on the console

Additional context
I don' t have the same issue with onBackgroundMessage. It's called once as expected

[dhakadv06]

Facing same issue. onResume and onLaunch works fine but onMessage triggers twice.

[brian2694]

Facing same issue.!

[hoahuathien]

Facing the same problem with onMessage and onResume.

[rodrigolmacedo]

Same issue here, its is boring, in other app with other version the bug dont occurs T_T

[scognito]

I confirm (firebase messaging 6.0.9, and flutter 1.12.13+hotfix.5)
but it happens only on Android, not iOS.

[eyoeldefare]

Only on the android, it seems to me. Its easy to handle programmatically but not sure if there's a clean way to deal with it.

[CoderJava]

Facing same issue.

[woprandi]

I confirm it's only on Android

[woprandi]

onResume is also called twice

[sergitovar91]

Here the same issue, I get duplicate notifications on android (onResume and OnMessage). Here you will find all my details. It is the default flutter project with firebase firebase_messaging: ^6.0.9

Output:
W/FirebaseMessaging( 7129): Unable to log event: analytics library is missing
W/FirebaseMessaging( 7129): Unable to log event: analytics library is missing
I/flutter ( 7129): onMessage: {notification: {title: prueba, body: prueba}, data: {click_action: FLUTTER_NOTIFICATION_CLICK}}
I/flutter ( 7129): onMessage: {notification: {title: prueba, body: prueba}, data: {click_action: FLUTTER_NOTIFICATION_CLICK}}

flutter.txt
code.txt

[janosdupai]

same issue on iOS. onMessage called twice with different message ID, so there could be the issue on server side.
I double checked that my php call run only once, but somehow I received 2 message. In both cases: foreground and background too....

[EverestBoy]

Same here, on Message is called twice, flutter team are you listening?

[woprandi]

@janosdupai I don't have this issue on iOS. I tested again today

[janosdupai]

@woprandi
I use Firebase Cloud Message for a Flutter app.

I try to trigger a push notification with php code. It give me a success: 1 result, but on my device I always receive 2 message with the same title&body but different message ID (which is provided by google firebase).

I double checked, that I trigger this function only once on a server side.

my code on the server

    $url = 'https://fcm.googleapis.com/fcm/send';
     $msg = array
          (
                'body'  => $message,
                'title' => $title,
                        'badge' => 1,/*Default sound*/
                        'sound' => 'default',
          );
    $fields = array
            (
                'registration_ids' => $id,
                'notification'  => $msg
            );

    $fields = json_encode ( $fields );

    $apiKey = 'XXXXXXX'; //IOS

    $headers = array (
            'Authorization: key='.$apiKey,
            'Content-Type: application/json'
    );

    $ch = curl_init ();
    curl_setopt ( $ch, CURLOPT_URL, $url );
    curl_setopt ( $ch, CURLOPT_POST, true );
    curl_setopt ( $ch, CURLOPT_HTTPHEADER, $headers );
    curl_setopt ( $ch, CURLOPT_RETURNTRANSFER, true );
    curl_setopt ( $ch, CURLOPT_SSL_VERIFYPEER, false );
    curl_setopt ( $ch, CURLOPT_POSTFIELDS, $fields );

    $result = curl_exec ( $ch );
    curl_close ( $ch );
        echo $result;

I tried to trigger this from Terminal, which worked fine, and sent only 1 message. My terminal code:

DATA='{"notification": {"body": "this is a body","title": "this is a title"}, "priority": "high", "data": {"click_action": "FLUTTER_NOTIFICATION_CLICK", "id": "1", "status": "done"}, "to": "MYDEVICETOKEN"}'
curl https://fcm.googleapis.com/fcm/send -H "Content-Type:application/json" -X POST -d "$DATA" -H "Authorization: key=XXXXXXXXX"

[woprandi]

@janosdupai Can you check the FCM response via curl -i ?

[janosdupai]

@woprandi

{"multicast_id":8502274311835153380,"success":1,"failure":0,"canonical_ids":0,"results":[{"message_id":"1579683773320267"}]}

I receive this message_id in flutter app, but I receive another one in a small delay (with same message title and body)....

on flutter console

flutter: {status: done, id: 1, click_action: FLUTTER_NOTIFICATION_CLICK, google.c.a.e: 1, gcm.message_id: 1579683773320267, aps: {alert: {title: This is title #1, body: here is a message. message}, sound: default}}
flutter: {status: done, id: 1, click_action: FLUTTER_NOTIFICATION_CLICK, google.c.a.e: 1, gcm.message_id: 1579685542411682, aps: {alert: {title: This is title #1, body: here is a message. message}, sound: default}}

[CoderJava]

I'm test used terminal but the result it's same. onMessage is called twice. I'm testing on Android device.

[scognito]

@woprandi

{"multicast_id":8502274311835153380,"success":1,"failure":0,"canonical_ids":0,"results":[{"message_id":"1579683773320267"}]}

I receive this message_id in flutter app, but I receive another one in a small delay (with same message title and body)....

on flutter console

flutter: {status: done, id: 1, click_action: FLUTTER_NOTIFICATION_CLICK, google.c.a.e: 1, gcm.message_id: 1579683773320267, aps: {alert: {title: This is title #1, body: here is a message. message}, sound: default}}
flutter: {status: done, id: 1, click_action: FLUTTER_NOTIFICATION_CLICK, google.c.a.e: 1, gcm.message_id: 1579685542411682, aps: {alert: {title: This is title #1, body: here is a message. message}, sound: default}}

I receive it two times even from terminal

[sudip92]

Facing same issue with firebase_messaging: ^6.0.9. onMessage and onResume called multiple times

[eyoeldefare]

Same here, on Message is called twice, flutter team are you listening?

Can you imagine how many issues there are under this package? You need to be more appreciative of their craft bro. They can't solve everything overnight, give them some time.

[woprandi]

After fast investigation, the method onAttachedToEngine of the class FirebaseMessagingPlugin, which call registerReceiver, is called twice. That explain the double call.
I will try to continue to investigate but I'm not an expert

[woprandi]

A working workaround :

class MainActivity: FlutterActivity() {
   /*  override fun configureFlutterEngine(@NonNull flutterEngine: FlutterEngine) {
        GeneratedPluginRegistrant.registerWith(flutterEngine);
    }*/
}

[cayau-wamsa]

For me, works on update Flutter version 1.17.5 and firebase_messaging: ^6.0.16

[fnicastri]

I'm facing the same issue on iOS

[rivetingpeppermint]

Still facing the same issue on both Android and iOS. I'm using firebase_messaging: ^6.0.16 and Flutter 1.17.5.

[Chethansmash7]

I think I solved the issue.But I need to be sure as to what steps you are following.Those who have the issue please reply to this comment with the steps by step procedure...

[fnicastri]

@Chethansmash7

1. Clone this repo
2. change app id and put the new GoogleService-Info.plist in the project
3. build packages/firebase_messaging/example
4. send a notification while the app is in foreground
5. onMessage get called twice

flutter: onMessage: {body: Body, google.c.sender.id: 276852428296, google.c.a.e: 1, click_action: FLUTTER_NOTIFICATION_CLICK, aps: {alert: {title: Title, body: Test notification}, content-available: 1}, title: title, gcm.message_id: 1594807744573443, priority: high, content_available: true, gcm.notification.priority: high}

flutter: onMessage: {click_action: FLUTTER_NOTIFICATION_CLICK, google.c.sender.id: 276852428296, google.c.a.e: 1, content_available: true, aps: {alert: {title: Title, body: Test notification}, content-available: 1}, title: title, gcm.message_id: 1594807744573443, body: Body, priority: high, gcm.notification.priority: high}

Flutter doctor

[✓] Flutter (Channel stable, v1.17.5, on Mac OS X 10.15.5 19F101, locale en-US)
    • Flutter version 1.17.5 at /Users/cico/src/flutter
    • Framework revision 8af6b2f038 (2 weeks ago), 2020-06-30 12:53:55 -0700
    • Engine revision ee76268252
    • Dart version 2.8.4

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.0)
    • Android SDK at /Users/cico/Library/Android/sdk
    • Platform android-30, build-tools 30.0.0
    • ANDROID_SDK_ROOT = /Users/cico/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.5)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.5, Build version 11E608c
    • CocoaPods version 1.9.3

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 47.1.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

Can you share your solution?

[fnicastri]

I've noticed that the callback onMessage got called twice in FLTFirebaseMessagingPlugin.m

commenting out

if #available(iOS 10.0, *) {
  UNUserNotificationCenter.current().delegate = self as? UNUserNotificationCenterDelegate
}

did the trick.
But obviously it is just a work around, I'm not aware of the possible repercussions.

The flow is:

1. (BOOL)application:(UIApplication *)application didReceiveRemoteNotification:(NSDictionary *)userInfo fetchCompletionHandler:(void (^)(UIBackgroundFetchResult result))completionHandler
   get called and
2. it calls void)didReceiveRemoteNotification:(NSDictionary *)userInfo
3. - (void)userNotificationCenter:(UNUserNotificationCenter *)center willPresentNotification:(UNNotification *)notification withCompletionHandler:(void (^)(UNNotificationPresentationOptions))completionHandler NS_AVAILABLE_IOS(10.0) get called
4. and it call a second time [_channel invokeMethod:@"onMessage" arguments:userInfo]

[rivetingpeppermint]

I tried @fnicastri's workaround and it works for onMessage, but onResume is still called twice on iOS. onResume is called when the app is still in the background as well as when the app is brought to the foreground. Is it supposed to be this way? From reading the documentation, I thought onResume will only be called when the app is brought to the foreground, and not when it's in the background too.

[fnicastri]

@rivetingpeppermint @TahaTesser
Yes, digging more I noticed the same issue.
This is a serious issue that makes notifications unusable.

[rivetingpeppermint]

I also just found out that when I run my app on iOS, onResume and onLaunch are called when we open the app normally (from the home screen, not from clicking the notification in the system tray). This behavior doesn't happen with Android. I used the iPad Pro (9.7-inch, running iOS 13.5.1) and iPhone 7 (running iOS 12.4.1).

[fnicastri]

@TahaTesser
Thanks for reopening this bug.
you could change the platform tag too and maybe the title.

[hasanzia1993]

I confirm it's only on Android

it on iOS too

[HUYTHAINGUYEN]

Does anyone have a workaround for this problem yet?

[eyoeldefare]

Does anyone have a workaround for this problem yet?

init firebase only once, it worked for me

[fnicastri]

Does anyone have a workaround for this problem yet?

init firebase only once, it worked for me

Can you explain it?

[ollyde]

It's fixed with the new version. I'm using this current configuration: (Don't use carets it's not good)

  firebase_core: 0.5.0
  firebase_auth: 0.18.0
  firebase_messaging: 7.0.0

Be aware there is now some additional Android setup 👎

[rivetingpeppermint]

@OllyDixon what additional setup?

[ollyde]

@rivetingpeppermint ahh sorry, it's on the github/pub page.

[fnicastri]

@OllyDixon @TahaTesser

It's fixed with the new version. I'm using this current configuration: (Don't use carets it's not good)

  firebase_core: 0.5.0
  firebase_auth: 0.18.0
  firebase_messaging: 7.0.0

Be aware there is now some additional Android setup 👎

It's not.
I still get onResume called twice on iOS. On Android it's fine now (no additional setup needed)
And if I add

if #available(iOS 10.0, *) {
  UNUserNotificationCenter.current().delegate = self as? UNUserNotificationCenterDelegate
}

I get nothing at all.

Using the example I get onMessage twice and onResume once.
Something is not working at all even with this new release.

[dppatel03]

firebase_core: 0.5.0
firebase_auth: 0.18.0
firebase_messaging: 7.0.0

I am getting same issue at iOS.

[kartercs]

Having the same issue on IOS for onMessage and onResume.
If it can help the second message object have the same informations as the first one but in different order like this :

{sender: ***, google.c.sender.id: ***, google.c.a.e: ***, click_action: FLUTTER_NOTIFICATION_CLICK, aps: {alert: {title: ***, body: ***}, sound: ***, content-available: ***}, sound: ***, content_available: ***, priority: ***, gcm.message_id: ***, gcm.notification.priority: ***}

{click_action: FLUTTER_NOTIFICATION_CLICK, sender: ***, google.c.a.e: ***, google.c.sender.id: ***, aps: {alert: {title: ***e, body: ***}, sound: default, content-available: 1}, sound: ***, gcm.message_id: ***, priority: ***, content_available: ***, gcm.notification.priority: ***}

[salva73]

Same issue here, using flutter v. 1.22.0 and firebase messaging 7.0.3, this behavior happens when I use "content-available": true

[TahaTesser]

@salva73
Could you please file a new issue with all the steps