• Breaking change the SelectNotificationCallback and DidReceiveLocalNotificationCallback typedefs now map to functions that returns void instead of a Future<dynamic>. This change was done to better communicate the plugin doesn't actually await any asynchronous computation and is similar to how button pressed callbacks work for Flutter where they are typically use VoidCallback
• Updated example app to show how to display notification where a byte array is used to specify the icon on Linux
• Breaking change the value property of the Importance class is now non-nullable
• Breaking change the FlutterLocalNotificationsPlugin.private() constructor that was visible for testing purposes has been removed. The plugin now uses the defaultTargetPlatform property from the Flutter framework to determine the platform an application running on. This removes the need for depending on the platform package. To write tests that require a platform-specific implementation of the plugin, the debugDefaultTargetPlatformOverride property can be used to do so
• Breaking change fixed issue 1306 where an Android notification channel description should have been optional. This means the description property of the AndroidNotificationChannel class and the channelDescription property of the AndroidNotificationDetails class are now named parameters
• Breaking change the AndroidIcon class is now a generic class i.e. AndroidIcon<T> and it's icon property has been renamed to data. With this change, the type of the icon property that belongs to the Person class has changed from AndroidIcon? to AndroidIcon<Object>?
• [Android] Added the ByteArrayAndroidIcon class that implements the AndroidIcon<T> class. This allows using a byte array to use as the icon for a person in a message style notification. A ByteArrayAndroidIcon.fromBase64String() named constructor is also available that will enable this using a base-64 encoded string. Thanks to the PR from Alexander Petermann
• [Android] Android 12 support
• Restored Linux support
• Fixed grammatical errors in readme. Thanks to PR from Aneesh Rao
• Plugin now uses the clock package for internal logic that relies on geting the current time, such as validating that the date for a scheduled notification is set in the future