|Type||Topic||Plugin||Version||macOS||Windows||Linux||Console & Web||iOS|
|class||User Notifications||MBS MacFrameworks Plugin||19.1||Yes||No||No||Yes, macOS only||No|
A UNNotification object contains the initial notification request, which contains the notification's payload, and the date on which the notification was delivered.
Don't create notification objects directly. When handling notifications, the system delivers notification objects to your events. The UNUserNotificationCenterMBS object also maintains the list of notifications that were previously delivered, and you use the getDeliveredNotifications method to retrieve those objects.
This is an abstract class. You can't create an instance, but you can get one from various plugin functions.
- 3 properties
- 2 methods
- 2 shared methods
- 9 constants
The file for an attachment is corrupt.
An attachment is too large.
The URL for an attachment was invalid.
An error occurred when trying to move an attachment to the system data store.
The specified attachment is not in the system data store.
The file type of an attachment is not supported.
The notification has no user-facing content, but should.
The notification does not have an associated date, but should.
Notifications are not allowed.
This error occurs when you try to submit a notification request and your app or app extension is not authorized to schedule notifications.
This class has no sub classes.
Some properties using for this class:
- UNNotificationResponseMBS.notification as UNNotificationMBS
Some events for this class:
- UNUserNotificationCenterMBS.getDeliveredNotificationsCompleted(notifications() as UNNotificationMBS, tag as variant)
- UNUserNotificationCenterMBS.openSettingsForNotification(notification as UNNotificationMBS)
- UNUserNotificationCenterMBS.willPresentNotification(notification as UNNotificationMBS, byref options as Integer)
The items on this page are in the following plugins: MBS MacFrameworks Plugin.
MBS FileMaker tutorial videos