-
Notifications
You must be signed in to change notification settings - Fork 14
Description
Hello, we recently discovered that our marketing push notifications have been broken for quite some time. I've narrowed it down to an mparticle update between versions 5.35.1 to 5.38.2, and continue to see the issue in the current 5.49.0 version. We currently are delegating the handling of these pushes to the sdk via your receiver and service in our manifest as described in your docs:
<receiver
android:exported="true"
android:name="com.mparticle.MPReceiver"
android:permission="com.google.android.c2dm.permission.SEND">
<intent-filter>
<action android:name="com.google.android.c2dm.intent.RECEIVE" />
<!-- Use your package name as the category -->
<category android:name="com.reverb.app" />
</intent-filter>
</receiver>
<service android:name="com.mparticle.MPService" />
<receiver android:name="com.braze.push.BrazePushReceiver" />
Braze In-app messages do still work, so this configuration is still receiving pushes and correctly routing those to the Braze sdk, it is just failing when it comes to displaying system notifications. Also, for both in-app messages and push notifications, I see these 2 events in the logs, which seems to indicate MPReceiver is at least trying to handle both:
MPServiceHandling action: com.google.android.c2dm.intent.RECEIVE
MPServiceHandling action: com.mparticle.push.RECEIVE
I have also verified that the issue is not with the Braze sdk since if I add a call to BrazeFirebaseMessagingService.handleBrazeRemoteMessage in our own FirebaseMessagingService implementation, pushes display. I am considering rolling forward with this workaround, but I am unsure how to log these to mparticle. For logNotification I'm guessing we would use RemoteMessage.toIntent(), and for logNotificationOpened look for some intent extra that braze sets?