Quickstart-ios: Support for "mutable-content": true

[daveanderson]

The documentation for UNNotificationServiceExtension indicates

• The remote notification’s aps dictionary includes the mutable-content key with the value set to 1.

The FCM documentation at https://firebase.google.com/docs/cloud-messaging/http-server-ref#send-downstream does not make reference to the mutable-content key or a way to set the mutable-content key.

if I include "mutable-content": true as part of the notification dictionary within the payload submitted to FCM, the value is received (outside of the aps dictionary) on iOS as

    "gcm.notification.mutable-content" = true;

When will FCM support the mutable-content capability? How will I need to specify this within the FCM payload so that it will be received on iOS and allow the use of a UNNotificationServiceExtension to pre-process the received notification?

[Atheros1]

(bump)
Without this support in the HTTP API we cannot get phones to pre-process the received notification either. Setting the message in the notification body is not possible in our case.

[t0rr3sp3dr0]

Same problem here

[simsimmal]

Same here

[kjones]

This is a big problem and needs to be fixed ASAP. Without it we can't make any progress on iOS 10 notification service and content extensions.

[HiroshiHorie]

I can not believe this is not fixed yet, should have been ready while iOS 10 was in beta.

[ianbarber]

Thanks - we have a FR for it internally, and are looking at the server side changes now. No specific timelines I can share, but should be in a future release - sorry there is nothing more concrete to share!

[joedivittorio]

@ianbarber any update on this?

[ianbarber]

No update, sorry

[baims]

we've been waiting for 3 months now, any updates at least ?

[jaumevn]

@ianbarber any news on this?

[adrian-oaida]

@ianbarber is there a timeline for this feature ?

[BasantAshraf]

Any Updates please ?

[simsimmal]

Any updates? Issue is closed now??
Firebase seems a bad choice as a push service provider if you care about ios. We really want to support rich notifications.

[ianbarber]

Hi all - no update. Issue is closed as the tracker is for bugs on the samples. Support is still being worked on but we don't have a timeline - best place to check is the Firebase Release Notes and the firebase-talk Google group: https://firebase.google.com/support/ - sorry nothing more definitive right now!

[atulvuliv]

This is so bad. We moved everything to FCM and now its lacking the basic features. Why to change the payload to "gcm.notification.mutable-content" = true; ?

[ianbarber]

Appreciate your frustration - we should have been ahead of this one, sorry.

[ianbarber]

Because this issue tracker is for samples, and this is not an issue with
the samples.

On Thu, 10 Nov 2016, 01:29 priyeshmarvi, [email protected] wrote:

@ianbarber https://github.com/ianbarber but why did you closed this
issue .. you need to set bug or enhancement tag on it

—
You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub
https://github.com/firebase/quickstart-ios/issues/70#issuecomment-259642124,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAM0Vp1f6OczpNHiuxENJibBJ1J7qTbHks5q8uPxgaJpZM4JgsEq
.

[daveanderson]

Not trying to be disagreeable, but the sample _should_ show how to do this.

[ianbarber]

Yeah, I get that, but the max the sample should show how to do is things
the product does. If we supported mutable-content, and the sample didn't
show it, that would be a clear sample bug. Its worth noting there is a
specific place for filing product bugs and feature requests too (
https://firebase.google.com/support/contact/bugs-features/) so I'm not
trying to shut down otherwise useful feedback!

On Thu, 10 Nov 2016 at 12:19 Dave Anderson [email protected] wrote:

Not trying to be disagreeable, but the sample _should_ show how to do
this.

—
You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub
https://github.com/firebase/quickstart-ios/issues/70#issuecomment-259790563,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAM0VtLJH4wx_x-sygzENU31XpzNtNxvks5q83afgaJpZM4JgsEq
.

[hopye]

omg, still no fix ?

[ianbarber]

Just an update for anyone checking the new release for this: its being worked on, but we wont have anything until next year, sorry.

[grioja]

@ianbarber can you open up the API so we aren't relying on the SDK to whitelist adding these kinds of attributes to payloads? For future-proofing if the SDK isn't going to move as fast as client feature releases.

[tomaskraina]

@ianbarber Thanks for the heads up. Is there any way to escalate this issue? Anything I can do, e.g. file anything similar to Apple's radar?

[erudonja1]

So basically, If I understood well, we can't use rich notifications on ios 10, because FCM client can't find "mutable-content" in "aps -> notification" node of push message?

NotificationService and NotificationContent extension in that case are not triggered and rich notifications are not created by the iOS 10...

This will be possible next year?

[ianbarber]

@tomaskraina https://firebase.google.com/support/contact/bugs-features/ is the closest thing to a radar.

[hc-kim]

I hope this to be fixed ASAP as well. I write a bug report to above link also.
(Everyone who enters this thread should send one bug report for each one. So they can quickly recognize how this is huge bug.)

[chengsam]

Is it possible to include the image URL in the data message and create a local notification with image downloaded?

[grioja]

@ianbarber is there any update on rich notification support?

[N0un]

@ianbarber Hi, have you an idea about when this fix will be released ?

@chengsam Yes, you ca put your custom keys-values in the data message. But the only way to get that kind of message is when your app is alive, on foreground or background. To process it when your app is not yet started or killed, you have to include notification fields with data message (hybrid message) and to modify the content of the no-yet-displayed notification. To do that, you need the notification extension and this famous "mutable-content" key. So for now, with Firebase, it's impossible.

[aronse]

Hey guys, just migrated from Parse and found out that 'mutable-content' is not supported. Thought it'd be working out of the box considering iOS10 was released nearly 5 months ago... Anyway, any idea/update about when this will be added? @ianbarber

[N0un]

@aronse I contacted Firebase support team few hours ago and I just received that :

Many developers have already requested this feature for iOS. It is still being discussed by our engineering team and is being prioritized accordingly. I cannot provide any timeline and details regarding this feature, but you can keep track of our release notes.

[aronse]

@N0un Thanks! Well I can't really wait to see this implemented (or not) in the release notes... Also not exactly confident about using something that's 5 months late feature-wise (especially for something as trivial as this) so I guess I'll use something else.

[Gujci]

Will we ever have any update on this? Or should I consider using other solutions as soon as possible?

[debayanb]

Is there any update on this? We need rich notifications support from firebase.

[tomaskraina]

@debayanb You can have iOS10 rich notification working on Firebase with little bit more work. Hint: Use click_action.

What's missing is being able to mutate the content of the notification, like add an image, for example without implementing Notification Content target.

[Gujci]

@tomaskraina that's great, but as far as I know click action was here before iOS 10, what we can't do now is, as you mentioned, mutating the content, like loading and configuring the notification to present in a notification content extension with rich data (which is iOS 10 specific) since our notification service extension never gets called. Please correct me, if I'm wrong.

[tomaskraina]

@Gujci You don't need to mutate the content in order to use the Notification Content Extension and show custom UI. Notification Content extension can be triggered via click-action, which translates into category when sent to APNS. That's what I do in my current app.

Only Notification Service Extension can't be triggered at the moment as you need the mutable-content flag.

[Gujci]

@tomaskraina that is cool, but in my case the Notification Content Extension needs more data, basically the Notification Service Extension has to ask the server for more data. But I'll try to skip this step or just use the node apns module on the server. Thanks anyway :)

[tomaskraina]

@Gujci Sure, no prob :) You can request the additional data in the Notification Content Extension.

