I'm using the plugin, while everything works fine when our push notifications go through firebase, we also use another SDK (CleverTap) which has push notifications for marketing campaigns. The issue is the push has totally different payloads and has separate tracking for view/tap on the notification. When the push is sent through CleverTap we get duplicate notifications. One is empty (the one handled through MyFirebaseMessagingService) and the other one is fine, since it's handled by the CleverTap SDK.
Any thoughts on how to solve this?
I think implementing FirebaseMessagingService on my own and pushing either through CleverTap or CrossFirebaseCloudMessaging.Current.OnNotificationReceived();
For more information, I made my own FirebaseMessagingService, but I think it was ignored and MyFirebaseMessagingService takes over on release builds.
Hello,
Issue is on Android.
I'm using the plugin, while everything works fine when our push notifications go through firebase, we also use another SDK (CleverTap) which has push notifications for marketing campaigns. The issue is the push has totally different payloads and has separate tracking for view/tap on the notification. When the push is sent through CleverTap we get duplicate notifications. One is empty (the one handled through MyFirebaseMessagingService) and the other one is fine, since it's handled by the CleverTap SDK.
Any thoughts on how to solve this?
I think implementing FirebaseMessagingService on my own and pushing either through CleverTap or CrossFirebaseCloudMessaging.Current.OnNotificationReceived();
For more information, I made my own FirebaseMessagingService, but I think it was ignored and MyFirebaseMessagingService takes over on release builds.