firebase_messaging not working if include flutter_local_notifications package on iOS

[anderscheow]

Method on Firebase Cloud Messaging, onMessage and onResume do not get trigger when I include flutter_local_notifications package.

[MaikuB]

There's a note about this in the README under the iOS integration section. Please check there

[rlee1990]

Any way to get around this issue. Really don't see any other packages for local notifications for ios or android

[rlee1990]

@MaikuB

[MaikuB]

Have you read my comment above on the note in the README?

[andreidiaconu]

From the README:

NOTE: this plugin registers itself as the delegate to handle incoming notifications and actions. This may cause problems if you're using other plugins for push notifications (e.g. firebase_messaging) as they will most likely do the same and it's only possible to register a single delegate. iOS handles showing push notifications out of the box so if you're only using this plugin to display the notification payload on Android then it's suggested that you fork the plugin code and remove the following part in the iOS code

UNUserNotificationCenter *center = [UNUserNotificationCenter currentNotificationCenter];
center.delegate = instance;

Unfortunately, this platform limitation does mean that it's not possible to use this plugin together other plugins for push notifications on iOS. If you are in this situation, then my only advice is that you'll need to need to look at writing customised platform-specific code for your application that may involve taking bits and pieces of code from the plugins you need.

I see this project is forked 27 times. Did anyone, by any chance, get the 2 plugins to work together (perhaps using a Decorator pattern or something similar)?

[radvansky-tomas]

bump

[MaikuB]

I had raised an issue in the Flutter repository to see if they could expose functionality that would enable multiple plugins can register as a notification center delegate. I would suggesting upvoting there flutter/flutter#22099

[rlee1990]

@MaikuB Any timeline on when the flutter team will make this change?

[MaikuB]

@rlee1990 you'd have to ask the Flutter team

[eikebartels]

I think an option would be to disable the method swizzling and call the apis directly in the app delegate?

To think this throw, @MaikuB I assume this lib also uses method swizzling? If so what would be the best way to call the apis manually?
With firebase messaging it is possible.
https://firebase.google.com/docs/cloud-messaging/ios/client#token-swizzle-disabled
https://firebase.google.com/docs/cloud-messaging/ios/receive#handle-swizzle

[tsangpozheng]

IOSInitializationSettings should add a switch that controls whether this plugin will register self as the only UNUserNotificationCenter delegate.

This option will save us from forking the code and remove the following part in the iOS code as the doc said.
UNUserNotificationCenter *center = [UNUserNotificationCenter currentNotificationCenter]; center.delegate = instance;

[MaikuB]

Had already considered that a long time ago, ignoring the need to fork, it seemed to me like it could cause more problems. See #50

[rlee1990]

Hi @MaikuB will we still have this issue with the update that the Flutter team made?

[MaikuB]

@eikebartels apologies for the late response, somehow I've missed your message. The plugin itself isn't implemented to use method swizzling.

@rlee1990 if the update you're referring is around the issue on the Flutter repository where you had tagged me then no. That's a completely different issue and if you go back to the earlier posts, I have mentioned that I had an issue created on the Flutter repo that is relevant for the problem here. I can see you had given the post a thumbs up already too