[firebase_messaging] iOS notification onResume, onLaunch callback not working #2011

sandyara · 2020-02-17T14:15:22Z

We Tried creating notification in our flutter application and found it to be working perfectly fine in Android devices. When it comes to iOS device we are getting the notifications when the app is in the background or when it is not open, but on clicking them we aren't taken to the respective screens which are because the callbacks aren't called. Kindly help to fix this issue.

Versions Used:
Flutter: 1.12.13+hotfix.8
firebase_messaging: 6.0.9
Minimum iOS version supported: 10.0

To Reproduce
Steps to reproduce the behavior:

Created APNs Auth Key and Configured in Firebase
Enabled Capabilities
- Push Notifications
- Background Mode (Background Fetch and Remote Notifications)
Added below code in AppDelegate.m
if (@available(iOS 10.0, *)) {
[UNUserNotificationCenter currentNotificationCenter].delegate = (id) self;
}

Added below code in main.dart for listening onResume and onLaunch callbacks

_firebaseMessaging.configure(
  onMessage: (Map<String, dynamic> message) async {
    print('on message $message');
  },
  onResume: (Map<String, dynamic> message) async {
    print('on resume $message');
  },
  onLaunch: (Map<String, dynamic> message) async {
    print("OnLaunch Message");
  },
);
_firebaseMessaging.getToken().then((token) {
  print("NOTIFY TOKEN ${token}");
});

Note: I could not find the solution in #935 #1757 #1677 #23293

The text was updated successfully, but these errors were encountered:

DevarshRanpara · 2020-02-19T08:49:51Z

Facing same issue, getting notification if app is not open on screen.
I want to redirect user to specific screen on notification click, but i am getting 3 different cases for notification

1. If app is in foreground

I don't get notification.

2. If app is in background (Not terminated)

I get notification, but on notification click unable to redirect to specific screen.

3. If app is terminated

I get notification, and on notification click i am able to redirect to specific screen. (I want this to be happen in all above cases)

Here is more detail of my issue.

Edit

This one worked for me, now i am able to redirect user in any case.

as he suggests to remove above code from swift or objective C file and it should work.

if (@available(iOS 10.0, *)) {
  [UNUserNotificationCenter currentNotificationCenter].delegate = (id<UNUserNotificationCenterDelegate>) self;
}

AlexandreRoba · 2020-03-01T12:00:39Z

Was facing the same issue. Removing the swift check as mentionned by @DevarshRanpara resolved the issue.

iapicca · 2020-03-06T16:56:19Z

Hi @sandyara
did the proposed solution fix the issue for you
thank you

LOG-TAG · 2020-03-13T11:18:45Z

@AlexandreRoba @sandyara same issue exists or your comment solution working fine on firebase_messaging: ^6.0.12 ?
update:
tested working fine without that line

firebase_messaging docs are killing dev time :(

Jackcui68 · 2020-03-21T05:12:42Z

the same issue to me.
but as the doc,with the code ,it still works. where is the problem?

if (@available(iOS 10.0, *)) {
[UNUserNotificationCenter currentNotificationCenter].delegate = (id) self;
}

yazinsai · 2020-04-02T12:02:15Z

Had a similar issue -- including a minimal repo that can be used to demonstrate the erroneous behavior.

Describe the bug
Background notifications on iOS do not trigger the onLaunch / onResume methods in my Flutter app. I also do not see a badge / notification in the iOS notification center. Instead, I receive an onMessage trigger when the app is reopened

To Reproduce
I created a minimal repo that exhibits this behavior

Clone the repository here
Run the app on the iOS simulator
Note the Token: xxx value in the Debug Console
Move the app to the background
Trigger a notification using the following curl command:

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": "<TOKEN>"}'
curl https://fcm.googleapis.com/fcm/send -H "Content-Type:application/json" -X POST -d "$DATA" -H "Authorization: key=AAAALOSN_jE:APA91bEl5CscNyXpHRrz9F4lJJnFTlt9_FPwEOvI54Q6dr2eSuS00rryGiEXkABdhfMSHimkHrybSh7r3kfhVlciBpO3HYPa_kyT34eg-JE3bWsUg479OQK5ANzCTpJ-bvktN1AWw9j4"

Expected behavior
I expect a notification to appear in the iOS Notification Center, that when clicked will trigger the onResume method. Instead, no notification is presented.

Additional context
Output of flutter doctor -v:

[✓] Flutter (Channel stable, v1.12.13+hotfix.9, on Mac OS X 10.15.3 19D76, locale en-BH)
    • Flutter version 1.12.13+hotfix.9 at /Users/rock/Downloads/flutter
    • Framework revision f139b11009 (2 days ago), 2020-03-30 13:57:30 -0700
    • Engine revision af51afceb8
    • Dart version 2.7.2

 
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at /Users/rock/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 29.0.2
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
    • All Android licenses accepted.

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

[✓] Android Studio (version 3.5)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 42.1.1
    • Dart plugin version 191.8593
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)

