The plugin should provide the ability to specify custom notification actions. However, this will depends on the Flutter engine being able to support headless-Dart code as per https://github.com/flutter/flutter/issues/6192 and https://github.com/flutter/flutter/issues/3671

It appears Android support is there but will wait to see on if the engine can support it for iOS applications, and for Flutter to provide abstractions to access the functionality. Without the support being added in, then this won't work for scenarios like when the application has been terminated as the logic associated with the action would've been defined in Dart.

Update with remaining work (IMO)

• [x] rework callbacks to deal with "foreground" and "background" notification actions. See https://github.com/MaikuB/flutter_local_notifications/pull/1489 for more detailed discussion
• [x] potential issue with setting notification categories affecting ability to see the notification actions https://github.com/MaikuB/flutter_local_notifications/issues/1481

Note that last two perhaps could be omitted given market share and those require using deprecated APIs

Edit:

• there is headless execution on iOS but there are limitations at the moment. See https://github.com/flutter/flutter/issues/23904. Upvote the issue on the Flutter repo if this concerns you to help the Flutter team prioritise
• removed tasks on supporting older iOS and macOS versions given market share and those require using deprecated APIs

This PR addresses #17 - and includes a very basic implementation for iOS & Android.

A click on the notification will launch (if not already running) a separate Flutter engine, which initializes a callback dispatcher. The dispatcher function then sets up platform communication for other plugins and starts listening to a event channel for existing or additional notification click events.

Screenshots

Android:

Simple actions:

Text input actions to collect user entered text:

iOS:

macOS:

Simple actions:

Text input actions to collect user entered text:

The PR is in early stage to gather feedback on the basic use case by others.

Feedback requested

Please support this PR by testing it in your own App and comment with missing features / use cases.

To use it, add the following to your pubspec.yaml file:

dependency_overrides:
  flutter_local_notifications:
    git:
      url: https://github.com/ened/flutter_local_notifications.git
      path: flutter_local_notifications
      ref: 17-notification-actions
  flutter_local_notifications_platform_interface:
    git:
      url: https://github.com/ened/flutter_local_notifications.git
      path: flutter_local_notifications_platform_interface
      ref: 17-notification-actions

The documentation is still very incomplete, therefore please refer to the example project of this branch.

Open tasks

• [x] Text input & predefined action (Android) support
• [x] Android: Notification Actions text color: https://stackoverflow.com/questions/41073294/how-to-change-notification-action-text-color-in-android-n
• [ ] Documentation
• [ ] Test coverage
• [x] macOS support
• [x] metadata/payload accessible in action handler
• [x] autoCancel property for android notification action handler that dismisses the notification (feature parity with iOS)

Describe the bug The follwoing phenomena occur on android phones and I am not sure whether they would occur on iOS phones or not.

1. 'showDailyAtTime()' dose not work as expected, which should have pushed the notification at a specific time but failed;
2. Two apps invoking this plugin and running on a same Android phone seems tending to push notifications at the same time using 'showDailyAtTime()';
3. Very often, when pushing notifications, more than 1 notifications are pushed at the same time with 'showDailyAtTime()';

These issues have nothing to do with the phone model, as I have tried on different phones. In addition, I do not know why the built-in example code of "flutter_local_notifications" cannot work, as every time I lauched the App, it crashes and prompted "flutter_local_notifications_example 已停止。"

To Reproduce

This plugin used to work normally, but after I did some things like: upgrading the flutter SDK and tweaking the codes in gradle file to suite the new SDK and updated plugins, these bugs appeared. I tried to rewind everything to somewhere the code can work normally, which includes getting back the old flutter SDK version and the gitted code, but all failed.

What do I need If possible, please simply give me some clues why these phenomena happens. Thanks so much for your help.

I'm trying to fire a notification when the background location callback returns. But this leads into the following exception: Unhandled Exception: MissingPluginException(No implementation found for method initialize on channel dexterous.com/flutter/local_notifications)

I know, that there was an issue with the same problem before, but there was no solution provided.

While i was fininshing my fork to implement a basic Action Button functionality, i finded a high possible security issue for every app using the flutter_local_notification.

Causes:

The payload returned between the native code and Flutter method callback is plain text. That means the app above should extract that plain text value to process it. Taking note that some of key informations, such notification id, are lost in MethodCall transition process, the actual scenario estimulate the app developer to put complex references over plain text payload do caputure it after the user taps on notification.