[debayanb]

@tomaskraina thanks man. I'll try it out.

[CharlesAE]

I guess im not the only one waiting on a fix

[hopye]

When are we getting a fix on this ? Please!!!

Lg

Sent from my iPhone 6 Plus

On Feb 4, 2017, at 4:49 PM, Charles E [e-mail] wrote:

I guess im not the only one waiting on a fix

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

[pinireisman]

Come on Firebase...
People are waiting for this for a long long time now.
Please deliver on your statements of being truly a cross platform solution for us mobile developers.
This is a very important feature that we REALLY need supported.

so PLEASE!!!

[johngithubby]

Really, after more than 5 months, nothing???

[tomaskraina]

Hey all,

For anyone missing this feature badly, don't hesitate to file an official feature request with critical urgency at https://firebase.google.com/support/contact/bugs-features/

I recommend using the same title as this github issue and adding a link to the description.

I believe that this could help the engineers and/or managers at Firebase prioritize this issue internally, after seeing how many people need this.

[felipesabino]

@tomaskraina Did that on Friday and got a sad feedback

Hi Felipe,

Thanks for reaching out. We're definitely aware that many users, such as yourself, would like the support for the "mutable-content" key for iOS available through FCM. We're exploring potential solutions, but I can't share any details or timelines at this time. We'll keep your feedback in consideration moving forward though.

Keep an eye out on our release notes for any further updates.

Cheers,
Firebase Support

Well, if you are counting on it be aware that it looks like it is not even is not even in development yet, let alone scheduled to be released shortly.

---

[Speculation]

Well, it is kind of understandable as adding this mutable tag to the payload is more than meets the eye. I initially thought it would be just adding a mutable tag to the notification payload until we started doing it on our own push sender mechanism.

When dealing with an app extension while having data on a local database means that you need to use an app group to share data between the app and the extension. Also, you have to migrate the data manually from the app to the app group and, if I had to guess, I would say that they want to make this step as straightforward as possible for developers, which can lead to a lot of complications, resulting in the humungous delay on delivering it.

[kroikie]

Hi All,

We added the mutable_content field to FCM API. Notification messages sent with mutable_content set to true can be intercepted on iOS 10+ clients and be updated before being presented to the user.

The mutable_content field maps to the mutable-content field on APNs.

[felipesabino]

That's great news! I am not even sad anymore that the support team had no idea of what was going on

@kroikie Do you know if we can expect Firebase SDKs to behave properly even with this app group issue when sharing content data between app and app extensions? If not, do you know who can provide this kind of information?

[kroikie]

Hi @felipesabino from an FCM perspective the app group should not have any impact on the receipt of messages. I would assume the same for the other SDKs but I'm less sure about it's impact on them. I will raise it with my team and we will be sure to address any issues that come up, thanks for flagging it.

[johngithubby]

@kroikie thanks. Did you guys add this to the Notifications UI console? That's where I need it first.

[hopye]

This is just embarrassing! . Such a quick and easy implementation. And yet we are waiting for 6 months.

Lg

Sent from my iPhone 6 Plus

On Feb 7, 2017, at 8:53 AM, pinireisman [e-mail] wrote:

Come on Firebase...
People are waiting for this for a long long time now.
Please deliver on your statements of being truly a cross platform solution for us mobile developers.
This is a very important feature that we REALLY need supported.

so PLEASE!!!

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

[bhavukjain1]

Works perfectly for the rich notifications.

[ianbarber]

Locking this thread as it is now available in the API. Feel free to raise other feature requests with support - or open issues for other concerns!