Idea

bda2206@gmail.com avatar image
bda2206@gmail.com suggested

Push Notifications to offer all native functionality with one additional field needed in the function call

The current push function does not support all the native IOS functionality. Since IOS 9, push messages are not delivered to the application if it is in foreground, unless you pass the content-available:1 key.

reference:

https://developer.apple.com/library/content/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/PayloadKeyReference.html

I would like to see an additional optional data field NativeKeys that you can provide native key/values to, such they are added to the delivered data alongside the keys that are specifically listed in Playfab.

ie passing a value {content-available : 1} would result in the following being delivered to the device.

{ aps : { Badge: 1, content-available : 1, Message : "message", Title: "title" }}

passing a value {content-available : 1, sound : "ding.mp3" } would result in

{ aps : { Badge: 1, content-available : 1,sound : "ding.mp3", Message : "message", Title: "title" }}

This would be future proofing the playfab platform against any changes in push functionality across the various platforms.

Push Notifications
10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Comment

·
brendan avatar image
brendan commented

Please see this thread for info on how to use advanced Push: https://community.playfab.com/questions/17177/ios-push-not-received-in-application.html

10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Write a Comment

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Your Opinion Counts

Share your great idea, or help out by voting for other people's ideas.