- Breaking change calling
initializewill no longer trigger theonSelectNotificationif a notification was tapped on prior to callinginitialize. This was done as thegetNotificationAppLaunchDetailsmethod already provided a way to handle when an application was launched by a notification. Furthermore, callinginitializemultiple times (e.g. on different pages) would have previously caused theonSelectNotificationcallback multiples times as well. This potentially results in the same notification being processed again - Breaking change the
matchDateComponentsparameter has been renamed tomatchDateTimeComponents - Dates in the past can now be used with
zonedSchedulewhen a value for thematchDateTimeComponentsparameter has been specified to create recurring notifications. Thanks to the PR from Erlend for implementing this and the previous change - [Android] notification data is now saved to shared preferences in a background thread to minimise jank. Thanks to the PR from davidlepilote
- [Android] the
tagproperty has been added to theAndroidNotificationDetailsclass. This allows notifications on Android to be uniquely identifier through the use of the value of thetagand theidpassed to the method for show/schedule the notification - [Android] the optional
tagargument has been added to thecancelmethod for theFlutterLocalNotificationsPluginandAndroidFlutterLocalNotificationsPluginclasses. This can be used to cancel notifications where thetaghas been specified - [iOS][macOS] the
threadIdentifierproperty has been added to theIOSNotificationDetailsandMacOSNotificationDetailsclasses. This can be used to group notifications on iOS 10.0 or newer, and macOS 10.14 or newer. Thanks to the PR from Marcin Chudy for adding this and thetagproperty for Android notifications - The Android and iOS example applications have been recreated in Kotlin and Swift respectively
- Updated example application's dev dependency on the deprecated
e2efor integration tests to useintegration_testinstead - Bumped Flutter dependencies
- Example app cleanup including updating Proguard rules as specifying the rules for Flutter were no longer needed