When is the mentioned update for aps / APNs handling going to come out?
Closed this issue · 6 comments
- My current app sends a lot of additional info along with a message, and because currently anything after "aps" key is included in the push payload, it easily goes over 256 bytes and does not send pushes. When I tried putting the "aps" key as anything other than the first key, it simply doesn't send.
- Is this change going to be exclusively server side? Would it require a SDK update?
Referencing the change mentioned in: http://www.pubnub.com/docs/objective-c/iOS/tutorial/apple-push-notification.html
"As of today, when Mobile Push Gateway for APNs scans a messsage payload for APNs content, anything in the "aps" key will be sent, as well any key that follows"
"This behavior will change in a future release so that only content contained in the "aps" tag is sent to APNS."
Following up on this: when it says "The behavior will change in a future release..." this seems like a server-side change. Does that mean that the behavior will change such that all users are affected by the behavior, and not just the users with the newest SDK?
The current behavior will continue to work as is (backward compatible). There will be a more clear format that allows you specify the data that will be sent to APN, GCM and to the PubNub realtime channel. Forthcoming docs will clearly define how to do this.
Do you know when that release will be?
@navkast please email support@pubnub.com and we'll get you on the beta.
geremy
Don't think I'm interested in the beta. I just want to know when the release will be.
Its TBD. Thats why we'd like to get you on the beta list, at the least
to check it out to see if it helps you, and the most, to get you a
concrete release date once we've hammered out all known issues.
geremy
On 6/10/14, 1:27 PM, Naveen Kasthuri wrote:
Don't think I'm interested in the beta. I just want to know when the
release will be.—
Reply to this email directly or view it on GitHub
#66 (comment).