Bot releases are hidden (Show)
Published by MaikuB about 4 years ago
Published by MaikuB about 4 years ago
zonedSchedule
methodPublished by MaikuB about 4 years ago
Published by MaikuB about 4 years ago
onDidReceiveLocalNotification
callback specific to iOS. Thanks to the PR from Mike Truso
Published by MaikuB about 4 years ago
schedule
, showDailyAtTime
and showWeeklyAtDayAndTime
methods has been marked as a deprecated due to problems with time zones, particularly when it comes to daylight savings.zonedSchedule
method to the plugin that allows for scheduling notifications to occur on a specific date and time relative a specific time zone. This can be used to schedule daily and weekly notifications as well. The example app has been updated to demonstrate its usage. Applications will need to retrieve the device's local IANA timezone ID via native code or a plugin (e.g. flutter_native_timezone
). Note that to support time zone-based scheduling, the plugin now depends on the timezone
package so that an instance of the TZDateTime
class is required to the specify the time the notification should occur. This should work in most cases as it is IANA-based and native platforms have time zones that are IANA-based as well. To support time zone aware dates on older versions of Android (which use older Java APIs), the plugin depends on the ThreeTen Android Backport library. Once Flutter's support for Android Studio 4.0 and Android Gradle plugin 4.0 has stabilised, the plugin will be updated to make use of desugaring instead of relying on the ThreeTen Android Backport library.getNotificationAppLaunchDetails()
behaved inconsistently depending on if it was called before or after initialize()
getActiveNotifications()
method to the AndroidFlutterLocalNotificationsPlugin
class thanks to the PR from Vincent Kammerer. This can be used to query the active notifications and is only applicable to Android 6.0 or newerandroidAllowWhileIdle
boolean argument to the periodicallyShow
method. When set to true, this changes how recurring notifications are shown so that the Android AlarmManager
API is used to schedule a notification with exact timing. When the notification appears, the next one is scheduled after that. This is get around the limitations where the AlarmManager
APIs don't provide a way for work to be repeated with precising timing regardless of the power mode.fullScreenIntent
argument that has been added to the constructor of the AndroidNotificationDetails
class. Thanks to the PR from Nadav Fima
subtitle
property of the IOSNotificationDetails
class. This property is only application to iOS versions 10 or newerInitializationSettings
and NotificationDetails
classes no longer have positional parameters but now have named parameters called android
and iOS
for passing in data specific to Android and iOS. There macOS
named parameter has also been added for passing data specific to macOStoMap
method that was used internally to transfer data over platform channels is no longer publicly accessibleDay
AndroidNotificationChannelAction
Importance
(note: as default
is a keyword, what use to be Default
is now defaultImportance
)Priority
(note: as default
is a keyword, what use to be Default
is now defaultPriority
)GroupAlertBehavior
NotificationVisibility
RepeatInterval
IOSInitializationSettings
constructor to prevent null values being passed inThis was incorrectly published in the 1.5.0 update
Published by MaikuB about 4 years ago
Published by MaikuB about 4 years ago
schedule
, showDailyAtTime
and showWeeklyAtDayAndTime
methods has been marked as a deprecated due to problems with time zones, particularly when it comes to daylight savings.zonedSchedule
method to the plugin that allows for scheduling notifications to occur on a specific date and time relative a specific time zone. This can be used to schedule daily and weekly notifications as well. The example app has been updated to demonstrate its usage. Note that to support time zone-based scheduling, the plugin now depends on the timezone
package so that an instance of the TZDateTime
class is required to the specify the time the notification should occur. This should work in most cases as it is IANA-based and native platforms have time zones that are IANA-based as well. To support time zone aware dates on older versions of Android (which use older Java APIs), the plugin depends on the ThreeTen Android Backport library. Once Flutter's support for Android Studio 4.0 and Android Gradle plugin 4.0 has stabilised, the plugin will be updated to make use of desugaring instead of relying on the ThreeTen Android Backport library.getNotificationAppLaunchDetails()
behaved inconsistently depending on if it was called before or after initialize()
getActiveNotifications()
method to the AndroidFlutterLocalNotificationsPlugin
class thanks to the PR from Vincent Kammerer. This can be used to query the active notifications and is only applicable to Android 6.0 or newerandroidAllowWhileIdle
boolean argument to the periodicallyShow
method. When set to true, this changes how recurring notifications are shown so that the Android AlarmManager
API is used to schedule a notification with exact timing. When the notification appears, the next one is scheduled after that. This is get around the limitations where the AlarmManager
APIs don't provide a way for work to be repeated with precising timing regardless of the power mode.fullScreenIntent
argument that has been added to the AndroidNotificationDetails
class. Thanks to the PR from Nadav Fima
subtitle
property of the IOSNotificationDetails
class. This property is only application to iOS versions 10 or newerInitializationSettings
and NotificationDetails
classes no longer have positional parameters but now have named parameters called android
and iOS
for passing in data specific to Android and iOS. There macOS
named parameter has also been added for passing data specific to macOStoMap
method that was used internally to transfer data over platform channels is no longer publicly accessibleDay
AndroidNotificationChannelAction
Importance
(note: as default
is a keyword, what use to be Default
is now defaultImportance
)Priority
(note: as default
is a keyword, what use to be Default
is now defaultPriority
)GroupAlertBehavior
NotificationVisibility
RepeatInterval
IOSInitializationSettings
constructor to prevent null values being passed inPublished by MaikuB about 4 years ago
RepeatInterval
enum values to use lower camel casingplugin_platform_interface
dependencyPublished by MaikuB about 4 years ago
platform
package version range constraint so that 3.x null safety releases could be used (currently used in Flutter 1.22 stable)Published by MaikuB about 4 years ago
Published by MaikuB about 4 years ago
Published by MaikuB about 4 years ago
Published by MaikuB about 4 years ago
fullScreenIntent
argument that has been added to the AndroidNotificationDetails
class. Thanks to the PR from Nadav Fima
Published by MaikuB about 4 years ago
initialize()
and getNotificationAppLaunchDetails()
to fail when called from the backgroundPublished by MaikuB about 4 years ago
onSelectNotification
callback could be called again after the user has tapped on a notification, sent the application to the background and returned to the app via the Recents screen. This issue could have previously called getNotificationAppLaunchDetails()
to mistakenly report that a notification launched the app when it's called again as part of the application being resumedPublished by MaikuB over 4 years ago
getActiveNotifications()
method to the AndroidFlutterLocalNotificationsPlugin
class thanks to the PR from Vincent Kammerer. This can be used to query the active notifications and is only applicable to Android 6.0 or newerPublished by MaikuB over 4 years ago
e2e
dependency from merging in changes from 1.4.4+2 releasePublished by MaikuB over 4 years ago
e2e
dependencyPublished by MaikuB over 4 years ago
Published by MaikuB over 4 years ago
getNotificationAppLaunchDetails()
behaved inconsistently depending on if it was called before or after initialize()