BUG Fix for Apple Silent Push Notifications
Payload must contain something other than only content-available:1,
adding sound="" is a good known solution.
BUG Fix for Apple Silent Push Notifications (Bis, typo got mixed in)
Payload must contain something other than only content-available:1,
adding sound="" is a good known solution.
Added TargetPackageName and NotificationKey

Added TargetPackageName (serialized as "restricted_package_name") and NotificationKey (serialized as "notification_key") to the GCM notification object that will be sent to GCM server
Changed SSL protocol used for APNS from SSL3 to TLS. Using SSL3 was no longer working for the APNS sandbox environment
Changed SSL Protocol from SSL3 to TLS for the APNS Feedback service
Include OldSubscriptionId and SubscriptionExpiryUtc in notification result for expired Windows and Windows Phone subscriptions.
Added FirefoxOS support

- Added PushBroker extensions
- FirefoxOS push channel
- Fluent creation of notifications
Added missing reference for PushSharp.Core
Changed target framework to .NET 4
Merge pull request #369 from coffeesmurf/master

Fix for APNS Sandbox notifications that were no longer working
Merge pull request #314 from alixMougenot/master

BUG Fix for Apple Silent Push Notifications
Remove nasty stuff
Typo on Sample project has been fixed
unified coding convention(indentation)
- spaces => tabs
Add iOS8 Interactive Notification Support

Add APS "category" property for iOS8 interactive notifications.
Add more category support

Add a fluent helper to set a category and a constructor.
Don't try to convert JObject/JArray to JValue and then to JToken
Apple increased the APNS payload size to 2048
Merge pull request #412 from steveheyman/master

Add iOS8 Interactive Notification Support
Removed specific test for 500 error to comply with Google's documentation:

Errors in the 500-599 range (such as 500 or 503) indicate that there wa an
internal error in the GCM server while trying to process the request, or
that the server is temporarily unavailable (for example, because of
timeouts). Sender must retry later, honoring any Retry-After header
included in the response. Application servers must implement exponential
back-off.

https://developer.android.com/google/gcm/http.html