Don't set "aps" key if no well-known properties are present

[aaronpk]

It is possible and entirely valid to send a push notification through APNS containing just the payload {"hello":"world"}. This should arrive in the app's delegate method exactly as was sent (assuming the app is in the foreground when the notification is sent).

Currently the library always adds the aps key even if none of the alert, badge, etc keys are set. Instead, the aps key should only be set if at least one of the well-known properties are present.

[argon]

You're right, however it didn't seem to me like there is an obvious use case for sending notifications which don't have an aps property - they can only be consumed when the app is running, and from my experience they're not designed for communication with a running app, the fact that it works is for convenience more than anything.

I'll take a look though and if I can see an obvious way to implement it I will.

-A

On 5 Dec 2013, at 20:01, Aaron Parecki notifications@github.com wrote:

It is possible and entirely valid to send a push notification through APNS containing just the payload {"hello":"world"}. This should arrive in the app's delegate method exactly as was sent (assuming the app is in the foreground when the notification is sent).

Currently the library always adds the aps key even if none of the alert, badge, etc keys are set. Instead, the aps key should only be set if at least one of the well-known properties are present.

—
Reply to this email directly or view it on GitHub.

[aaronpk]

Cool, thanks!

[argon]

I've been very busy recently, will try to get something going over the Holidays.

[argon]

I see this behaviour is desirable when MDM is used. My apologies. I have developed a fix which will be in the next version.

[aaronpk]

Thanks!