If that app allows another users with low priviledge to send notifications to someone, now they have access to send malicious strings through notifications that could reach internal process steps and allow code or parameters injection to manipulate the app.

Example

Consider a App using a json encoded string over payload to recovery its references after the user tap a notification. A malicious user could inject another json encoded string (with manipulated parameters or extra fields) through the body message or even on a input text response, such as Android´s RemoteInput. After the tap event, the malicious code could be processed and interpreted, allowing the user to reach unauthorized pages or functionalities. such as expired promotion codes, privated messages, etc.

Solution

The solution is to return over MethodCall flutter listener an object and not a plain text. As the layers between android and ios cannot communicate with dart files passing memory object ( because they are made from different technologies ) we gonna pass the object encoded, containing the payload string escaped, and decode the object to memory on flutters ´s side, without need to check the payload, considering that every user input contains unsafe information.

Under the object used to transfer the information, we gonna put the others notification information, such notification_id, etc.

The difference bettween the plugin doing that oposes the app is the pluggin extends to native code, where is completely possible to distinguish parameters from payload without need to process and interpret the payload content.

But the obvious consequence is the new returned payload is totaly different from the old one. The new method is naturaly incompatible with App who readed plain text from the olders versions.

So i propose to create a copy of onSelectNotification, on called onReceiveNotification, passing a object to the receiver event, and also to mark the old onSelectNotification as deprecated and unsecure. That way the new notification plugin will not becom totaly incompatible with those apps, the developers will be warned about the danger and will keep receiving another updates until they change their codes.

So, what you guys think about that? there is a better way to do those changes?

It works perfectly while the app is running, but when the application is closed the function is not called.

The code can be found here https://github.com/GroovinChip/CallManager/blob/dev/lib/HomeScreen.dart

I can't provide a stacktrace because the issue only occurs while the app is not running.

If you'd be so kind as to provide quick assistance, I'd really appreciate it - I had to pull a crucial feature from production due to this bug.

Thanks!

The Desktop Notifications Specification is used as an implementation.

I have separated the Linux plugin package from the main plugin package. This is necessary to correctly implement the Dart version of the plugin without using native code. For example, dbus package is used to communicate with the Desktop Notifications Specification and a few more auxiliary packages that allow to access native methods/environment. Once this pull request is merged in the new version of the plugin, change the relative path to the package in pubspec.yaml: https://github.com/proninyaroslav/flutter_local_notifications/blob/ddc57043dcb6d68bd94d48b9fc601753ff4f899c/flutter_local_notifications/pubspec.yaml#L15

Implemented features:

• initialize() method and LinuxInitializationSettings.
• show() method and LinuxNotificationDetails.
• cancel(), cancelAll() methods.
• getCapabilities() method, which returns some of the capabilities implemented by the system notification service. Please see Desktop Notifications Specification#Backwards Compatibility.
• getSystemIdMap() method, that returns a Map with the specified notification id as the key and the id, assigned by the system, as the value. Because by specification, the system itself generates notification id, an [app id: system id] map is used, which is cached within the user session.

Non-implemented features:

• Notification actions. It's possible to implement them, but I didn't do this, because there is still no established/official API in the plugin. For example, one of the possible implementations that is not yet upstream https://github.com/MaikuB/flutter_local_notifications/pull/880.
• Scheduled/pending notifications. As mentioned here https://github.com/MaikuB/flutter_local_notifications/pull/1208#issuecomment-869552295, currently, the scheduler implementation is fraught with difficulties, because Linux doesn't have an appropriate API. As a possible option, we can consider interacting with systemd (similar to launchd on macOS) via D-Bus API of systemd (as done in the Desktop Notifications Specification). This will allow the scheduler to run as a system service. I haven't yet investigated how realistic it's to implement it in the plugin without changes from the application developer/user side.
• getNotificationAppLaunchDetails(). To respond to notification after the application is terminated, the application should be registered as DBus activatable (see DBusApplicationLaunching for more information), and register action before activating the application. This is difficult to do in a plugin because plugins instantiate during application activation, so getNotificationAppLaunchDetails can't be implemented without changing the main user application.

Testing the Desktop Notifications Specification in real-world conditions is difficult, because different Linux distributions and DE may or may not implement some of the specification things. For example, on GNOME, you can't set a timeout, custom sound, or screen location. Therefore, I wrote extensive tests that validate the request setmantics and format required by the Desktop Notifications Specification. For real world testing of notifications, I would recommend using different DEs such as GNOME (e.g Ubuntu or Fedora), KDE (e.g Kubuntu), XFCE (e.g Xubuntu), MATE (e.g Ubuntu MATE), etc.

