chore(deps): bump flutter_local_notifications from 15.1.3 to 17.1.0 in /uni

[dependabot[bot]]

Bumps flutter_local_notifications from 15.1.3 to 17.1.0.

Release notes

Sourced from flutter_local_notifications's releases.

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

• 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-v16.3.1+1

• [iOS] added privacy manifest

flutter_local_notifications-v16.3.0

• [iOS][macOS] added the checkPermissions() method to the IOSFlutterLocalNotificationsPlugin and MacOSFlutterLocalNotificationsPlugin classes respectively. This can be use to check the notification permissions granted to the app. Thanks to the PR from Konstantin Dovnar
• Fixed part of the readme where a word was missing in the "AndroidManifest.xml setup" section

flutter_local_notifications-v16.2.0

• [Android] added the silent property to the AndroidNotificationDetails that allows specifying a notification on Android to be silent even if associated the notification channel allows for sounds to be played. Thanks to the PR from aa-euclidk

flutter_local_notifications-v16.1.0

• [Android] calling the requestExactAlarmsPermission() method will now go directly to the alarm settings screen specific to the app instead the general alarm settings screen where users needed to pick the app they wanted to change the settings for. Thanks to the PR from ShunMc
• [Android] fixed conflict with other plugins when it comes to handling permission requests. Thanks to the PR from Patrick
• Fixed grammar issue and iOS/macOS specific code snippet in the notification actions section of the readme. Thanks to the PRs from Md. Touhidul Islam

flutter_local_notifications-v16.0.0

• [Android] Breaking change renamed the requestPermission() method associated with the AndroidFlutterLocalNotificationsPlugin class to requestNotificationsPermission(). This was done to be more explicit given another method (requestExactAlarmsPermission()) has been added that also requests a permission (more details below).
• [Android] Breaking change the plugin now only declares the bare minimum in its AndroidManifest.xml. This means applications making use of either scheduled notifications, full-screen intent notifications or notification actions will now require changes in the application's own AndroidManifest.xml file. Please check the AndroidManifest.xml setup section of the readme for more details. The reason this was done was because not all applications will leverage all of the plugin's features. Doing this will now allow applications to only request the appropriate permissions needed for their application. This addresses issue 1687
• [Android] added the ability to request permission to schedule exact alarms via the requestExactAlarmsPermission() method that has been added to the AndroidFlutterLocalNotificationsPlugin class that represents the Android implementation of the plugin. This has been done in response to behaviour changes introduced in Android 14 (API level 34) when comes to using exact alarms. See the official documentation about these changes here. This change addresses issue 1906
• [Android] bumped Java desugaring dependency and updated readme accordingly to also mention Gradle version that is used by plugin
• [Android] fixed issue an issue similar to 2033 that was addressed in 15.0.1 where notifications on scheduled using older version of the plugin via the periodicallyShow() method would fail to have the next subsequent ones scheduled. 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 had androidAllowWhileIdle specified but didn't account for how there are recurring notifications that were scheduled using older versions of the plugin prior to androidAllowWhile being added. This was also released as part of the 15.1.1 and 14.1.3 hotfix releases
• [Android] fixed issue 2106 where calling getNotificationChannels() reports the wrong importance level or result in an exception if the importance level was unspecified. This was also released as part of the 15.1.2 and 14.1.4 hotfix releases
• [iOS][macOS] addresses issue 2097 by updating API docs for the presentSound and defaultPresentSound properties that belong to the DarwinNotificationDetails and DarwinInitializationSettings classes respectively to clarify the background behaviour and how have a sound play even when app is the background yet these properties are set to false

... (truncated)

Commits

• 5e7d4ee [various] prepare for 17.1.0 release (#2306)
• 5dd51aa [flutter_local_notifications] Added AudioAttributesUsage for AndroidNotificat...
• f63f9c1 [various] Added bigText to ActiveNotification (#2290)
• a6b2e98 Updated docs to reflect actual iOS behaviour (#2276)
• 494c4ca Fix #2293 - update link to Gradle desugaring setup documentation in README.md...
• 48bd0c8 prepare for 17.0.1 release (#2296)
• c48b5d9 added reason for using User Defaults API to iOS privacy manifest (#2294)
• 070f213 prepare for 17.0.0 release (#2258)
• 4873079 [flutter_local_notifications] bumped compile SDK version to 34 (#2257)
• 0de329a Update README.md (#2251)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot[bot]]

Superseded by #1234.