flutter_local_notifications-v17.1.2

• [Android] fixed issue 2318 where an exception could occur on calling the getNotificationChannels() method from the AndroidFlutterLocalNotificationsPlugin class. This happened when Android found that the audio attributes associated with the channel was null. The plugin will now coalesce the null value to indicate that the usage of the audio is for notifications as per https://developer.android.com/reference/android/media/AudioAttributes#USAGE_NOTIFICATION. On the Dart side, this would correspond to the AudioAttributesUsage.notification enum value

flutter_local_notifications-v17.1.1

• [Android] fixes issue #2299 where within the range of the max integer value of epoch time passed to a messaging style would result in a casting exception

flutter_local_notifications-v17.1.0

• [Android] bigText has added to ActiveNotification that allows getting information about the longer text associated with a notification displayed using the big text style. Thanks to the PR from vulpeep
• [Android] added audioAttributesUsage to AndroidNotificationChannel. Thanks to the PR from Dithesh
• Fix description of the behaviour iOS pending notifications limit. Thanks to the PR from Amman Zaman
• Updated link in readme to Gradle desugaring setup. Thanks to the PR from James Allen

flutter_local_notifications-v17.0.1

• [iOS] updated privacy manifest to declare reason the plugin uses the User Defaults API. Thanks to the PR from Miya49-p0

flutter_local_notifications-v17.0.0

• [Android] Breaking change bumped compileSdk to 34 and updated readme to mention this
• Updated compileSdk and targetSdkVersion of example app to 34
• Important announcement given how both quickly both Flutter ecosystem and Android ecosystem evolves, the minimum Flutter SDK version will be bumped to make it easier to maintain the plugin. Note that official plugins already follow a similar approach e.g. have a minimum Flutter SDK version of 3.13. This is being called out as if this affects your applications (e.g. supported OS versions) then you may need to consider maintaining your own fork in the future
• Updated build status badge shown on readme to sync to recent changes on using GitHub Actions
• Fixed code snippet in readme related to handling the onDidReceiveLocalNotification callback. Thanks to the PR from Sanket Patel

flutter_local_notifications-v16.3.3

• [Android] added missing check on if SCHEDULE_EXACT_ALARM permission was granted when using the alarmClock as the AndroidScheduleMode
• Bumped device_info_plus dependency for example app, which means example app requires Flutter SDK version 3.3.0 or higher to run

flutter_local_notifications-v16.3.2

• [Android] fixed how native stack traces were obtained. Relates to issue 2088. Thanks to the PR from Jonas Uekötter

flutter_local_notifications-v16.3.1+1

• [iOS] added privacy manifest

flutter_local_notifications-v16.3.1

• Added missing acknowledgement for readme fix in 16.3.0
• [Android] fixed issue 2136 where notifications on scheduled using older versions of the plugin (likely before the androidAllowWhileIdle flag was added) could fail to work. This issue started occuring in 14.0 where support for inexact notifications was added using the ScheduleMode enum that was added and resulted in the deprecation of androidAllowWhileIdle. A mechanism was added to help "migrate" old notifications that wouldn't have this flag so that it results in a notification scheduled with exact timing as per the old behaviour. Thanks to the PR from Ruchi Purohit. Note that this release is to include hotfix that was made as part of the 14.1.5 and 15.1.3 hotfix releases

flutter_local_notifications-v15.1.3

• [Android] fixed issue 2136 where notifications on scheduled using older versions of the plugin (likely before the androidAllowWhileIdle flag was added) could fail to work. This issue started occuring in 14.0 where support for inexact notifications was added using the ScheduleMode enum that was added and resulted in the deprecation of androidAllowWhileIdle. A mechanism was added to help "migrate" old notifications that wouldn't have this flag so that it results in a notification scheduled with exact timing as per the old behaviour. Thanks to the PR from Ruchi Purohit. Note that this release is to include hotfix that was made as part of the 14.1.5 hotfix release