I also ask you to pay attention to these two methods: https://github.com/proninyaroslav/flutter_local_notifications/blob/ddc57043dcb6d68bd94d48b9fc601753ff4f899c/flutter_local_notifications_linux/lib/src/typedefs.dart#L5 https://github.com/proninyaroslav/flutter_local_notifications/blob/ddc57043dcb6d68bd94d48b9fc601753ff4f899c/flutter_local_notifications_linux/lib/src/helpers.dart#L9 Because I split the Linux plugin version into a separate package, I had to copy these two methods for the plugin to work correctly. It might be worth leaving that as it is. Although you might consider moving the common methods into a separate package.

Hi,

I used to zonedSchedule to send notifications at the specific time, it works fine on the emulator but when I try different real devices and schedule notification at the specific time, there is no notification, crash, or error.

Here is my code:

tz.initializeTimeZones();

      var now = DateTime.now();

      var time2 = tz.TZDateTime(
        tz.local,
        now.year,
        now.month,
        now.day,
        _selectedTime.hour,
        _selectedTime.minute,
      );

      int notificationID = widget.newActivity.id;

      _flutterLocalNotificationsPlugin
          .zonedSchedule(
              notificationID, title, body, time2, generalNotificationDetails,
              uiLocalNotificationDateInterpretation:
                  UILocalNotificationDateInterpretation.absoluteTime,
              androidAllowWhileIdle: true)
          .then((value) {
        _setAlarm(widget.newActivity.id, _formattedTime);
        setState(() {
          _hasNotification = true;
        });
        print("notification created!");
      });

Hi MaikuB, I seem to be encountering an issue where when notifications are displayed and manually dismissed, upon restarting the device, when the phone boots up, all previous notifications that occurred while the phone was turned on suddenly all come in all at once. It's as if they were never really dismissed.

If I set a notification to fire at a specific time, it, fires, then I manually call "CancelNotification" on that single notification with that ID, even though this successfully removes the notification and dismisses it from the status bar, when I restart the phone, it reappears as if it were never canceled.

If I use "CancelAllNotifications" however, it does truly "cancel" it and previously dismissed notifications don't reappear upon restart, but obviously, I can continuously call "CancelAllNotifications" for a single notification because it will remove all the other unrelated notifications iv'e set up as well.

Any idea about this?

Describe the bug I have an app with 3 million downloads and flutter_local_notifications are the #1 issues on Crashlytics (not because of this plugin, but because Android itself sucks).

What I do is to fill the plugin Java code with try/catches to ignore errors so the app won't crash (the users will not receive notifications, but at least they can use the app).

Here are some logs (those are just examples: almost every point in this plugin crashes, including boot_received):

Fatal Exception: java.lang.RuntimeException: Unable to start receiver com.dexterous.flutterlocalnotifications.ScheduledNotificationReceiver: java.lang.NullPointerException: Attempt to write to field 'long android.app.Notification.when' on a null object reference
       at android.app.ActivityThread.handleReceiver(ActivityThread.java:3369)
       at android.app.ActivityThread.-wrap20(ActivityThread.java)
       at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1726)
       at android.os.Handler.dispatchMessage(Handler.java:102)
       at android.os.Looper.loop(Looper.java:154)
       at android.app.ActivityThread.main(ActivityThread.java:6776)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1518)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1408)

Caused by java.lang.NullPointerException: Attempt to write to field 'long android.app.Notification.when' on a null object reference
       at com.dexterous.flutterlocalnotifications.ScheduledNotificationReceiver.onReceive(ScheduledNotificationReceiver.java:32)
       at android.app.ActivityThread.handleReceiver(ActivityThread.java:3362)
       at android.app.ActivityThread.-wrap20(ActivityThread.java)
       at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1726)
       at android.os.Handler.dispatchMessage(Handler.java:102)
       at android.os.Looper.loop(Looper.java:154)
       at android.app.ActivityThread.main(ActivityThread.java:6776)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1518)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1408)