[✓] VS Code (version 1.43.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.8.1

[✓] Connected device (1 available)
    • iPhone 11 • 11E9FF08-2E40-4812-A0A4-DC3B1E3398CC • ios •
      com.apple.CoreSimulator.SimRuntime.iOS-13-3 (simulator)

• No issues found!

Note: I could not find the solution in #935 #1757 #1677 or #2011

aizazzaheer · 2020-04-23T08:24:36Z

Facing the same issue, I've not added the iOS 10 code in AppDelegate.swift yet not able to receive anything on onlaunch and onresume handlers. Anyone facing something similar?

kristina-efros · 2020-04-27T07:57:16Z

Faced the same problem - instead of onResume and onLaunch callbacks an onMessage callback is received.

nominator · 2020-05-07T05:14:12Z

any update on this?

KarimMohamed20 · 2020-05-07T15:24:19Z

New Updates?

aloisdeniel · 2020-05-11T07:54:31Z

Any news? This is a really blocking issue I'm facing too. 😟

alustrement · 2020-05-11T08:05:20Z

+1 This bug is blocking the release of our product, thank you for your reactivity.

yazinsai · 2020-05-17T08:13:07Z

@iapicca the fix doesn't work. Please share an update with everyone on this thread.

acoutts · 2020-05-20T10:06:54Z

In my case I've got onMessage and onResume working as expected, but onLaunch does not fire in iOS. All 3 handlers working as expected in Android.

I have had a lot of issues with firebase messaging in iOS, and there are a ton of open issues about this. Is there another library that works as expected that we can use?

ziasultan2 · 2020-05-31T19:16:54Z

in my version v1.12.13+hotfix.9 fcm not working at all. before update it works without any problem. and now it's not giving any message but local notification working only. It's terrible lots of error in every version that really sucks that's why I stopped upgrading

MATTYGILO · 2020-06-21T14:48:26Z

has anyone worked out a fix?

spideyduulr · 2020-07-09T13:39:07Z

has anyone worked out a fix????????

emran92 · 2020-07-14T00:13:50Z

I'm on firebase_messaging: ^6.0.16

onResume and onLaunch on iOS is working. It works only when I click on the notification banner, but not when I click on the app icon. Is that an expected behaviour ?

Also the banner on the notification centre or lock screen wasn't showing up until I uploaded the app on Testflight.

Badge wasn't showing up until I added badge: 1 on the Additional options on cloud messaging dashboard

Here's my code:

_firebaseMessaging.configure(
        onMessage: (Map<String, dynamic> message) async {
      print('on Message:  $message');
      if (Platform.isIOS) {
        _title = message['title'];
        _message = message['body'];
      } else {
        _title = message['notification']['title'];
        _message = message['notification']['body'];
      }
    }, onResume: (Map<String, dynamic> message) async {
      print('on Resume $message');
      if (Platform.isIOS) {
        _title = message['title'];
        _message = message['body'];
      } else {
        _title = message['data']['title'];
        _message = message['data']['body'];
      }
    }, onLaunch: (Map<String, dynamic> message) async {
      print('onLaunch $message');
      if (Platform.isIOS) {
        _title = message['title'];
        _message = message['body'];
      } else {
        _title = message['data']['title'];
        _message = message['data']['body'];
      }
    });

RauschDev · 2020-07-16T07:38:17Z

Same problem for me, this bug is blocking the release of our product.

ziasultan2 · 2020-07-16T13:40:33Z

Check your configuration and rebuild again

…

On Thu, Jul 16, 2020 at 1:38 PM Marco Rausch ***@***.***> wrote: Same problem for me, this bug is blocking the release of our product. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#2011 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACQSUSDO2GJZRSM2FNNWLXTR32U7VANCNFSM4KWSQRCQ> .

ThomasTeoSY · 2020-07-28T08:23:09Z

The project I am working on is having the same issue and at last, we found that the root cause was due to format of the push notification is incorrect. I noticed that a lot of comments that I found from the internet asking people to put click_action inside the data content. But for my case, I put the click_action in the notification content and its works in my case.

Not working example:
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": ""}'

Working example:
DATA='{"notification": {"body": "this is a body","title": "this is a title", "click_action": "FLUTTER_NOTIFICATION_CLICK"}, "priority": "high", "data": {"id": "1", "status": "done"}, "to": ""}'

MobileMon · 2020-08-10T11:41:56Z

Its working fine for me. I suspect some of you may not be parsing the title and body correctly on iOS and that's where the error is occurring. Try using this code:

try{
     if (Platform.isAndroid) {
       if (message['notification'] != null){
         title = message['notification']['title'] ?? '';
         body = message['notification']['body'] ?? '';
       }
     }
     else if (Platform.isIOS) {
       if (message['aps'] != null){
         if (message['aps']['alert'] != null){
           title = message['aps']['alert']['title'] ?? '';
           body = message['aps']['alert']['body'] ?? '';
         }
       }
     }
     title = title == null ? '' : title;
     body = body == null ? '' : body;
   }
   catch(e){
     title = title == null ? '' : title;
     body = body == null ? '' : body;
   }

Ranjithsp6 · 2020-08-14T05:34:14Z

Its working fine for me. I suspect some of you may not be parsing the title and body correctly on iOS and that's where the error is occurring. Try using this code:

try{
     if (Platform.isAndroid) {
       if (message['notification'] != null){
         title = message['notification']['title'] ?? '';
         body = message['notification']['body'] ?? '';
       }
     }
     else if (Platform.isIOS) {
       if (message['aps'] != null){
         if (message['aps']['alert'] != null){
           title = message['aps']['alert']['title'] ?? '';
           body = message['aps']['alert']['body'] ?? '';
         }
       }
     }
     title = title == null ? '' : title;
     body = body == null ? '' : body;
   }
   catch(e){
     title = title == null ? '' : title;
     body = body == null ? '' : body;
   }

Hai @MobileMon ,
I am parsing only data message, Is there any difference for Android and IOS on parsing data message?
In my case on launch is not working only on IOS

vercorro · 2020-08-28T11:43:59Z

       title = message['aps']['alert']['title'] ?? '';
       body = message['aps']['alert']['body'] ?? '';

It's now working well thanks to you buddy.

Imgkl · 2021-01-04T07:28:57Z

Its working fine for me. I suspect some of you may not be parsing the title and body correctly on iOS and that's where the error is occurring. Try using this code:
try{
     if (Platform.isAndroid) {
       if (message['notification'] != null){
         title = message['notification']['title'] ?? '';
         body = message['notification']['body'] ?? '';
       }
     }
     else if (Platform.isIOS) {
       if (message['aps'] != null){
         if (message['aps']['alert'] != null){
           title = message['aps']['alert']['title'] ?? '';
           body = message['aps']['alert']['body'] ?? '';
         }
       }
     }
     title = title == null ? '' : title;
     body = body == null ? '' : body;
   }
   catch(e){
     title = title == null ? '' : title;
     body = body == null ? '' : body;
   }
Hai @MobileMon ,
I am parsing only data message, Is there any difference for Android and IOS on parsing data message?
In my case on launch is not working only on IOS

Did you find how to parse only the data message? I'm also facing the same issue.

Imgkl · 2021-01-08T08:54:45Z

 if (Platform.isAndroid) {
    if (message['data'] != null) {
      screen = message['data']['screen'];
      docID = message['data']['docId'];
      title = message['data']['title'];
    }
  } else if (Platform.isIOS) {
    if (message != null) {
      screen = message['screen'];
      docID = message['docId'];
      title = message['title'];
    }
  } else {
    debugPrint("No message was received");
  }

This is how we should parse the data message.

Pauljohnson78 · 2021-02-15T13:30:18Z

Strange one indeed this.

Android

All working as expected.

iOS device (14.3)

Receiving notification (in tray) in both instances when app is not in foreground.
onResume() - onLaunch() - onResume() all fail to fire with no errors.

iOS simulator

Notifications are not visible in tray (expected behaviour).
onResume() - onLaunch() - onResume() all fire correctly and contain correct data (unexpected behaviour(at least for me)).

Anyone had any luck with this one yet?

I'll keep plugging away.

russellwheatley · 2021-04-23T09:41:34Z

Hey @sandyara, we're a few major versions removed since you raised this issue; 9.1.2. Could you please let me know if you see the same issue after upgrading, and following the latest documentation? The two platforms are very different on how notification are handled, and it is worth your time to carefully understand the expectations documented here.

google-oss-bot · 2021-05-04T01:03:26Z

Hey @sandyara. We need more information to resolve this issue but there hasn't been an update in 7 weekdays. I'm marking the issue as stale and if there are no new updates in the next 7 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

sandyara added the type: bug Something isn't working label Feb 17, 2020

This was referenced Mar 6, 2020

[firebase_messaging] notification title/body is missing for onResume and onLaunch #2012

Closed

[Firebase Messaging Flutter] onResume and onLaunch callbacks are not called on Android #2042

Closed

iapicca added the impact: crowd Affects many people, though not necessarily a specific customer with an assigned label. (P2) label Mar 6, 2020

iapicca added the blocked: customer-response Waiting for customer response, e.g. more information was requested. label Mar 6, 2020

yazinsai mentioned this issue Apr 2, 2020

[firebase_messaging] onLaunch/onResume not triggered for background notifications on iOS #2284

Closed

Ehesp added the plugin: messaging label Apr 22, 2020

iapicca removed the blocked: customer-response Waiting for customer response, e.g. more information was requested. label May 20, 2020

russellwheatley added the blocked: customer-response Waiting for customer response, e.g. more information was requested. label Apr 23, 2021

google-oss-bot added the Stale Issue with no recent activity label May 4, 2021

Salakar closed this as completed May 6, 2021

firebase locked and limited conversation to collaborators Jun 6, 2021

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[firebase_messaging] iOS notification onResume, onLaunch callback not working #2011

[firebase_messaging] iOS notification onResume, onLaunch callback not working #2011

sandyara commented Feb 17, 2020 •

edited

Loading

DevarshRanpara commented Feb 19, 2020 •

edited

Loading

AlexandreRoba commented Mar 1, 2020

iapicca commented Mar 6, 2020

LOG-TAG commented Mar 13, 2020 •

edited

Loading

Jackcui68 commented Mar 21, 2020

yazinsai commented Apr 2, 2020 •

edited

Loading

aizazzaheer commented Apr 23, 2020 •

edited

Loading

kristina-efros commented Apr 27, 2020

nominator commented May 7, 2020

KarimMohamed20 commented May 7, 2020

aloisdeniel commented May 11, 2020

alustrement commented May 11, 2020

yazinsai commented May 17, 2020

acoutts commented May 20, 2020

ziasultan2 commented May 31, 2020

MATTYGILO commented Jun 21, 2020

spideyduulr commented Jul 9, 2020

emran92 commented Jul 14, 2020 •

edited

Loading

RauschDev commented Jul 16, 2020

ziasultan2 commented Jul 16, 2020 via email

ThomasTeoSY commented Jul 28, 2020 •

edited

Loading

MobileMon commented Aug 10, 2020

Ranjithsp6 commented Aug 14, 2020

vercorro commented Aug 28, 2020

Imgkl commented Jan 4, 2021

Imgkl commented Jan 8, 2021

Pauljohnson78 commented Feb 15, 2021

russellwheatley commented Apr 23, 2021 •

edited

Loading

google-oss-bot commented May 4, 2021

[firebase_messaging] iOS notification onResume, onLaunch callback not working #2011

[firebase_messaging] iOS notification onResume, onLaunch callback not working #2011

Comments

sandyara commented Feb 17, 2020 • edited Loading

DevarshRanpara commented Feb 19, 2020 • edited Loading

1. If app is in foreground

2. If app is in background (Not terminated)

3. If app is terminated

Edit

AlexandreRoba commented Mar 1, 2020

iapicca commented Mar 6, 2020

LOG-TAG commented Mar 13, 2020 • edited Loading

Jackcui68 commented Mar 21, 2020

yazinsai commented Apr 2, 2020 • edited Loading

aizazzaheer commented Apr 23, 2020 • edited Loading

kristina-efros commented Apr 27, 2020

nominator commented May 7, 2020

KarimMohamed20 commented May 7, 2020

aloisdeniel commented May 11, 2020

alustrement commented May 11, 2020

yazinsai commented May 17, 2020

acoutts commented May 20, 2020

ziasultan2 commented May 31, 2020

MATTYGILO commented Jun 21, 2020

spideyduulr commented Jul 9, 2020

emran92 commented Jul 14, 2020 • edited Loading

RauschDev commented Jul 16, 2020

ziasultan2 commented Jul 16, 2020 via email

ThomasTeoSY commented Jul 28, 2020 • edited Loading

MobileMon commented Aug 10, 2020

Ranjithsp6 commented Aug 14, 2020

vercorro commented Aug 28, 2020

Imgkl commented Jan 4, 2021

Imgkl commented Jan 8, 2021

Pauljohnson78 commented Feb 15, 2021

russellwheatley commented Apr 23, 2021 • edited Loading

google-oss-bot commented May 4, 2021

sandyara commented Feb 17, 2020 •

edited

Loading

DevarshRanpara commented Feb 19, 2020 •

edited

Loading

LOG-TAG commented Mar 13, 2020 •

edited

Loading

yazinsai commented Apr 2, 2020 •

edited

Loading

aizazzaheer commented Apr 23, 2020 •

edited

Loading

emran92 commented Jul 14, 2020 •

edited

Loading

ThomasTeoSY commented Jul 28, 2020 •

edited

Loading

russellwheatley commented Apr 23, 2021 •

edited

Loading