Azure Notification Hubs updates for iOS 13

Apple recently updated their public Push service in a way that affects Azure Notification Hubs customers. [Learn more](https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fnotification-hubs%2Fpush-notification-updates-ios-13&data=02%7C01%7Cv-krwea%40microsoft.com%7C5db3f7e8f7234faf816808d7566acc2c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637072888996446108&sdata=rSgRlhwBWOFXHcA0m5hWzU55jcJUIOOxMeLHi8yfRRY%3D&reserved=0) about the impact of these changes on Azure Notification Hubs. Specifically, Apple now requires that developers identify notifications as an alert or background notifications through the new ‘apns-push-type’ header in the APNS API According to [Apple’s documentation](https://developer.apple.com/documentation/usernotifications/setting%5Fup%5Fa%5Fremote%5Fnotification%5Fserver/sending%5Fnotification%5Frequests%5Fto%5Fapns): “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.” Developers must now set this header in their applications that send notifications through Azure Notification Hubs. Due to a technical limitation, customers must use token-based authentication for APNS credentials with requests that includes this attribute. If you’re using certificate-based authentication for your APNS credentials, you must switch to using token-based authentication. To help you during this transition, when Azure Notification Hubs detects a notification that doesn’t have the apns-push-type set, the service will infer the push type from the notification request and set the value automatically. Remember, you must configure Azure Notification Hubs to use token-based authentication to set the required header; please refer to [Token-based (HTTP/2) Authentication for APNS](https://docs.microsoft.com/en-us/azure/notification-hubs/notification-hubs-push-notification-http2-token-authentification) for additional information. Another minor change, but one that requires a change to the back-end application that sends notifications, is the requirement that for background notifications the apns-priority header must be set to 5\. Many applications set the apns-priority header to 10 (indicating immediate delivery), or don’t set it and get the default value which is also 10\. This is no longer allowed for background notifications, so you must set the value for each request as Apple will not deliver background notifications if this value is missing. For years, iOS developers used the description attribute of the deviceToken data sent to the push token delegate to extract the push token a back-end application uses to send notifications to the device. With Xcode 11, that description attribute changed to a different format. Existing code developers used for this is now broken. We’ve updated the Azure Notification Hubs SDK to accommodate this change. Please update the SDK used by your applications to the version 2.0.4 or newer of the [Azure Notification Hubs iOS SDK](https://github.com/Azure/azure-notificationhubs-ios). * Notification Hubs * Features * [ Notification Hubs](https://azure.microsoft.com/en-gb/services/notification-hubs/)