Fatal Exception: java.lang.RuntimeException: Unable to start receiver com.dexterous.flutterlocalnotifications.ScheduledNotificationReceiver: java.lang.NullPointerException: Attempt to invoke virtual method 'int java.lang.Integer.intValue()' on a null object reference
       at android.app.ActivityThread.handleReceiver(ActivityThread.java:3658)
       at android.app.ActivityThread.access$1400(ActivityThread.java:245)
       at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1839)
       at android.os.Handler.dispatchMessage(Handler.java:106)
       at android.os.Looper.loop(Looper.java:216)
       at android.app.ActivityThread.main(ActivityThread.java:7258)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:494)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:975)

Caused by java.lang.NullPointerException: Attempt to invoke virtual method 'int java.lang.Integer.intValue()' on a null object reference
       at com.dexterous.flutterlocalnotifications.FlutterLocalNotificationsPlugin.setupNotificationChannel(FlutterLocalNotificationsPlugin.java:634)
       at com.dexterous.flutterlocalnotifications.FlutterLocalNotificationsPlugin.createNotification(FlutterLocalNotificationsPlugin.java:130)
       at com.dexterous.flutterlocalnotifications.FlutterLocalNotificationsPlugin.showNotification(FlutterLocalNotificationsPlugin.java:688)
       at com.dexterous.flutterlocalnotifications.ScheduledNotificationReceiver.onReceive(ScheduledNotificationReceiver.java:45)
       at android.app.ActivityThread.handleReceiver(ActivityThread.java:3649)
       at android.app.ActivityThread.access$1400(ActivityThread.java:245)
       at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1839)
       at android.os.Handler.dispatchMessage(Handler.java:106)
       at android.os.Looper.loop(Looper.java:216)
       at android.app.ActivityThread.main(ActivityThread.java:7258)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:494)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:975)

Fatal Exception: java.lang.RuntimeException: Unable to start receiver com.dexterous.flutterlocalnotifications.ScheduledNotificationReceiver: java.lang.NullPointerException: Attempt to read from field 'java.lang.String com.dexterous.flutterlocalnotifications.models.NotificationDetails.channelId' on a null object reference
       at android.app.ActivityThread.handleReceiver(ActivityThread.java:4012)
       at android.app.ActivityThread.access$1500(ActivityThread.java:232)
       at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2025)
       at android.os.Handler.dispatchMessage(Handler.java:107)
       at android.os.Looper.loop(Looper.java:241)
       at android.app.ActivityThread.main(ActivityThread.java:7617)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:492)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:941)

Caused by java.lang.NullPointerException: Attempt to read from field 'java.lang.String com.dexterous.flutterlocalnotifications.models.NotificationDetails.channelId' on a null object reference
       at com.dexterous.flutterlocalnotifications.models.NotificationChannelDetails.fromNotificationDetails(NotificationChannelDetails.java:74)
       at com.dexterous.flutterlocalnotifications.FlutterLocalNotificationsPlugin.createNotification(FlutterLocalNotificationsPlugin.java:138)
       at com.dexterous.flutterlocalnotifications.FlutterLocalNotificationsPlugin.showNotification(FlutterLocalNotificationsPlugin.java:803)
       at com.dexterous.flutterlocalnotifications.ScheduledNotificationReceiver.onReceive(ScheduledNotificationReceiver.java:56)
       at android.app.ActivityThread.handleReceiver(ActivityThread.java:4003)
       at android.app.ActivityThread.access$1500(ActivityThread.java:232)
       at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2025)
       at android.os.Handler.dispatchMessage(Handler.java:107)
       at android.os.Looper.loop(Looper.java:241)
       at android.app.ActivityThread.main(ActivityThread.java:7617)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:492)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:941)

I previously used showDailyAtTime to set a daily reminder - that was a pretty nice API.

I saw it was deprecated, and now to add intervals was pretty rough..

• First you have to get a time zone, by initializing a database and calling either a platform call or getting a third party package.
• Then you have to be sure the TZDateTime, given the timezone location, has a date in the future ( or it will crash ), even though i'm only interested in the hour and seconds of the day.
• Then you have to pick the DateTimeComponents which only have two items.

This was a lot of work to get up and running. I think this could be improved upon.

