FCM Service Conflict with Other Firebase Messaging Plugins

[Clon1998]

The flutter_live_activities plugin automatically registers a FirebaseMessagingService in Android, which conflicts with other FCM-based plugins (like awesome_notifications_fcm) that also register their own FirebaseMessagingService. This causes only one service to receive FCM messages, breaking functionality for other plugins.

Current Behavior

• flutter_live_activities automatically registers LiveActivityFirebaseMessagingService
• Other FCM plugins (e.g., awesome_notifications_fcm) register their own services
• Only one service receives FCM messages, breaking the other plugin's functionality
• No documentation warns about this conflict

Expected Behavior

Either:

1. Documentation clearly warns about FCM service conflicts and provides integration guidance
2. Optional service registration - allow developers to disable automatic service registration
3. Integration helpers - provide utilities to integrate with existing FCM services

Current workaround required:

Developers must manually disable the service in their main AndroidManifest.xml:

<service
    android:name="com.example.live_activities.LiveActivityFirebaseMessagingService"
    android:enabled="false" />

Reproduction Steps

1. Add flutter_live_activities to a Flutter project
2. Add any other FCM-based plugin (e.g., awesome_notifications_fcm, firebase_messaging)
3. Try to receive notifications through the other plugin
4. Observe that notifications are not received/handled correctly

[EArminjon]

Developers must manually disable the service in their main AndroidManifest.xml:

That will disable Live Activity on Android.

Didn't expected that behavior, need to find a solution.

[Clon1998]

Developers must manually disable the service in their main AndroidManifest.xml:

That will disable Live Activity on Android.

Didn't expected that behavior, need to find a solution.

Yep,
but since I am using awesome notifications anyway it's fine for my use case.

[EArminjon]

Developers must manually disable the service in their main AndroidManifest.xml:

That will disable Live Activity on Android.
Didn't expected that behavior, need to find a solution.

Yep, but since I am using awesome notifications anyway it's fine for my use case.

So you use https://pub.dev/packages/awesome_notifications instead of https://pub.dev/packages/awesome_notifications_fcm ?

On my side, despite the fact that the Live Activity plugin listen FirebaseMessagingService.onMessageReceived, my Flutter code can well listen FirebaseMessaging.onBackgroundMessage or FirebaseMessaging.onMessage and receive messages.

So the issue is related to other native package only which try to listen also FirebaseMessagingService.onMessageReceived ?

[Clon1998]

Developers must manually disable the service in their main AndroidManifest.xml:

That will disable Live Activity on Android.
Didn't expected that behavior, need to find a solution.

Yep, but since I am using awesome notifications anyway it's fine for my use case.

So you use https://pub.dev/packages/awesome_notifications instead of https://pub.dev/packages/awesome_notifications_fcm ?

On my side, despite the fact that the Live Activity plugin listen FirebaseMessagingService.onMessageReceived, my Flutter code can well listen FirebaseMessaging.onBackgroundMessage or FirebaseMessaging.onMessage and receive messages.

So the issue is related to other native package only which try to listen also FirebaseMessagingService.onMessageReceived ?

I am using both the non fcm and fcm version of awesome notifications. The first package manages the part of creating notifications while the fcm version, integrates with firebase and allows remote push notifications.

I did not investigate the issue further but apparently only one service can listen to the firebase messaging service.

Another solution to allow multiple would be a custom one that would delegate the messages to either service based on the content of the message. However, since I am fine without LA on Android, I stuck to disabling the service of the LA libary.