[firebase_messaging] Should support Rich notifications by default on iOS.

[kaumudpa]

It still does not support Rich Notifications (Notifications with Image) on iOS, Anybody has workaround for this??? If not this would be a feature request.

[khainhero]

Perhaps, this can help you. I am planning to include this for my own project when I have time. So I can modify the notification before its displayed to the user.
https://developer.apple.com/documentation/usernotifications/unnotificationserviceextension

more info here:
https://documentation.onesignal.com/docs/service-extensions#section-notificationextenderservice-span-class-label-all-label-android-android-span-

[kaumudpa]

We need a way to send Rich Notifications out of the box for ios for FCM. The current plugin supports FCM Rich messages for Android but not for iOS.

[zanecidan]

We need a way to send Rich Notifications out of the box for ios for FCM. The current plugin supports FCM Rich messages for Android but not for iOS.

@kaumudpa I'm looking into this too. May I know how do you send Rich Notifications for Android using current plugin?

[kaumudpa]

I will give you a small and simple example.

Without any additional efforts in the project Rich Notifications i.e. Notifications with Image can be sent to an android device. But Rich Notifications cannot be sent to the iOS Devices on the current plugin.

I have tried using Notification extension in the ios project but it created problems with the plugin. This should be an Out of the box feature for the plugin.

I am attaching screenshots of ios and android for the same notification which was sent using the following :

{
   "to": "Your FCM Device Token",
   "content_available": true,
   "mutable_content": true,
   "notification":
   {
              "title": "Testing Rich FCM",
              "body": "Testing FCM With images",
              "sound": "default",
              "image": "https://cdn.pixabay.com/photo/2018/01/21/01/46/architecture-3095716_960_720.jpg"
            }
}

[zanecidan]

@kaumudpa Thank you very much.

[janmoppel]

Hello @kaumudpa !

Does the problem still persist in the latest plugin version?

[kaumudpa]

Yes it does.

…

On Mon, 30 Sep 2019 at 1:49 PM, Jan Moppel ***@***.***> wrote: Hello @kaumudpa <https://github.com/kaumudpa> ! Does the problem still persist in the latest plugin version? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#35866?email_source=notifications&email_token=ADHE2NFE6XFVCEAEQ325FULQMGZCVA5CNFSM4H7OMJIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD742NSQ#issuecomment-536454858>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADHE2NGRG2TDEWGPN5HIGFTQMGZCVANCNFSM4H7OMJIA> .

[kroikie]

@kaumudpa

This issue has been moved to firebase/flutterfire#357. Any further collaboration will be done there.

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.