Arguing for adding support for content-available in alert notifications

[Frizlab]

Is your feature request related to a problem? Please describe.
Yes.
My goal is to write a conversation solution (among other).
When I was in another company, when we sent a push for a new message, we used to use a content-available push, to be called in didReceiveRemoteNotification in the iOS app.
I’d like to do the same, but APNSwift does not allow alert notifications w/ content-available.

Describe the solution you'd like
Add a contentAvailable argument to APNSAlertNotification.

Describe alternatives you've considered

• Send a silent notification in addition to the alert notification. This has the advantage of making it possible to coalesce the potential background updates. This would have to be in conjonction with the other alternative considered:
• Use the user notification delegate and willPresent. This works only when the app is in the foreground. The app won’t be launched if it is not in memory anymore, nor even if it is in the background.

Additional context
I understand Apple seems to not want the content-available key to be used alongside an alert, but really, it works… (I have tested.)

What do you think?

[kylebrowning]

Its been suggested already #209

I would think its safer to not support it as if something breaks with APple's side, people using this library will come here asking why.

That being said you can write a custom version of the Alert yourself in your own library and use it.

[Frizlab]

I understand. I might do that, or use an NSE (I wanted to avoid IPC; it's a pain!).

Anyways, thanks for your answer.