You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use the alert push type for notifications that trigger a user interaction—for example, an alert, badge, or sound. If you set this push type, the apns-topic header field must use your app’s bundle ID as the topic. For more information, see Generating a Remote Notification.
27
+
The alert push type is required on watchOS 6 and later. It is recommended on macOS, iOS, tvOS, and iPadOS.
28
+
*/
29
+
APNSItemPushTypeAlert,
30
+
31
+
/**
32
+
Use the background push type for notifications that deliver content in the background, and don’t trigger any user interactions. If you set this push type, the apns-topic header field must use your app’s bundle ID as the topic. For more information, see Pushing Background Updates to Your App.
33
+
The background push type is required on watchOS 6 and later. It is recommended on macOS, iOS, tvOS, and iPadOS.
34
+
*/
35
+
APNSItemPushTypeBackground,
36
+
37
+
/**
38
+
Use the voip push type for notifications that provide information about an incoming Voice-over-IP (VoIP) call. For more information, see Responding to VoIP Notifications from PushKit.
39
+
If you set this push type, the apns-topic header field must use your app’s bundle ID with .voip appended to the end. If you’re using certificate-based authentication, you must also register the certificate for VoIP services. The topic is then part of the 1.2.840.113635.100.6.3.4 or 1.2.840.113635.100.6.3.6 extension.
40
+
The voip push type is not available on watchOS. It is recommended on macOS, iOS, tvOS, and iPadOS.
41
+
*/
42
+
APNSItemPushTypeVoip,
43
+
44
+
/**
45
+
Use the complication push type for notifications that contain update information for a watchOS app’s complications. For more information, see Updating Your Timeline.
46
+
If you set this push type, the apns-topic header field must use your app’s bundle ID with .complication appended to the end. If you’re using certificate-based authentication, you must also register the certificate for WatchKit services. The topic is then part of the 1.2.840.113635.100.6.3.6 extension.
47
+
The complication push type is recommended for watchOS and iOS. It is not available on macOS, tvOS, and iPadOS.
48
+
*/
49
+
APNSItemPushTypeComplication,
50
+
51
+
/**
52
+
Use the fileprovider push type to signal changes to a File Provider extension. If you set this push type, the apns-topic header field must use your app’s bundle ID with .pushkit.fileprovider appended to the end. For more information, see Using Push Notifications to Signal Changes.
53
+
The fileprovider push type is not available on watchOS. It is recommended on macOS, iOS, tvOS, and iPadOS.
54
+
*/
55
+
APNSItemPushTypeFileProvider,
56
+
57
+
/**
58
+
Use the mdm push type for notifications that tell managed devices to contact the MDM server. If you set this push type, you must use the topic from the UID attribute in the subject of your MDM push certificate. For more information, see Device Management.
59
+
The mdm push type is not available on watchOS. It is recommended on macOS, iOS, tvOS, and iPadOS.
60
+
*/
61
+
APNSItemPushTypeMDM
62
+
};
63
+
64
+
/**
65
+
Default APNSItemPushType.
66
+
*/
67
+
APNSItemPushType APNSItemPushTypeDefault(void);
68
+
69
+
/**
70
+
Retrieve the valid string value for the HTTP header.
Required for watchOS 6 and later; recommended for macOS, iOS, tvOS, and iPadOS) The value of this header must accurately reflect the contents of your notification’s payload. If there is a mismatch, or if the header is missing on required systems, APNs may return an error, delay the delivery of the notification, or drop it altogether.
0 commit comments