Michael Bui

#21 requires implementing all that's required for headless Dart execution to work and the functionality is less complex than doing custom actions. Makes it more easier to test headless Dart...

Are you referring to #21 around a callback when a notification is to be shown?

There is at least this callback, which isn't specific to a scheduled notification when the app is in the foreground https://developer.apple.com/documentation/usernotifications/unusernotificationcenterdelegate/1649518-usernotificationcenter I should clarify that I wasn't looking at #21...

@davystrong none at the moment. I previously tried to add headless execution of Dart code (this is relevant so code can be run even if the app is terminated) but...

i suspect you'll run into issues as headless execution relies on running on a background isolate but we also want actions to be able to run code on the main...

If you're not concerned with that then I'd suggest that you implement it in your own fork. I'd prefer the UI issue gets solved as well to avoid the scenario...

@vikramaggarwal13 Based on what I know, I don't think that is achievable. Doing custom layouts for notifications on each platform, requires using the way UI is done on that platform...

not at this stage, the reasons why have been discussed above already

To clarify i'm referring to via this plugin. an alternative that you look at writing code that uses platform channels yourself. This may likely require you to invoke the media...

@robindijkhof: it means when the app isn't running or has been killed/shutdown through whatever means (e.g. swiping up depending on the OS). Regarding updating the OP, there's actually a blocked...