Super class: CKOperationMBS
|Type||Topic||Plugin||Version||macOS||Windows||Linux||Console & Web||iOS|
|class||CloudKit||MBS Mac64bit Plugin||16.5||Yes||No||No||Yes, macOS only||No|
Notification objects contain the data associated with push notifications that have already been sent to an app. Fetch notification objects to identify changes that your app might have missed or to retrieve the complete push notification payload, which might have been truncated when it was delivered to the device.
After fetching the current notifications, you can mark some or all of them as read using a CKMarkNotificationsReadOperation object. Marking a notification as read prevents it from being returned by subsequent fetch operations.
The events to process the fetched notifications are executed serially on an internal queue that is managed by the operation object. Your events must be capable of executing on a background thread, so any tasks that require access to the main thread must be redirected accordingly.
The completion event is called after the operation executes and returns its results to you. You can use a completed event to perform housekeeping chores related to the operation, but do not use it to process the results of the operation itself. Any completion event you specify should be prepared to handle the failure of the operation to complete its task, whether due to an error or an explicit cancellation.
Subclass of the CKOperationMBS class.
- 2 events
- 3 properties
- method Constructor(previousServerChangeToken as CKServerChangeTokenMBS)
Super class CKOperationMBS
- 2 events
- 7 properties
- 6 methods
This class has no sub classes.
The items on this page are in the following plugins: MBS Mac64bit Plugin.
MBS Xojo blog