Hi, actually I am using work manager and sending notifications when the app is closed. The progress one which was shown in the example works fine when the app is in the foreground or background(Means in Recent) and I got working it when the app is closed using WorkManager but for loop does not get executed. Without it Notification works properly even when app is closed. here is the example code from Workmanager().executeTask(...); all the dependencies has been initiated after that...

    for (decDuration = 0; decDuration >= durationElapsed.inSeconds; decDuration++) {
      await Future.delayed(const Duration(seconds: 1)); //here awaiting for 1 sec but no luck
      AppConstants.logger('Testing.....$decDuration');
      AndroidNotificationDetails and = AndroidNotificationDetails(
        'parked_vehicle',
        'Vehicle Parking Time Remaining',
        channelDescription:
            'This Notification will notify the user that vehicle\'s time of booking for the parking is about to expire.',
        importance: Importance.max,
        priority: Priority.max,
        channelShowBadge: false,
        ticker: 'parked_vehicle',
        color: Colors.blue,
        onlyAlertOnce: true,
        showProgress: true,
        progress: decDuration,
        maxProgress: totalDuration.inSeconds,
        visibility: NotificationVisibility.public,
      );
      NotificationDetails platformSpecificDetails =
          NotificationDetails(android: and);

      await flutterLocalNotificationsPlugin.show(
        nID,
        '${booking.vehicleNumber} is parked at ${booking.lotName}',
        'Parking is about to end in -- ${AppConstants.formatDuration(Duration(seconds: decDuration))}',
        platformSpecificDetails,
      );
    }

Please let me know if we need to do something more for executing for loop because without for loop await Future.delayed works. I have checked to delay for 3 sec, 3 times.

Hi, I am actually showing a notification that indicates the remaining time of the Booking of the Vehicle parked at the parking lot. eg. From Booking_Time = 2022-10-10 12:25 To Booking_Time = 2022-10-10 18:25

so the problem is, suppose the time remaining is 06:25:00. In the notification it starts properly but no matter what the value for chronometerCountDown = true/false the timer goes upward only. if chronometerCountDown = false it shows 06:25:00, 06:25:01, 06:25:02, 06:25:03...this is as expected if chronometerCountDown = true it shows -06:25:00, -06:25:01, -06:25:02, -06:25:03...going upward only

Below is my AndroidNOtificationDetails :: DateTime whenTimer = currentTime.subtract(durationElapsed); AndroidNotificationDetails and = AndroidNotificationDetails( 'parked_vehicle', 'Vehicle Parking Time Remaining', channelDescription: 'This Notification will notify the user that vehicle's time of booking for the parking is about to expire.', importance: Importance.max, priority: Priority.max, channelShowBadge: false, ticker: 'parked_vehicle', color: Colors.blue, onlyAlertOnce: true, when: whenTimer.millisecondsSinceEpoch, timeoutAfter: whenTimer.difference(DateTime.now()).inMilliseconds, usesChronometer: true, chronometerCountDown: true, visibility: NotificationVisibility.public, ongoing: true, );

I hope I have mentioned my problem properly.

NOTE: I have checked the example and it shows same behaviour when: DateTime.now().millisecondsSinceEpoch - 120 * 1000, usesChronometer: true, chronometerCountDown: true,

In short chronometerCountDown: true only adds the "-" sign nothing else.

How can I cancel a notification through groupKey? I have created multiple notifications with the same id and different groupKey. Now I want to cancel a notification that is specific to a particular groupKey.

I try to let my user send a silent notification if he wants to: For that I set presentSound to false:

  static Future _notificationDetails() async {
    //print("sound: " + sound.toString());
    return NotificationDetails(
      android: AndroidNotificationDetails(
        'channel id',
        'channel name',
        //'channel description',
        channelDescription: 'channel description',
        importance: Importance.max,
        playSound: false,
        sound: const RawResourceAndroidNotificationSound('sound'),
      ),
      iOS: const DarwinNotificationDetails(
        presentSound: false,
        sound: 'sound.aiff',
      ),
    );
  }

This works in foreground but not if the app is terminated. I always get the notification with sound. I tried with flutter_local_notifications 9.3.2 and 13.0.0. How can I create silent notifications?

As this repository hosts two packages, please ensure the PR title starts with the name of the package that it relates to using square brackets (e.g. [flutter_local_notifications]). The contribution guidelines can be found at https://github.com/MaikuB/flutter_local_notifications/blob/master/CONTRIBUTING.md. Please review this as it contains details on what to follow when submitting a PR.

With such a simple change, hopefully I did things correctly.

https://github.com/MaikuB/flutter_local_notifications/issues/1855

Forgive me if this is the incorrect way to suggest this - I'm incredibly grateful for the work you did https://github.com/MaikuB/flutter_local_notifications/pull/1740 and was hoping the same could be done to suppress warning when building for MACOS as well as we use both in production. Thanks for your time.