-
Notifications
You must be signed in to change notification settings - Fork 341
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for New APNS format #44
Comments
Thanks for pointing this out, I wasn't aware of it. I'll take a look soon. |
Does the current legacy implementation support expiration date and priority setting in the gem? |
Apparently as well on the new service the payload size has been bumped from 256bytes to 1024 or 2048 (different sizes given at different sessions). Which will help to make it more usable in the future and bring it closer to GCM etc. |
The notification format rpush currently uses has been bumped up higher than 256 bytes as well. Messages >256bytes work in the sandbox environment. They still fail on the production one though, presumably until iOS8 is officially released. |
@skunkworker it does support expiration, which Rpush exposes as the |
@gdeglin @skunkworker can you point me in the direction of talk about the increased payload sizes? |
Looking at ./lib/rpush/client/active_model/apns/notification.rb , it looks like this gem is currently only supporting the LEGACY APNS "Enhanced Noticication Format"
where the notification packet starts with a "1"
see:
https://developer.apple.com/library/ios/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/Chapters/LegacyFormat.html#//apple_ref/doc/uid/TP40008194-CH105-SW1
When are you planning on updating the code to support the newer APNS format starting
with a "2" ?
https://developer.apple.com/library/ios/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/Chapters/CommunicatingWIthAPS.html
The text was updated successfully, but these errors were encountered: