- Breaking change callbacks have now been reworked. There are now the following callbacks and both will pass an instance of the
NotificationResponseclass onDidReceiveNotificationResponse: invoked only when the app is running. This works for when a user has selected a notification or notification action. This replaces theonSelectNotificationcallback that existed before. For notification actions, the action needs to be configured to indicate the the app or user interface should be shown on invoking the action for this callback to be invoked i.e. by specifying theDarwinNotificationActionOption.foregroundoption on iOS and theshowsUserInterfaceproperty on Android. On macOS and Linux, as there's no support for background isolates it will always invoke this callbackonDidReceiveBackgroundNotificationResponse: invoked on a background isolate for when a user has selected a notification action. This replaces theonSelectNotificationActioncallback- Breaking change the
NotificationAppLaunchDetailshas been updated to contain an instanceNotificationResponseclass with thepayloadbelonging to theNotificationResponseclass. This is to allow knowing more details about what caused the app to launch e.g. if a notification action was used to do so - [iOS][macOS] updated how notification categories were set behind the scenes so the categories specified. This fixes an issue where notification action may not work at all as were being appended to the list of existing categories. This could lead to issues where notification actions wouldn't work at all and potentially result in notification categories growing over time.
- Updated docs to clarify that on Apple's platforms, notification actions are only supported on iOS 10 or newer and macOS 10.14 or newer