Support iOS VoIP and Standard notifications in one hub
My app need standard, silent and VoIP notifications. If I want to support them, I need 2 notification hubs just because of iOS.
We’re hoping to expand support for push types in a future release. We’ll add this to the feature list we’re considering
David Lapes commented
This would require the user to register with a pushkit taken and normal apns token on the same hub.
We currently run 4 hubs per bundle production/sandbox and voip and classic. It is a pain but it does work.
Christian Hettich | RE'FLEKT GmbH commented
When using token based authentification, notification hubs need to send some headers to the apple push api that define what kind of push you want to send.
For "alert" pushes:
"apns-push-type" needs to be set to "alert"
"apns-topic" needs to be set to you apps BundleId
For "voip" pushes:
"apns-push-type" needs to be set to "voip"
"apns-topic" needs to be set to you apps BundleId + the suffix "voip"
When using the Notification Hub .NET Sdk you can set headers for template notifications.
Some of these headers are passed to the apple push api and some not.
"apns-push-type" is passed to apple and you have to set it.
Unfortunately notification hubs don't pass the "apns-topic" you set in the headers to the apple push api.
It always uses the value which is configured in the portal.
Because of this it is not possible to use a single Notification Hub for both types of pushes.
Passing the "apns-topic" header to the apple push api would solve this problem.
Michal Dobrodenka commented
And there is not event word about VoIP push in docs