Backendless Support
 
Assigned to Dev

ios push Notifications - missing features

Hi,

any plans when messages will be fully compatible with iOS 10 ? .. there are at least two issues today :

- new flags like "mutable-content" are still not supported from what I can see

- There is an issue with the current implementation ..every time you create a object of instance of "PublishOptions".. the header "ios-content-available" = 1 is added by default ( to cover the case of silent notification)but this is basically creating conflicting issues in adding other iOS flags and when I try to remove that header, the whole thing just does not work (The notification message does not get delivered"..

final note : I'm using SDK v3.0.44

Regards

Eyad

Leave a Comment

Comments (14)

photo
1

Hello Support team,

would appreciate an answer here please

photo
1

Hello Eyad

I've contacted our iOS developer. He'll respond in this topic soon. Thanks for patience and sorry for inconvenience.

Regards Anton

photo
1

Hi Anton

Any news on the above issue ?

photo
photo
1

Hi Eyad,

Have you tried adding "mutable-content" as a user-defined header? Any headers you add should be delivered to the client.

As for you "ios-content-available", are you saying if you send that header with "0", it is not delivered as such?

Regards,

Mark

photo
1

Hi Mark,

Well I guess there is something missing here , let me just say tell you what I know and lets us see if anything is missing

1- about the first issue .. the flag (mutable-content),

iOS device are expecting the Notification messages to have the keys/values in specific format (capture 1 in attachment) ..

Using backendless Messaging if you try to send all those flags mentioned in capture 1 (the documentation suggest that we need to prefix the flag name with “ios-”). .. the received notification message dictionary is shown in capture 2 in same attached, here you see how the notification keys actually were formatted .. those flags which were supported by the Messaging module were included in “aps” key after stripping out the ios- prefix, supported flags like: badge, content-available, sound,..etc).. however the rest (including mutable-content flag) were not added and I take it because Messaging Module is not configured to do that .. (so to your point , yes it gets delivered but not included in the right place within the “aps” key) …some other dropped out flags also are key ones for formatting the notification message such as :body, title , subtitle ..

This is my view , let me know if anything is missing .

2- Now about the other part (the “content-available” key) .. this is actually linked to the point above , I thought it might be the source of conflict with not including the missing keys from the “aps" but further testing revealed that it might have nothing to do with it

photo
1

...

photo
1

Hi Mark,

Let me know if you have comments on the above

photo
photo
1

Hi Mark ,

I wonder if you saw the above reply ?

photo
1

Hey Eyad,

Your issue has been assigned to developer and would be investigated as soon as possible.

For reference, ticket ID is BKNDLSS-13731.

Regards,

Vlad

photo
1

Hi Vald,

Thanks .. how can I check the status of this request now ?

photo
1

Hi Eyad,

Unfortunately You can't, we will let you know at once the ticket resolved

photo
photo
1

Hi Vlad,

we are still awaiting a reply here ..would you please let me know if you have an update ?

photo
1

Hi Eyad,

We hit a little hickup with resource allocation for the iOS side of the SDKs. The issues have been streamlined and we're in good shape to move on now. Most of the iOS work is now done on preparing the SDK for the 4.0 release and there is quite a backlog there. I will re-prioritize the change for the headers, but cannot promise an immediate reaction.

Regards,

Mark

photo
1

Hi Mark ,

That will do ..lets hope

Thanks

Eyad